Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon8.gif   frequent crashes on SL4, posted by Devin Bougie on Wed Feb 4 18:08:42 2009 
    icon2.gif   Re: frequent crashes on SL4, posted by Edmundo T Rodriguez on Wed Feb 4 18:46:58 2009 
    icon2.gif   Re: frequent crashes on SL4, posted by Stefan Ritt on Wed Feb 4 19:34:35 2009 
       icon2.gif   Re: frequent crashes on SL4, posted by Devin Bougie on Wed Feb 4 21:41:46 2009 
       icon2.gif   Re: frequent crashes on SL4, posted by Devin Bougie on Fri Feb 6 23:43:47 2009 
          icon2.gif   Re: frequent crashes on SL4, posted by Devin Bougie on Sat Feb 7 01:47:07 2009 
             icon2.gif   Re: frequent crashes on SL4, posted by Devin Bougie on Sat Feb 7 06:26:48 2009 090206a.log
       icon2.gif   Re: frequent crashes on SL4, posted by Devin Bougie on Sat Feb 7 01:59:53 2009 
          icon2.gif   Re: frequent crashes on SL4, posted by Stefan Ritt on Thu Feb 12 17:13:05 2009 
          icon2.gif   Re: frequent crashes on SL4, posted by Stefan Ritt on Fri Feb 13 16:57:02 2009 
             icon2.gif   Re: frequent crashes on SL4, posted by Devin Bougie on Tue Mar 24 15:14:28 2009 
                icon5.gif   difficulty with slow connections (was Re: frequent crashes on SL4), posted by Devin Bougie on Wed Mar 3 22:28:04 2010 
                   icon2.gif   difficulty with slow connections (was Re: frequent crashes on SL4), posted by Stefan Ritt on Fri Mar 12 12:49:39 2010 
                      icon2.gif   difficulty with slow connections (was Re: frequent crashes on SL4), posted by Devin Bougie on Wed Sep 8 15:31:33 2010 
Message ID: 66198     Entry time: Sat Feb 7 01:47:07 2009     In reply to: 66197     Reply to this: 66200
Icon: Reply  Author: Devin Bougie  Author Email: dab66@lepp.cornell.edu 
Category: Request  OS: Linux  ELOG Version: 2.7.5 
Subject: Re: frequent crashes on SL4 
> The bad news is that elogd is still crashing even after disabling Image Magick.  The good news is that this time it was reproducible and I did obtain a
> stack trace using gdb.

The seg fault reported above seems to be related to a specific elog entry combined with sending email notifications.  When trying to submit changes to that entry while sending email notifications, elogd seg faults.  We can edit the entry before it and create and edit a new entry after 
it.  Trying to edit that one entry and send notifications, however, reliably crashes elogd.  If I check "supress email notification", elogd does not seem to crash.  I have replicated this on separate elog servers running both SL4 and on SL5.  To compare with SL4, here is the trace I see on SL5 (Scientific Linux 5).

Once I receive the OK, I will send you the actual file that stores the problematic entry.  Please let me know if there is anything else I can send you.

Many thanks,
Devin

------
[root@lnx767 ~]# gdb /usr/local/sbin/elogd 13328
GNU gdb Red Hat Linux (6.5-37.el5_2.2rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

Attaching to program: /usr/local/sbin/elogd, process 13328
Reading symbols from /lib/libssl.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libssl.so.6
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /usr/lib/libgssapi_krb5.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgssapi_krb5.so.2
Reading symbols from /usr/lib/libkrb5.so.3...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libkrb5.so.3
Reading symbols from /lib/libcom_err.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /usr/lib/libk5crypto.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libk5crypto.so.3
Reading symbols from /lib/libresolv.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libcrypto.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.6
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libkrb5support.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libkrb5support.so.0
Reading symbols from /lib/libkeyutils.so.1...
(no debugging symbols found)...done.
Loaded symbols for /lib/libkeyutils.so.1
Reading symbols from /lib/libselinux.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libselinux.so.1
Reading symbols from /lib/libsepol.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libsepol.so.1
Reading symbols from /lib/libnss_files.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_nis.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1

(no debugging symbols found)
0x008db402 in __kernel_vsyscall ()
(gdb) c
Continuing.
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0x0804a125 in strieq ()
(gdb) where
#0  0x0804a125 in strieq ()
#1  0x73207365 in ?? ()
#2  0x00000000 in ?? ()
ELOG V3.1.5-fe60aaf