innd 2.3 hangon after an news.daily
ab at icsmedia.de
ab at icsmedia.de
Mon Apr 17 10:16:59 UTC 2000
Hi,
I test the version inn-CURRENT-20000414 with he db-2.7.7 .
After a news.daily the innd wasn't responding. The same after an newstart.
Over the gdb I found the program waiting in the open_db_file() function.
The ovdb_recover logs that:
Apr 17 11:13:30 papenburg-lnx ovdb_recover[408]: OVDB: log_get: read: Input/output error
Apr 17 11:13:30 papenburg-lnx ovdb_recover[408]: OVDB: Finding last valid log LSN: file: 35 offset 3827394
Apr 17 11:13:30 papenburg-lnx ovdb_recover[408]: OVDB: log_get: unable to find checkpoint record: no checkpoint set.
Apr 17 11:14:19 papenburg-lnx ovdb_recover[408]: OVDB: log_get: checksum mismatch
Apr 17 11:14:19 papenburg-lnx ovdb_recover[408]: OVDB: log_get: read: Input/output error
and he ends with an "Segmentation fault".
(gdb) info stack
#0 0x0 in ?? ()
#1 0x807df3e in __log_close_files ()
#2 0x807bfc6 in log_close ()
#3 0x80685de in db_appexit ()
#4 0x806859c in db_appinit ()
#5 0x804a6b8 in ovdb_open_berkeleydb (mode=2, flags=1) at ovdb.c:643
#6 0x8049d2d in main (argc=2, argv=0xbffff8a4) at ovdb_recover.c:60
Axel
More information about the inn-workers
mailing list