Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 702 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  66157   Tue Jan 20 15:20:38 2009 Entry Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Stack error when email notification is active

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)

  66158   Tue Jan 20 15:26:03 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: 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:

 

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.

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 ...
  66160   Tue Jan 20 16:07:03 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: 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.

 

-----------------------------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!

 

  66161   Tue Jan 20 16:10:22 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: 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.

 Windows binaries took care of this problem as with Message ID: 66157.

Problem solved, thanks!

 

  66164   Wed Jan 21 14:19:45 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: Stack error when email notification is active

Michael Ambrus wrote:

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!

 

 

Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.

The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:

Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6

The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?

It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.

Regards /Michael

  66183   Wed Jan 28 14:38:52 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: Stack error when email notification is active

Stefan Ritt wrote:

 

Michael Ambrus wrote:

 

Michael Ambrus wrote:

 

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!

 

 

 

Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.

The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:

Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6

The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?

It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.

Regards /Michael

 

The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.

Furthermore, TLS is not supported in elogd, only plain SMTP is possible. 

Thanks for the info, it saves me some time know this on beforehand.

You're right about the Windows binary, it's a lower SVN revision (2140).

 

  66184   Wed Jan 28 14:39:56 2009 Reply Michael Ambrusambrmi09@gmail.comBug reportWindows2.7.5Re: Stack error when email notification is active

Stefan Ritt wrote:

 

Michael Ambrus wrote:

 

Michael Ambrus wrote:

 

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!

 

 

 

Unfortunately can't validate this right now. I'm at a remote network trying to get ELOG on my Windows laptop working with e-mail notifications. Either my normal ISP will not allow the SMTP to accept relaying from external networks, or something else is wrong.

The Windows binary is behaving somewhat differently, it seems to behave like earlier versions. I.e. the error message seen on the browser (Error sending Email via "smtp.xxx.xxx") is very limited. Logging (level 6) will not revile much and -v doesn't output any hints either. Assuming the first possible cause, I registered a account at gmail to try see if their SMTP would allow e-mail relaying. Trying with the Windows binary version I seemingly leads to the same result (i.e. I don't see much and the error seen at the browser is the same). However, when trying to run ELOG on a machine at my home network the message is different:

Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. w40sm7583927ugc.6

The message does not surprise me (from previous experience, TLS was what made made postfix complicated to set up too). But what does surprise me is that the messages differ between the two (ELOG V2.7.5 running on a Linux machine and the Windows binary of the same version). Does Linux/Windows versions differ by conditionals in the code or did I somehow get an older Windows binary?

It would also be helpful knowing if ayone has got ELOG working with smtp.gmail.com.

Regards /Michael

 

The Windows Binaries are not recompiled for each minor modification. You should check the SVN revistion (the number which shows up at the very bottom of the page, which is 2153 in this case). It might well be that the Windows Binaries do not yet contain the modification for extended SMTP error report.

Furthermore, TLS is not supported in elogd, only plain SMTP is possible. 

Thanks for the info, it saves me some time know this on beforehand.

You're right about the Windows binary, it's a lower SVN revision (2140).

 

  66822   Sat May 15 06:01:40 2010 Entry A. Martinamartin@example.comBug reportAllsvnattachment filename bug & Makefile issue
If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Note the attachment to this post.

----

Makefile has the line:

# flag for SSL support
USE_SSL    = 1

However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
 You have to comment them out.

Lines 76-85 of Makefile should be replaced with this:

ifdef USE_SSL
ifneq ($(USE_SSL), 0)
CFLAGS += -DHAVE_SSL
LIBS += -lssl
endif
endif

ifdef USE_CRYPT
ifneq ($(USE_CRYPT), 0)
CFLAGS += -DHAVE_CRYPT
LIBS += -lcrypt
endif
endif

Thanks,
amartin
Attachment 1: file.txt
ELOG V3.1.5-3fb85fa6