[Aide] Segmentation fault on s390x architecture [0.11]

Christoph Ehret christoph.ehret at swisscom.com
Mon Feb 27 17:44:41 EET 2006


Hi,

When running aide on a s390x architecture, I get a segmentation fault. I
first saw this when running "make check". I then tried to run "aide
--init" with my own aide.conf file, but again I had a segmentation
fault. If we have a look at was happened when I ran aide --init with my
own conf file, we can see that some data was written to "aide.db.new"
before the segmentation fault happened :

@@begin_db
# This file was generated by Aide, version 0.9.4
# Time of generation was 2006-02-27 16:19:27
@@db_spec name lname attr perm uid gid size atime mtime ctime inode
lcount md5 sha1 rmd160 tiger
/sbin 0 67111933 40755 0 0 4096 MTE0MTA0MTgyNA== MTEzNzUxMTE4Ng==
MTEzNzUxMTE4Ng== 86 2 0 0 0 0
/scratch 0 67111933 40777 0 0 3976 MTE0MTA1MDgxOA== MTE0MDYxODE4NQ==
MTE0MDYxODE4NQ== 2 111 0 0 0 0
/tmp 0 67111933 41777 0 0 4096 MTE0MTA1MzE2MA== MTE0MTA1MzE1OQ==
MTE0MTA1MzE1OQ== 2 3 0 0 0 0
/sys 0 67111933 40755 0 0 0 MTE0MTAwOTYxNA== MTE0MDU4NzUwMA==
MTE0MDU4NzUwMA== 1 8 0 0 0 0
/dev 0 67111933 40755 0 0 3000 MTE0MTAzMDg5OA== MTE0MDU4NzUxOQ==
MTE0MDU4NzUxOQ== 204 8 0 0 0 0
/srv 0 67111933 40755 0 0 4096 MTE0MTAzMDg5OA== MTA5MjMzMDEzMA==
MTEyMzE1NTg0MA== 87 2 0 0 0 0
/media 0 67111933 40755 0 0 4096 MTE0MTAzMDg5OA== MTA5MjMzMDEzMA==
MTEyMzE1NTg0MA== 84 2 0 0 0 0
/mnt 0 67111933 40755 0 0 4096 MTE0MTAzMDg5OA== MTA5MjMzMDEzMA==
MTEyMzE1NTg0MA== 85 2 0 0 0 0


And here the end of the strace output when I run again the aide --init :


write(3, "/media 0 67111933 40755 0 0 4096"..., 97) = 97
lstat("/mnt", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
gettimeofday({1141053567, 607180}, NULL) = 0
write(3, "/mnt 0 67111933 40755 0 0 4096 M"..., 95) = 95
lstat("/.autofsck", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
gettimeofday({1141053567, 607710}, NULL) = 0
open("/.autofsck", O_RDONLY)            = 6
fstat(6, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


Is this due to the s390x architecture or is there any other reason to
this segmentation fault ?

I really thank you for your help.

Chris



More information about the Aide mailing list