Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Re: OVDB errors (Julien ?LIE)
   2. Re: OVDB errors (Kamil =?iso-8859-2?Q?Jo=F1ca?=)


----------------------------------------------------------------------

Message: 1
Date: Sun, 30 Jul 2017 14:43:00 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: OVDB errors
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

Hi Kamil,
> Recently I upgrade my inn debian package to version:
> 2.6.1-2+b2 (whatever it measn).
> Then I have noticed OVDB errors:

What was your previous version?  (a LFS one?)

In the Debian preinst script, there is:

""
You are trying to upgrade inn2 on a 32-bit system where an old inn2 package
without Large File Support is currently installed.

Since INN 2.5.4, Debian has stopped providing a 32-bit inn2 package and a
LFS-enabled inn2-lfs package and now only this LFS-enabled inn2 package is
supported.

This will require rebuilding the history index and the overview database,
but the postinst script will attempt to do it for you.

BEWARE: the timecaf spool format is not compatible between 32 and 64 bit
systems and no conversion tool is available.
""


The overview database should have already been rebuilt.



> 2017-07-30T11:01:37.897444+02:00 alfa nnrpd[26889]: OVDB: BDB2023 pthread 
> lock failed: Invalid argument
> 2017-07-30T11:01:37.897921+02:00 alfa nnrpd[26889]: OVDB: BDB0061 PANIC: 
> Invalid argument
> 2017-07-30T11:01:37.898150+02:00 alfa nnrpd[26889]: OVDB: BDB0060 PANIC: 
> fatal region error detected; run recovery
> 2017-07-30T11:01:37.898387+02:00 alfa nnrpd[26889]: OVDB: open: 
> version->open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
> 2017-07-30T11:01:37.898790+02:00 alfa nnrpd[26889]: can't open overview 
> Success
> 2017-07-30T11:01:43.133048+02:00 alfa ovdb_monitor[8485]: OVDB: BDB0060 
> PANIC: fatal region error detected; run recovery
> 2017-07-30T11:01:43.133662+02:00 alfa ovdb_monitor[8485]: OVDB: lock_detect: 
> BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
> 2017-07-30T11:01:43.133914+02:00 alfa ovdb_monitor[8485]: OVDB: BDB1581 File 
> handles still open at environment close
> 2017-07-30T11:01:43.134149+02:00 alfa ovdb_monitor[8485]: OVDB: BDB1582 Open 
> file handle: /var/spool/news/overview/__db.001
> 2017-07-30T11:01:43.134382+02:00 alfa ovdb_monitor[8485]: OVDB: BDB1582 Open 
> file handle: /var/spool/news/overview/__db.002
> 2017-07-30T11:01:43.134613+02:00 alfa ovdb_monitor[8485]: OVDB: BDB1582 Open 
> file handle: /var/spool/news/overview/__db.003
> 
> The only workaround is to rebuild overview :( but it happends ~daily.
> 
> I do not know if it is INN bug or Debian folks broke something ...

There are no recent changes in INN with regards to ovdb, and I think The Doctor
is running ovdb fine with the latest version.
I am sorry I do not have a clue right now to make it work better for you.

-- 
Julien ?LIE

? You know it's love when all you want is that person to be happy;
  even if you're not part of their happiness. ?


------------------------------

Message: 2
Date: Sun, 30 Jul 2017 14:52:05 +0200
From: [email protected] (Kamil =?iso-8859-2?Q?Jo=F1ca?=)
To: [email protected]
Subject: Re: OVDB errors
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-2

Julien ?LIE <[email protected]> writes:

> Hi Kamil,
>> Recently I upgrade my inn debian package to version:
>> 2.6.1-2+b2 (whatever it measn).
>> Then I have noticed OVDB errors:
>
> What was your previous version?  (a LFS one?)
No, it was also amd64 version
[...]

>> 
>> I do not know if it is INN bug or Debian folks broke something ...
>
> There are no recent changes in INN with regards to ovdb, and I think The 
> Doctor
> is running ovdb fine with the latest version.
> I am sorry I do not have a clue right now to make it work better for you.

So I have to check Berkeley DB or others libraries used by innd.
Thanks for info.
KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Help!  I'm trapped in a PDP 11/70!


------------------------------

Subject: Digest Footer

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

------------------------------

End of inn-workers Digest, Vol 96, Issue 6
******************************************

Reply via email to