Re: UTC time, posted by Luca on Thu Jan 12 02:35:02 2017
|
Any suggestion?
Luca
wrote:
Dear Steve, |
Re: UTC time, posted by Stefan Ritt on Thu Jan 12 08:28:45 2017
|
The INSERT CURRENT TIME/DATE button is not affected by this setting.
Luca
wrote:
Dear Steve, |
Re: UTC time, posted by Andreas Luedeke on Thu Jan 12 09:10:06 2017
|
Hi Luca,
if you want to change all datetime properties to UTC time, then you'll just need to set the timezone on the server to UTC, before elogd is
started. |
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. |
"No SMTP host defined in [global] section of configuration file", posted by Luca on Wed Jan 18 05:25:44 2017
|
Hi,
I started re-using after a month an elog on my linux machine and, without any apparent reason since I did not used the machine at all in the
last month, every time I try to submit a post I get the following error |
Re: "No SMTP host defined in [global] section of configuration file", posted by Stefan Ritt on Wed Jan 18 10:25:20 2017
|
These problems usually come when you are using a different configuration file that the one you think you are using. Note that you explicitly can tell
elogd to use a specific configuation file with the "-c" flag. Also make sure to restart elogd after major changes.
Luca |
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 |