Re: elogd crashes during SSL Mirror operations involving attachments, posted by Andreas Warburton on Fri Jan 13 21:05:49 2017
|
When I switch from SSL = 1 to SSL = 0 and I use http:// instead of https://, the ability to upload attachments to logbook entries returns. With
both Chrome and Safari browsers, with SSL = 1 the file upload hangs after only a small percentage of the file has been uploaded. I ran the following
openssl diagnostic on my elogd port. Would anyone have advice on what might be causing such errors? |
Re: elogd crashes during SSL Mirror operations involving attachments, posted by Andreas Warburton on Sat Jan 14 08:27:42 2017
|
For the time being, I am deeming ELOG 3.1.2 unusable with https (SSL = 1) functionality on my "Debian GNU/Linux 7 (wheezy)" server
with "OpenSSL 1.0.1t", due to the described apparent issues with SSL. Reverting to http (SSL = 0) brings back my ability to upload attachments
and synchronize with a remote elogd running on a MacOS laptop. |
|
Re: elogd crashes during SSL Mirror operations involving attachments, posted by Andreas Warburton on Thu Jan 19 12:56:51 2017
|
Further to my comment in https://midas.psi.ch/elogs/Forum/68549, if the described synchronization requires attachment(s) to be transferred from
my Mac laptop to the Debian linux server (with SSL = 0 set), it fails in all the tests that I tried.
To check whether these problems are linked to the OpenSSL version on the linux server, we also tried building an elogd executable using 1.0.2j |
Elog crashing at random intervals, posted by Lee Burnside on Sat Jan 28 22:23:46 2017
|
We're running Elog 3.1.2 om SL 7.2 and keep getting random crashes, sometimes when no one is accessing a logbook. The following is from /var/log/messages
with debugging turned on after the latest crash.
Jan 28 12:43:56 archer elogd[9629]: POST /PHYS3305Spring2017/ HTTP/1.1 |
|
Re: Elog crashing at random intervals, posted by Lee Burnside on Mon Jan 30 12:03:36 2017
|
Never mind, version from github solved issue.
Lee |
Possible misuse of email headers Message-Id and In-Reply-To, posted by fbretel on Wed Feb 8 16:38:15 2017
|
Hi,
As mentionned before, we happen to fail to receive email messages related to updates on
elog entries at our site. My understanding is that the SMTP header Message-Id MUST be unique for each email message. Whereas all elogd email |
|
Re: Possible misuse of email headers Message-Id and In-Reply-To, posted by Stefan Ritt on Wed Feb 8 18:16:30 2017
|
A pull request would be highy appreciated, because you can then test it thoroughly on your side. Adding a random number to the message id is simple.
"Reply-to" indeed does not make sense since elog cannot receive emails. Most sites use a generic "noreply@<domain>" to indicate
to the user that a reply does not make sense. I guess the "Reply-to" does not have to be unique, right? |
|
Re: Possible misuse of email headers Message-Id and In-Reply-To, posted by fbretel on Wed Mar 15 16:04:13 2017
|
| Pull-request posted. Cheers. |