Why may happen those errors and how to fix them?
inn 2.6.4

innd: buffindexed: block(2, 18) not occupied
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied
innd: buffindexed: block(1, 18) not occupied
innd: buffindexed: block(2, 16) not occupied
innd: buffindexed: block(0, 32) not occupied (index)
--
Miner

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Miner,

Why may happen those errors and how to fix them?

The good news is that these errors are auto-fixed just after the warning
in the logs. INN marks the block as occupied.

Yet, that's a bug that needs fixing but what causes it should be found...

innd: buffindexed: block(2, 18) not occupied
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied
innd: buffindexed: block(1, 18) not occupied
innd: buffindexed: block(2, 16) not occupied
innd: buffindexed: block(0, 32) not occupied (index)

Does it happen often? How many times a day?
What's your operating system?

--
Julien ÉLIE

« J'oubliais qu'Assurancetourix a une nouvelle corde à sa harpe ! »
(Astérix)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Julien ??LIE wrote:

Hi Miner,

Why may happen those errors and how to fix them?

The good news is that these errors are auto-fixed just after
the warning in the logs. INN marks the block as occupied.

Yet, that's a bug that needs fixing but what causes it should
be found...

innd: buffindexed: block(2, 18) not occupied
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied
innd: buffindexed: block(1, 18) not occupied
innd: buffindexed: block(2, 16) not occupied
innd: buffindexed: block(0, 32) not occupied (index)

Does it happen often? How many times a day?
What's your operating system?

It happen twice per day. I'm on Linux.

innd: buffindexed: block(2, 18) not occupied
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied
innd: buffindexed: block(1, 18) not occupied
innd: buffindexed: block(2, 16) not occupied
innd: buffindexed: block(0, 32) not occupied (index)
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied

--
Miner

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Julien ??LIE wrote:

Hi Miner,

Why may happen those errors and how to fix them?

The good news is that these errors are auto-fixed just after
the warning in the logs. INN marks the block as occupied.

Yet, that's a bug that needs fixing but what causes it should
be found...

innd: buffindexed: block(2, 18) not occupied
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied
innd: buffindexed: block(1, 18) not occupied
innd: buffindexed: block(2, 16) not occupied
innd: buffindexed: block(0, 32) not occupied (index)

This error disappear since I had replace old cycbuffs and
buffindexes with new.

--
Miner

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Julien ??LIE wrote:

Hi Miner,

Why may happen those errors and how to fix them?

The good news is that these errors are auto-fixed just after
the warning in the logs. INN marks the block as occupied.

Yet, that's a bug that needs fixing but what causes it should
be found...

innd: buffindexed: block(2, 18) not occupied
innd: buffindexed: block(0, 29) not occupied
innd: buffindexed: block(1, 20) not occupied
innd: buffindexed: block(1, 18) not occupied
innd: buffindexed: block(2, 16) not occupied
innd: buffindexed: block(0, 32) not occupied (index)

Does it happen often? How many times a day?
What's your operating system?

This error does not appear anymore since I did two things:
1) wrote more strict rules in storage.conf;
2) deleted the problematic group and recreate it again.

--
Miner

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Miner,

innd: buffindexed: block(2, 18) not occupied

Does it happen often? How many times a day?
What's your operating system?

This error does not appear anymore since I did two things:
1) wrote more strict rules in storage.conf;
2) deleted the problematic group and recreate it again.

I'm glad to hear the issue has been fixed with these actions.
What kind of "strict rules" did you add in storage.conf?

--
Julien ÉLIE

« – Qu'allons nous faire par Isis ?!
– Nous allons construire des défenses, par Bélénos !
– Tu as raison, par Bélisama !
– Est-ce qu'on ne pourrait pas s'en aller, par hasard ? » (Astérix)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Julien ??LIE wrote:

Hi Miner,

innd: buffindexed: block(2, 18) not occupied

Does it happen often? How many times a day?
What's your operating system?

This error does not appear anymore since I did two things:
1) wrote more strict rules in storage.conf;
2) deleted the problematic group and recreate it again.

I'm glad to hear the issue has been fixed with these actions.
What kind of "strict rules" did you add in storage.conf?

Before
newsgroups: !control,!control.*,!junk,!local.test,!local.help,!local.news,!local.complain,local.*

After
newsgroups: local.*,!control,!control.*,!junk,!local.test,!local.help,!local.info,!local.complain
--
Miner

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)