Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 703 of 807  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  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
  66830   Thu May 20 04:33:07 2010 Reply A. Martinamartin@example.comBug reportAllsvnRe: attachment 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"
> 
> Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
> For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
> followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
> 0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
> easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
> find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
> you, I would like to keep it as it is.
> 

Thank you for your response.  

I can certainly use another filename, but I'm curious why elog doesn't convert the filename "000000_000000_file.txt" to
"YYMMDD_HHMMSS_000000_000000_file.txt" when it gets uploaded.  All other files are automatically prepended with this
string.  Manually renaming the file and then editing the elog entry via text editor seems to fix the file.

thanks,
amartin
  69843   Fri Dec 6 09:39:44 2024 Warning Olivier MARTINamande.olive@yahoo.frQuestionLinux3.1.5Probleme TLS
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?

  69848   Mon Dec 9 10:23:32 2024 Reply Olivier MARTINamande.olive@yahoo.frQuestionLinux3.1.5Re: Probleme TLS

Thanks,

Does email notification from a Gmail address work? It is noted that port 465 must be used for SSL use? Is this correct :


SMTP host : smtp.gmail.com

SMTP port = 465

SMTP username = monadresse@gmail.com

And, should I enter the password attached to my Gmail email and where?

Thanks in advance.

 

Stefan Ritt wrote:

TSL is not implemented in ELOG. Maybe I find time some day to do that, but if we have any volunteers in our community who could help me with that I would appreciate.

Stefan

Olivier MARTIN wrote:
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?

 

 

ELOG V3.1.5-3fb85fa6