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: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 21 14:19:45 2009
|
| 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 |
|
Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 28 14:38:52 2009
|
| 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).
|
|
Re: Stack error when email notification is active, posted by Michael Ambrus on Wed Jan 28 14:39:56 2009
|
| 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).
|
Quick filter for date, posted by Michael on Thu Jul 16 11:18:05 2009
|
Hello !
Is any posibility to set quick filter, for fields with atribute "date", to exactly value, like 15/07/2009, instead of drop menu with values like - last day, last week, etc ?
Tnx in advance !
|
|
Re: Quick filter for date, posted by Michael on Thu Jul 16 13:47:31 2009
|
| Stefan Ritt wrote: |
|
| Michael wrote: |
|
Hello !
Is any posibility to set quick filter, for fields with atribute "date", to exactly value, like 15/07/2009, instead of drop menu with values like - last day, last week, etc ?
Tnx in advance !
|
No, this is not imlemented. But you can go to the "Find" page, and select the "Start" and "End" date with the calendar picker tool. This are a few more clicks to do, but puttting this all into the quick filter would not fit there.
|
ok, tnx. |
|
UNC Pfade, posted by Michael on Wed Oct 19 13:52:24 2022
|
Hallo,
gibt es eine Möglichkeit das subdir auf ein Netzlaufwerk zu legen?
\\server\freigabe\...
Der Freigabepfad wird leider immer unter C:\... angelegt
Vielen Dank |
|
Re: UNC Pfade, posted by Michael on Thu Oct 20 07:53:31 2022
|
So there is no way to save the file on the network?! :(
Can i install the elog on a windows server? i tried it yesterday, but i think i missed something, couse i only could open the elog on the server and not with a client pc.
| Stefan Ritt wrote: |
|
UNCs are not officially supported by elog, but your operating system might map them if you're lucky, just try. It is however not recommended to do so, since network drives can sometimes be slow during network congestion and the response of elog will then suffer.
Stefan
| Michael wrote: |
|
Hallo,
gibt es eine Möglichkeit das subdir auf ein Netzlaufwerk zu legen?
\\server\freigabe\...
Der Freigabepfad wird leider immer unter C:\... angelegt
Vielen Dank
|
|
|
|