Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

You do not have mail.


computers / news.software.nntp / Re: block not occupied

SubjectAuthor
* block not occupiedMiner
`* Re: block not occupiedJulien ÉLIE
 +- Re: block not occupiedMiner
 +- Re: block not occupiedMiner
 `- Re: block not occupiedMiner

1
block not occupied

<sttpps$9q1$1@txtcon.i2p>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=637&group=news.software.nntp#637

  copy link   Newsgroups: news.software.nntp
Path: i2pn2.org!i2pn.org!rocksolid2!txtcon.i2p!.POSTED.127.163.152.53!not-for-mail
From: joh...@dhoe.invalid (Miner)
Newsgroups: news.software.nntp
Subject: block not occupied
Date: Tue, 8 Feb 2022 13:05:02 -0000 (UTC)
Organization: TxtCon.I2P
Message-ID: <sttpps$9q1$1@txtcon.i2p>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 8 Feb 2022 13:05:02 -0000 (UTC)
Injection-Info: txtcon.i2p; posting-account="miner"; posting-host="127.163.152.53";
logging-data="10049"; mail-complaints-to="txtcon@i2pmail.org"
 by: Miner - Tue, 8 Feb 2022 13:05 UTC

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

Re: block not occupied

<stuhh1$1anqi$1@news.trigofacile.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=638&group=news.software.nntp#638

  copy link   Newsgroups: news.software.nntp
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.trigofacile.com!.POSTED.176-143-2-105.abo.bbox.fr!not-for-mail
From: iul...@nom-de-mon-site.com.invalid (Julien ÉLIE)
Newsgroups: news.software.nntp
Subject: Re: block not occupied
Date: Tue, 8 Feb 2022 20:49:52 +0100
Organization: Groupes francophones par TrigoFACILE
Message-ID: <stuhh1$1anqi$1@news.trigofacile.com>
References: <sttpps$9q1$1@txtcon.i2p>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 8 Feb 2022 19:49:53 -0000 (UTC)
Injection-Info: news.trigofacile.com; posting-account="julien"; posting-host="176-143-2-105.abo.bbox.fr:176.143.2.105";
logging-data="1400658"; mail-complaints-to="abuse@trigofacile.com"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
Gecko/20100101 Thunderbird/91.5.1
Cancel-Lock: sha1:zxnG/fVY7Me1c2RzthgeqGSDwP8= sha256:aWGDHyneBA0qdg0wKLuuz3UPYFON7hAyiWPfxVeSe0E=
sha1:+dYLzFN3lqtkwcjuqw6DOJci+Vo= sha256:jMILoAvm2nuamhpj2DHPXzpV1h8wT0GReQAP/IXqvro=
Content-Language: fr
In-Reply-To: <sttpps$9q1$1@txtcon.i2p>
 by: Julien ÉLIE - Tue, 8 Feb 2022 19:49 UTC

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)

Re: block not occupied

<stvuok$5d4$1@txtcon.i2p>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=639&group=news.software.nntp#639

  copy link   Newsgroups: news.software.nntp
Path: i2pn2.org!rocksolid2!txtcon.i2p!.POSTED.127.163.152.53!not-for-mail
From: joh...@dhoe.invalid (Miner)
Newsgroups: news.software.nntp
Subject: Re: block not occupied
Date: Wed, 9 Feb 2022 08:41:58 -0000 (UTC)
Organization: TxtCon.I2P
Message-ID: <stvuok$5d4$1@txtcon.i2p>
References: <sttpps$9q1$1@txtcon.i2p> <stuhh1$1anqi$1@news.trigofacile.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 9 Feb 2022 08:41:58 -0000 (UTC)
Injection-Info: txtcon.i2p; posting-account="miner"; posting-host="127.163.152.53";
logging-data="5540"; mail-complaints-to="txtcon@i2pmail.org"
 by: Miner - Wed, 9 Feb 2022 08:41 UTC

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

Re: block not occupied

<t1mt7g$ikm$1@txtcon.i2p>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=684&group=news.software.nntp#684

  copy link   Newsgroups: news.software.nntp
Path: i2pn2.org!i2pn.org!rocksolid2!txtcon.i2p!.POSTED.127.163.152.53!not-for-mail
From: joh...@doe.invalid (Miner)
Newsgroups: news.software.nntp
Subject: Re: block not occupied
Date: Sat, 26 Mar 2022 11:25:37 -0000 (UTC)
Organization: TxtCon.I2P
Message-ID: <t1mt7g$ikm$1@txtcon.i2p>
References: <sttpps$9q1$1@txtcon.i2p> <stuhh1$1anqi$1@news.trigofacile.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 26 Mar 2022 11:25:37 -0000 (UTC)
Injection-Info: txtcon.i2p; posting-account="miner"; posting-host="127.163.152.53";
logging-data="19094"; mail-complaints-to="txtcon@i2pmail.org"
 by: Miner - Sat, 26 Mar 2022 11:25 UTC

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

Re: block not occupied

<t8t3ss$lu5$1@txtcon.i2p>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=863&group=news.software.nntp#863

  copy link   Newsgroups: news.software.nntp
Path: i2pn2.org!rocksolid2!txtcon.i2p!.POSTED.127.163.152.53!not-for-mail
From: inva...@invalid.invalid (Miner)
Newsgroups: news.software.nntp
Subject: Re: block not occupied
Date: Tue, 21 Jun 2022 18:50:04 -0000 (UTC)
Organization: TxtCon.I2P
Message-ID: <t8t3ss$lu5$1@txtcon.i2p>
References: <sttpps$9q1$1@txtcon.i2p> <stuhh1$1anqi$1@news.trigofacile.com> <t8n5uk$838$1@txtcon.i2p> <t8qluv$dbu1$1@news.trigofacile.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 21 Jun 2022 18:50:04 -0000 (UTC)
Injection-Info: txtcon.i2p; posting-account="miner"; posting-host="127.163.152.53";
logging-data="22469"; mail-complaints-to="txtcon@i2pmail.org"
 by: Miner - Tue, 21 Jun 2022 18:50 UTC

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

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor