ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 254 of 807

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6451 Entries

Goto page Previous 1, 2, 3 ... 253, 254, 255 ... 805, 806, 807 Next

Fri Jan 16 23:54:46 2009

Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing)

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.

66154

Sat Jan 17 08:16:19 2009

John Rouillard

rouilj+elog@cs.umb.edu

Question

Linux

2.6.1+r164

Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing)

Kevin O'Sullivan wrote:

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

66156

Tue Jan 20 15:17:04 2009

Re: Top group causes: Internal error, no valid header!

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.

66158

Tue Jan 20 15:26:03 2009

Re: Top group causes: Internal error, no valid header!

Stefan Ritt wrote:

Michael Ambrus wrote:

Having "Top group" in a config-file for Windows will cause:

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.

Attachment 1: elogd.cfg

; Simple ELOG configuration for demonstration.

[global]
Group iSYS = ITodo, ITodo-v1.1, IBugZ
Group dSYS = DTodo, DBugZ
Group eSYS = ETodo, EBugZ
Group aSYS = ATodo, ABugZ
Group sSYS = STodo, SBugZ

Group Michael = work notes

Logbook Tabs = 1
port = 8084

;URL = https://kato.homelinux.org/elog-ambrmi09/
;SSL = 1
;Relative redirection = 1
URL = http://EUDR6J03J:8084

SMTP host = smtp.glocalnet.net
SMTP username = rhj764h@tninet.se
SMTP Password = XXXremovedXXX
Resolve host names = 1

;Top group Philips = iSYS, dSYS, eSYS, aSYS, sSYS
;Top group Private = Michael

Password file = philips.pwd
Admin user = mambrus
Self register = 1
Allow password change = 1

[global Philips]
Password file = philips.pwd
Admin user = mambrus
Self register = 1
Allow password change = 1

[global Private]
Password file = private.pwd
Admin user = mambrus
Self register = 1
Allow password change = 1

[global Isys]
Subdir = Isys

[global Dsys]
Subdir = Dsys

[global Esys]
Subdir = Esys

[global Asys]
Subdir = Asys

[global Ssys]
Subdir = Ssys

; 
==============================================================================
[work notes]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, 
Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

; 
==============================================================================
[ITodo]
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 1.0, 1.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date


Options Category= Implement, Prove, Document, Integrate, Investigate
Preset Submitter-Id = $long_name<$user_email>
Options Assignee     = michael.ambrus@philips.com
Preset Assignee = $user_email
Subst Host = $remote_host

Extendable options = Category, Class, Submitter-Id, Assignee, Version 

Required Attributes = Class, Submitter-Id

Preset Priority = low
Preset Confidential = no

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Class

; Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>

[ITodo-v1.1]
; 
==============================================================================
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 1.0, 1.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date


Options Category= Implement, Prove, Document, Integrate, Investigate
Preset Submitter-Id = $long_name<$user_email>
Options Assignee     = michael.ambrus@philips.com
Preset Assignee = $user_email
Subst Host = $remote_host

Extendable options = Category, Class, Submitter-Id, Assignee, Version 

Required Attributes = Class, Submitter-Id

Preset Priority = low
Preset Confidential = no
Preset Version = 1.1

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Class

; Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>


; 
==============================================================================

[IBugZ]
Theme = default
Comment = Bug&Issue Tracker
Attributes = Synopsis, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Host
Show Attributes Edit = Synopsis, Class, Priority, Severity, 
Confidential, Category, Submitter-Id
ROptions Class = sw-bug, doc-bug, support, change-request, mistaken, 
duplicate
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes

Options Category= Chores

Extendable options = Category, Submitter-Id 
Preset Submitter-Id = $long_name<$user_email>
Subst Host = $remote_host
Required Attributes = Class, Submitter-Id 

Preset Priority = low
Preset Confidential = no
Preset text = bugz_submit_tmplt.txt

Page Title = ELOG - $Class
Reverse sort = 1
Quick filter = Date, Class

;Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>


; DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

; 
==============================================================================

[DTodo]
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 0.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date


Options Category= Implement, Prove, Document, Integrate, Investigate
Preset Submitter-Id = $long_name<$user_email>
Options Assignee     = michael.ambrus@philips.com
Preset Assignee = $user_email
Subst Host = $remote_host

Extendable options = Category, Class, Submitter-Id, Assignee, Version 

Required Attributes = Class, Submitter-Id

Preset Priority = low
Preset Confidential = no

Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Class

; Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>

; 
==============================================================================
[DBugZ]
Theme = default
Comment = Bug&Issue Tracker
Attributes = Synopsis, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Host
Show Attributes Edit = Synopsis, Class, Priority, Severity, 
Confidential, Category, Submitter-Id
ROptions Class = sw-bug, doc-bug, support, change-request, mistaken, 
duplicate
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes

Options Category= Chores

Extendable options = Category, Submitter-Id 
Preset Submitter-Id = $long_name<$user_email>
Subst Host = $remote_host
Required Attributes = Class, Submitter-Id 

Preset Priority = low
Preset Confidential = no
Preset text = bugz_submit_tmplt.txt

Page Title = ELOG - $Class
Reverse sort = 1
Quick filter = Date, Class

;Email All = RISE@gmail.com
Use Email From = <elog@kato.homelinux.org>


; EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

; 
==============================================================================
[ETodo]
Theme = default
Comment = Todo list
Attributes = Subject, Version, Class, Priority, Severity, Confidential, 
Category, Submitter-Id, Assignee, Host
Show Attributes Edit = Subject, Version, Class, Priority, Severity, 
Confidential, Category, Submitter-Id, Assignee
ROptions Class = sw-architect, sw-algorithm, plattform
ROptions Priority = low, medium, high
ROptions Severity = non-critical, serious, critical
ROptions Confidential = no, yes
ROptions Version = 0.1

Style Priority high= background-color:red
Style Priority medium= background-color:yellow
Style Priority low= background-color:green
Style Priority low= color:white

Link display = id, date

... 209 more lines ...

66159

Tue Jan 20 15:37:19 2009

Re: Stack error when email notification is active

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?

66160

Tue Jan 20 16:07:03 2009

Re: Stack error when email notification is active

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.

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!

66161

Tue Jan 20 16:10:22 2009

Re: Top group causes: Internal error, no valid header!

Michael Ambrus wrote:

Having "Top group" in a config-file for Windows will cause:

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!

66162

Tue Jan 20 17:18:06 2009

Re: SMTP problems - Error sending Email via "smtp.glocalnet.net"

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.

Goto page Previous 1, 2, 3 ... 253, 254, 255 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6