Step by step AD/Kerberos authentication setup, posted by Gys Wuyts on Fri May 26 13:51:16 2023
|
Newby/noob Q: anybody have a resource other then the orignal doc on how to get ELog working using the domain users/passwords with a Win2K19 AD ?
thanks
|
Reverse proxy setting of Elog for Apache httpd 2.4 so that changing password windows works ?, posted by Takashi Ichihara on Tue Mar 19 06:13:03 2019
|
In CentOS 7.6 + Apache httpd-2.4.6 + ELOG V3.1.4 environment with Reverse Proxy setting of
/etc/httpd/conf/httpd.conf
: |
Re: Reverse proxy setting of Elog for Apache httpd 2.4 so that changing password windows works ?, posted by Takashi Ichihara on Tue Mar 26 06:41:21 2019
|
The problem was resolved. I forgot to do this statement...
https://elog.psi.ch/elog/adminguide.html
Because elogd uses links to itself (for example in the email notification and the redirection after a submit), it has to know under which URL it |
Too many open files - issue?, posted by Rob Calkins on Fri Oct 15 23:57:38 2021
|
Has anyone had issues with having too many files open? I'll setup my server and let it go but after a while, I end up with a lot of "cannot
create socket: Too many open files" errors being reported. I have a sync to another e-log going which I suspect is part of the cause since that
e-log server hasn't had this issue. I suspect that there are files being opened, going into some return loop code and then never getting closed. I'm |
Re: Too many open files - issue?, posted by Stefan Ritt on Mon Oct 25 13:34:06 2021
|
The code segements you show are from the command line tool elog.c, not the server elogd.c. The tool is called to submit a new message from the command
line. Even if there would be a file not properly closed, it will be closed by the operating system once the program finishes. So no problem of too many
open files there. |
Mirror synchronization and file servers, posted by Frank Baptista on Fri Mar 1 19:18:53 2019
|
We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each. Using the mirror
feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks. All of that
works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive. |
Re: Mirror synchronization and file servers, posted by Stefan Ritt on Mon Mar 4 13:35:13 2019
|
Sounds really strange to me. The remote server does not "know" that "S:\" is a network drive, so the syncing process should work
exactly as before. The only idea I have is that the access to the network files take pretty long, and you run into a timeout during syncing. We had this
in the past (for AFS netwhor shares, not Windows shares), where sometimes we have a blocking behaviour where the file access lasted 10-20 seconds, and |
Very long URLs in message list corrupt layout, posted by Ederag on Sun Mar 10 01:07:53 2019
|
First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.
When there is a very long URL in a message in "plain" encoding, |