elogd moves elog entries, posted by Konstantin Olchanski on Wed May 20 01:59:17 2015
|
elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
in the release announcement and in the release and migration notes. K.O. |
elogd lost entry database without restart during file system trouble, posted by Andreas Luedeke on Thu Apr 30 09:54:17 2015
|
I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
|
|
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: |