|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG |
Not logged in |
 |
|
|
|
|
|
Message ID: 66154
Entry time: Sat Jan 17 08:16:19 2009
In reply to: 66153
|
|
| 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) |
|
|
| Kevin O'Sullivan wrote: | I'm actually still having this issue in Ubuntu and I'm running elog version 2.7.5. In fact, now it's worse in 2.7.5 than in previous version because sometimes I have to restart the machine to get elog working again.
Is there anything I can do to help you find potential bugs with Ubuntu?
|
What does "lsof -p pid" on the elogd process show, how about "strace -p pid"?
Since you are using elogd with an apache providing reverse proxy, I wonder if one of
the httpd processes isn't properly closing it's connection when it's done. That would
hang the elogd process since it's single threaded and non forking (IIRC).
Also why do you need to restart the box, does killing and restarting the elogd process not work?
When you kill elogd, does 'sudo netstat -anp' show anything listening at the elogd port?
-- rouilj |