elogd keeps crashing, any thoughts?, posted by Allen on Thu Dec 3 20:25:50 2009
|
We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.
In the logs, I see: |
elogd hangs when Date format in elogd.cfg, posted by Stefan Kanitz on Thu Jan 8 14:42:34 2009
|
Hi,
after setting |
elogd hangs on self referencing log entry, posted by Kester Habermann on Mon Feb 25 17:03:50 2019 
|
Hello,
Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was
that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be |
|
elogd hangs, posted by Alan Grant on Fri Aug 18 05:28:16 2017
|
I have a very long standing problem with elog over the last few versions where almost daily the service will hang. Cannot even Restart elogd, that
just hangs. Clients experience Page not Found. I can only get the service reinitialized by rebooting the VM machine. I have Elog verbose logging On plus
a number of external triage monitors running but nothing is yielding clues beyond the precise time the hang occurs. Aside from providing the |
elogd does not exit on SIGTERM, posted by Heiko Scheit on Wed Feb 18 16:54:27 2004
|
When trying to stop elogd processes with the kill command
elogd exits only after access to the logbook.
|
|
elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:16:31 2016
|
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text: |
|
elogd dies after receiving second SIGHUP, posted by Kester Habermann on Tue Nov 11 16:45:04 2008
|
elogd continues to run after a SIGHUP. If a second SIGHUP is received the daemon terminates.
This was observed on Solaris 10 (SPARC).
The documentation states that elogd should re-read configuration after receiving SIGHUP. |
elogd crashes with malloc() memory corruption, posted by Mark Bergman on Fri Mar 1 16:35:21 2013
|
I'm having an issue with ELog 2.9.2 revision 2455 where it crashes consistently with:
*** glibc detected *** /usr/local/sbin/elogd: malloc(): memory corruption: 0x0000000014977210 ***
(the address varies). The crash seems to be triggered by the attempt to email a log entry. The log entry itself is saved. If I open the existing |