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: 66191     Entry time: Wed Feb 4 21:41:46 2009     In reply to: 66190
Icon: Reply  Author: Devin Bougie  Author Email: dab66@cornell.edu 
Category: Request  OS: Linux  ELOG Version: 2.7.5 
Subject: Re: frequent crashes on SL4 
Hi Stefan,

> Just follow
> https://midas.psi.ch/elog/faq.html#19

That's what I attempted to do, but the need to restart ELOG before I could get to the gdb console prevented us from obtaining a stack trace.  I am now setting up a test ELOG server where we will continue 
trying to reproduce our crashes and obtain a stack trace.

> Crashes with attached images are getting reported more and more these days, but so far I was not able to reproduce it. Maybe it's related to ImageMagic 
> somehow, in which case disabling this feature might give some insight. To do so, you have to modify elogd.c and recompile. Change
> 
>    /* check for ImageMagick */
>    my_shell("convert -version", str, sizeof(str));
>    image_magick_exist = (strstr(str, "ImageMagick") != NULL);
> 
> 
> to
> 
>    /* check for ImageMagick */
>    image_magick_exist = 0;

This has now been done and installed on our production server.  I will let you know if we have any more crashes with ImageMagick disabled.

Many thanks,
Devin
ELOG V3.1.5-fe60aaf