Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Stack error when email notification is active, posted by Michael Ambrus on Tue Jan 20 15:20:38 2009 
    icon2.gif   Re: Stack error when email notification is active, posted by Stefan Ritt on Tue Jan 20 15:37:19 2009 
       icon2.gif   Re: Stack error when email notification is active, posted by Michael Ambrus on Tue Jan 20 16:07:03 2009 
          icon2.gif   Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 21 14:19:45 2009 
             icon2.gif   Re: Stack error when email notification is active, posted by Stefan Ritt on Wed Jan 21 14:31:01 2009 
                icon2.gif   Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 28 14:38:52 2009 
                icon2.gif   Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 28 14:39:56 2009 
Message ID: 66184     Entry time: Wed Jan 28 14:39:56 2009     In reply to: 66165
Icon: Reply  Author: Michael Ambrus  Author Email: ambrmi09@gmail.com 
Category: Bug report  OS: Windows  ELOG Version: 2.7.5 
Subject: Re: 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).

 

ELOG V3.1.5-fe60aaf