Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   Elog Crashes, posted by lance on Mon Jul 20 09:26:41 2009 Elog_crash_events.doc
    icon2.gif   Re: Elog Crashes, posted by Stefan Ritt on Mon Jul 20 10:30:44 2009 
Message ID: 66450     Entry time: Mon Jul 20 10:30:44 2009     In reply to: 66449
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: Windows  ELOG Version: 2.7.6 
Subject: Re: Elog Crashes 

lance wrote:
Stefan,
 
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
 
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
 
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
 
I have attached the eventlog files for you if you have any ideas I would appreciate them.
 
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
 
Any help is much appreciated
 
 
Regards,
 
Lance

Using the Windows event log won't help much. I guess in your case elogd is driven into some kind of endless loop (does the CPU go to 100%???). There are only two possibilities to tackle this:

1) You find a way to reliably reproduce this problem, tell me how to do this. When I can reproduce it here, I can fix it easily.

2) You do debugging yourself. Under Linux this is simple, since you have debuggers on most systems. Under Windows however, you first have to install the Visual C++ development environment. I believe there is a free version (Express?) which you can use. You then run elogd under the debugger, and when it hangs you investigate where. This needs some basic knowledge about C++ development and I'm not sure if you have this, but maybe you can find someone around you who does. 

ELOG V3.1.5-3fb85fa6