Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Peter Kovac on Mon Nov 27 17:29:41 2006 
    icon2.gif   Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Stefan Ritt on Tue Nov 28 10:34:54 2006 
       icon2.gif   Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Kevin O'Sullivan on Fri Jan 16 23:54:46 2009 
          icon2.gif   Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by John Rouillard on Sat Jan 17 08:16:19 2009 
Message ID: 2097     Entry time: Tue Nov 28 10:34:54 2006     In reply to: 2093     Reply to this: 66153
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Linux  ELOG Version: 2.6.1+r164 
Subject: Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing) 

Peter Kovac wrote:
First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.

The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.

Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...


There are three reasons why an elog server can go into an infinite loop:

  • A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
  • A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
  • Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.
ELOG V3.1.5-fe60aaf