SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Stefan Ritt on Wed Nov 8 08:20:34 2006
|
[quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings common to all logbooks[/CODE]
is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking
"[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8), posted by Steve Jones on Wed Nov 8 12:55:58 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]BUG: In the initial comment section of elogd_fancy.cfg the line [CODE]# This [global] section contains settings
common to all logbooks[/CODE] is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup
the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine |
|
SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode, posted by Stefan Ritt on Wed Nov 8 13:07:31 2006
|
[quote="Steve Jones"]Very weird. No, I did not try an absolute path - but I did notice the attempt to "cd /" in the truss output. In fact, it was immediately
after that "cd /" test that things appeared to start not working - basically, elogd could not find anything.[/quote]
|
SVN1714 will not run in 'daemon" mode on Solaris8, posted by Steve Jones on Mon Sep 18 20:35:44 2006 
|
On Solaris, SVN1714 will not go into daemon mode. Running the compiled version under TRUSS (which provides a dump of every system call) and shows precisely
where elog is failing. I have attached two TRUSS outputs: one where it errors out and the other where it runs but "interactively". Both runs are as root,
simply one with and one without the "-D" |
SSL does not work, posted by Hisataka YOSHIDA on Fri Jun 5 03:49:20 2020
|
Hello.
I installed the latest elog (3.1.4-2) in CentOS 7, and it is working well without SSL.
When I enalbled SSL option (SSL = 1) in the "elogd.cfg", and tried to start the elogd, the message below was shown and failed to run. |
SSL connection drop with large content, posted by HyonSan Seo on Mon Aug 10 07:56:43 2020
|
Dear all,
I had some difficulty to upload large files (>20MB) with SSL connection. I think it is also related to https://elog.psi.ch/elogs/Forum/68636 |
SSL, posted by Thomas Kleeb on Wed Apr 11 16:32:22 2012
|
I'm slowly able to see the finish line
Now all I need to do is get SSL to work. My server name is hf-info-elog and I'm not sure what the correct values for Port= and URL= should be.
thank |
SSL, posted by Chris Smyth on Thu Aug 4 14:28:18 2016
|
How do I enable SSL with port 443 in version ELOG V2.7.8-2294 and
rename from localhost?
Server is running Windows 2008 |