Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 173 of 808  Not logged in ELOG logo
    icon2.gif   Re: elog@Ubuntu 18.04, posted by Carsten Winkler on Tue Feb 1 09:13:40 2022 
sudo ldconfig didn't solve the problem


Is there any other solution than elog static linking?
icon3.gif   Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 15:39:38 2022 
what is the default value for "Author" when replying to a log entry ?  I now see that for each reply to a log entry, the value of "Author"
is set to the value of the author of the original entry - this makes it very hard to see which user has replied to a particular log entry, especially when
users start replying to replies etc.
    icon2.gif   Re: Default "Author" when replying to a log entry, posted by Stefan Ritt on Tue Feb 1 15:43:00 2022 
As you can see, on this forum the author for replies is correct. This is done via the config option:

Preset on reply Author = $long_name




Jan
    icon2.gif   Re: elog@Ubuntu 18.04, posted by Carsten Winkler on Tue Feb 1 16:16:34 2022 
downloading the sources and building them on the target system solved the problem




Carsten
Winkler wrote:



sudo ldconfig
    icon2.gif   Re: Default "Author" when replying to a log entry, posted by Jan Just Keijser on Tue Feb 1 16:43:34 2022 
Excellent, exactly what I was looking for, many thanks!

 




Stefan
icon1.gif   Need help with permission, posted by Dan Witteman on Fri Sep 23 01:32:15 2022 
Hello,

I have just installed elog onto an ubuntu focal server using <sudo make install> and I am unable to create new entries.

When I access the log via a windows PC connected to the local network, I can see the demo logbook with the 1 test post, but I cannot create or
icon4.gif   Invalid Content-Length in header when running behind a load balancer, posted by Tamas Gal on Wed Jan 25 14:36:33 2023 Screenshot_2023-01-25_at_14.46.05.png
I am still struggling to get ELOG running behind a load balancer and hope to get some advice here. As already reported in https://elog.psi.ch/elogs/Forum/69542 I
observed an infinite loop of redirects when prompted to log in and using a non-empty password file. Without a password, the service worked as
expected. This was with version 3.1.3.
icon5.gif   Upload via command line through Apache reverse proxy and load balancer, posted by Tamas Gal on Wed Jan 25 18:41:27 2023 
After fiddling around I managed to get ELOG working behind the load balancer HAProxy by stacking ELOG together with an Apache reverse proxy in a Docker
stack. I am currently pretty convinced that something with the HTTP communication is somehow faulty in ELOG and Apache is more forgiving than HAProxy,
since the configuration is the same as without Apache. So putting ELOG behind an Apache and then Apache behind the HAProxy is working.
ELOG V3.1.5-3fb85fa6