On 02/03/2013 11:27 PM, Bill Wohler wrote: > Alex Mestiashvili <a...@biotec.tu-dresden.de> wrote: > > >> On 02/03/2013 07:13 AM, Bill Wohler wrote: >> >>> Package: libpam-abl >>> Version: 0.4.3-1 >>> Severity: normal >>> >>> Over the past couple of days, I've started getting a lot of the >>> following messages in my log file: >>> >>> Jan 30 08:41:01 olgas pam_abl[32671]: Invalid argument (22) while >>> opening or creating database >>> >>> What's going on? >>> >> Could you please check that the databases are not corrupted by running >> the following commands and paste the output here? >> You need to install db5.1-util package for the tools. >> as root: >> >> db5.1_verify -h /var/lib/abl users.db >> db5.1_verify -h /var/lib/abl hosts.db >> > Thanks very much for the help. Let's see: > > $ sudo db5.1_verify -h /var/lib/abl users.db > db5.1_verify: file unknown has LSN 1019/5969166, past end of log at > 1019/5955818 > db5.1_verify: Commonly caused by moving a database from one database > environment > db5.1_verify: to another without clearing the database LSNs, or by > removing all of > db5.1_verify: the log files from a database environment > db5.1_verify: Page 0: metadata page corrupted > db5.1_verify: Page 0: could not check metadata page > db5.1_verify: users.db: DB_VERIFY_BAD: Database verification failed > Verification of users.db failed. > > Looks like trouble. > > $ sudo db5.1_verify -h /var/lib/abl hosts.db > Verification of hosts.db succeeded. > > That looks OK. > > >> if they seem to be corrupted you can try to recover: >> >> db5.1_recover -v -h /var/lib/abl >> > $ sudo db5.1_recover -v -h /var/lib/abl > Finding last valid log LSN: file: 1019 offset 5974014 > > Wow, this has been going for some time. I have to leave now, so I'll > close with an observation and another question for you. > > You are welcome.
How did you install the libpam-abl package? It is not available for the stable so far... The highest version of Berkeley DB in Debian Stable 6.0.6 (Squeezy) is 4.8.30-2. The tests I performed yesterday where done on the testing system, where libdb is 5.1.29-5 - exactly as on your system. There is a tool called db5.1_upgrade which should be used to upgrade the database, but I don't know if it make sense to use it after running db5.1_recover on the old database... > I did a little more investigation. Between the time of the last good log > message and the one I listed above, two unusual things occurred. The > first is that I put my laptop to sleep, and the other is that I > installed the following packages (which don't look like they would > interfere): > > [INSTALL, DEPENDENCIES] libemma-java > [INSTALL, DEPENDENCIES] libganymed-ssh2-java > [INSTALL, DEPENDENCIES] libjna-java > [INSTALL, DEPENDENCIES] libsvnkit-java > [INSTALL, DEPENDENCIES] libtrilead-ssh2-java > [INSTALL] libsvnclientadapter-java > I don't think that these packages could influence libpam-abl and also don't see how putting to sleep would damage the database.. May be it makes sense to run smart check for the drive. > Also, I noticed that there were about 1000 old .log files in > /var/lib/abl. Is this normal? Is there a good way to consolidate them? > For the log files you can use db5.1_archive with -d flag, but see the man page for the details. > Thanks again! > > Best regards, Alex -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
