Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by Kevin O'Sullivan on Fri Jan 16 23:54:46 2009
|
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?
| Stefan Ritt wrote: |
| Peter Kovac wrote: | First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.
The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.
Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug... |
There are three reasons why an elog server can go into an infinite loop:
- A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
- A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
- Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.
|
|
|
Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing), posted by John Rouillard on Sat Jan 17 08:16:19 2009
|
| 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 |
|
Re: Top group causes: Internal error, no valid header!, posted by Stefan Ritt on Tue Jan 20 15:17:04 2009
|
| Michael Ambrus wrote: |
|
Having "Top group" in a config-file for Windows will cause:
GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0
Internal error, no valid header!
Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.
|
Please supply your full configuration file for error analysis. |
Re: Top group causes: Internal error, no valid header!, posted by Michael Ambrus on Tue Jan 20 15:26:03 2009 
|
| Stefan Ritt wrote: |
|
| Michael Ambrus wrote: |
|
Having "Top group" in a config-file for Windows will cause:
GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0
Internal error, no valid header!
Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.
|
Please supply your full configuration file for error analysis.
|
File attached. SMTP password removed, otherwise as original. |
|
Re: Stack error when email notification is active, posted by Stefan Ritt on Tue Jan 20 15:37:19 2009
|
| Michael Ambrus wrote: |
|
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries? |
|
Re: Stack error when email notification is active, posted by Michael Ambrus on Tue Jan 20 16:07:03 2009
|
| Stefan Ritt wrote: |
|
| Michael Ambrus wrote: |
|
Stack error is caused when an entry is submitted in a e-mail notification enabled log when a new entry is submitted. This error does not happen on linux (same Elog version, same config file).
Please let me know if there is anything I can do to help.
-----------------------------2916890032591
Content-Disposition: form-data; name="attfile"; filename=""
Content-Type: application/octet-stream
-----------------------------2916890032591--
timezone: 0, offset: 0
6 [main] elogd 2816 _cygtls::handle_exceptions: Error while dumping state
(probably corrupted stack)
Segmentation fault (core dumped)
|
Cygwin is not officially supported. Can you try the Windows binaries?
|
Sorry, I didn't know there were any (I've not used Elog for years and I think Cygwin was the only way back then). Tried them now and they seem to work. At least no stack error is caused. I'm getting some other error, but I think it's the handshake with the SMTP. I'll validate it's OK until tomorrow.
Windows binaries also solved the issue with the "Top grop" in my other bug rapport.
Thanks for the help!
|
|
Re: Top group causes: Internal error, no valid header!, posted by Michael Ambrus on Tue Jan 20 16:10:22 2009
|
| Michael Ambrus wrote: |
|
Having "Top group" in a config-file for Windows will cause:
GET / HTTP/1.1
Host: eudr6j03j:8084
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.0.5) Gecko/20
08120122 Firefox/3.0.5
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: sv-se,sv;q=0.8,en-us;q=0.5,en;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: unm=mambrus; upwd=U2lzc2kx; urem=0
Cache-Control: max-age=0
Internal error, no valid header!
Removing "top group" makes elogd.exe work. The error is repeatable and the same config file works on the same version of Elog on Linux. Elog was compiled with Cygwin.
|
Windows binaries took care of this problem as with Message ID: 66157.
Problem solved, thanks!
|
|
Re: SMTP problems - Error sending Email via "smtp.glocalnet.net", posted by Stefan Ritt on Tue Jan 20 17:18:06 2009
|
| Michael Ambrus wrote: |
|
Apparently 'MAIL FROM' syntax used by my ISP expects the address to be within <>.
Adding those in the config file fixes the problem:
Use Email From = <user@domain>
Note that the documentation indicates that the brackets should not be there and I'm not sure if this is a bug or not yet. According to this link the brackets should be there but I think to be consistent with other e-mail related attributes in the config file, they should be added by ELOG.
The 'Email' attibute however seems to work fine without the brackests. I.e.
Email All = user@doman
is OK.
I'm not very familiar with SMTP but I was fiddling around with this some time ago setting up a postfix MT. I eventually succeeded with my ISP, but not with gmail's SMTP. Apperently there are differences with the log-in procedure.
|
I added some code to elogd which always places <> around the "MAIL FROM:" in the SMTP communication. So I hope that problem should be solved from now on. Thank you for your detailed analysis and your hints. |
|