Bugzilla – Bug 406597
aide causes SIGABRT when doing an update
Last modified: 2009-01-14 10:13:52 UTC
I recently upgraded from 10.3 to 11.0 and found that aide is dying when doing an update. I successfully did an init and copied the new database over, however I get a SIGABRT on an update after some time. I've installed the debuginfo packages and ran aide through the debugging and this is what I got. gdb aide GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux"... (gdb) run --update Starting program: /usr/bin/aide --update Program received signal SIGABRT, Aborted. 0x0000000000477615 in raise () Current language: auto; currently asm (gdb) bt #0 0x0000000000477615 in raise () #1 0x00000000004376e3 in abort () #2 0x0000000000407e7c in db_readline_file (db=1) at db_file.c:550 #3 0x0000000000405067 in db_readline (db=19682) at db.c:238 #4 0x000000000040d2a1 in populate_tree (tree=0x726350) at gen_list.c:1456 #5 0x0000000000412cb3 in main (argc=<value optimized out>, argv=<value optimized out>) at aide.c:573 I did some more digging and found that the aide.spec file has "--with-dbhmactype=md5" as a configure option as well as "--enable-forced_dbmd", however there is no "--with-dbhmackey" option to configure. This cases aide to be required to have the database signed, but doesn't actually sign it because no key was provided at compile time. Once I added a "--with-dbhmackey" option with a test hash, it worked just fine.
anja,I would like to do an update here. fix is simple, removal of 1-2 lines in the .spec file
SWAMP: MaintenanceTracker-19644
released update
I just updated to opensuse 11.1 today and the problem is still there. Program received signal SIGABRT, Aborted. 0x00007ffff6978645 in raise () from /lib64/libc.so.6 (gdb) where #0 0x00007ffff6978645 in raise () from /lib64/libc.so.6 #1 0x00007ffff6979c33 in abort () from /lib64/libc.so.6 #2 0x000000000040a8f6 in ?? () #3 0x0000000000407a2a in ?? () #4 0x000000000040fd61 in ?? () #5 0x0000000000416083 in ?? () #6 0x00007ffff6964586 in __libc_start_main () from /lib64/libc.so.6 #7 0x0000000000402bb9 in ?? () #8 0x00007fffffffdbe8 in ?? () #9 0x000000000000001c in ?? () #10 0x0000000000000002 in ?? () #11 0x00007fffffffe096 in ?? () #12 0x00007fffffffe0a4 in ?? () #13 0x0000000000000000 in ?? ()
Nevermind, bug fixed. TUrns out you get an abort when using a database from an older version of aide.
Yes this really is broken again. I noticed that my cron jobs are aborting when I run aide --update. So I just grabbed the source RPM for aide 0.13.1-39.31 (the latest as of today) and checked the spec file. There is no --with-dbhmackey option, therefore aide will still fail as noted in the original description of this bug.
According to this post on the aide list the suggestion is to just remove --enable-forced_dbmd from the configure arguments.
hmpf. there were 2 aborts, i fixed the initial one, but not the one on update. i am removing the option as suggested
fixed for head, NEEDINFO ast for 11.1 fixing (11.0 seems to work)
The SWAMPID for this issue is 21409. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/21409)
submitted patchinfo and fixed package for 11.1
Update released for: aide Products: openSUSE 11.1 (debug, i586, ppc, x86_64)