Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 39 of 807  Not logged in ELOG logo
icon5.gif   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.
The logbooks appeared to be empty; new entries started with index "1".
The first time the origin of the problem were network troubles;
the second time it had been caused by a severe problem of our AFS file system service.
I never experienced this consequence for ELOG in the past when we had AFS problems.

Since the logbooks are used for the operation log of a user facility they continued to do new entries.
The next day I had to re-number the new entries and restart elogd and everything was fine.

I could understand if elogd crashes when the filesystem of the logbook goes away.
And when it restarts with an (temporarily) empty filesystem, that would explain what happened.
But it did not restart and the log file does not contain any information about any problem, 
just that suddenly all new entries in each logbook started with ID "1" again.

Stefan, any idea?
Anyone else ever experienced that with the new ELOG version (or older ones)?
icon1.gif   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:
Dec  3 14:01:23 nissrv18a kernel: [419738.139675] elogd[32003]: segfault at 4 ip 00007f183b19b560 sp 00007fff79f5e278 error 4
in libc-2.10.1.so[7f183b119000+166000]
 

Any thoughts?

icon5.gif   elogd hangs when Date format in elogd.cfg, posted by Stefan Kanitz on Thu Jan 8 14:42:34 2009 

Hi,

 

after setting

Date format = %Y-%m-%e

in elogd.cfg,

 

 

elogd hangs and must be restarted manually. Can anybody help me?

 

Thanks,

Steve

icon5.gif   elogd hangs on self referencing log entry, posted by Kester Habermann on Mon Feb 25 17:03:50 2019 011108a.log

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 reproduced by manually creating such a self-referencing log entry (see attachment). The problem entry that leads to the crash can be made by editing any elog entry and adding a line "Reply to: X" and a line "In reply to: X" where X is the MID of this entry.

1) Maybe it is possible to add a check when writing files that ensure, that is a log entry does not reference itself.
2) Maybe when loading files are preparing the thread view, elogd can detect cycles and abort.

 

 

icon5.gif   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 Config and log files what else can I provide for you to assist, and what other triage measures can you suggest I try? FYI, there can be up to 20 users at one time doing searches (not updates), and I've trimmed the depth of log files that can be searched so that the CPU/service doesn't bog down but that hasn't helped either. Inserts happen in the background using the elog client app (about 2 or 3 inserts per batch at sporadic times).

icon8.gif   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.

It should exit immediately, maybe after some cleanup.
icon5.gif   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: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
elogd: src/elogd.c:465: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.

The only change we did was adding/editing entries.

 

Does anyone else encounter the same issue ?

I did not find any hint in release notes that this issue would be fixed in a later version

 

Please don't get me wrong, I am not complaining. Elog does a great job for us since years.

 

Christian

icon8.gif   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.
ELOG V3.1.5-3fb85fa6