Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 386 of 808  Not logged in ELOG logo
    icon2.gif   Re: Paid version , posted by Stefan Ritt on Thu Jul 7 10:56:39 2022 
There is only an open source version.




Vasio
wrote:



Good day all ,
    icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 11:13:09 2022 
Probably you need a setting

URL = https://elog.test.km3net.de

or so in your elogd.cfg file.
    icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 11:40:59 2022 
Yeah, after you enter a password, elog redirects to what it finds in "URL". You can trace that by opening "development tools" in
Google Chrome, go to "network" and watch packets going back and forth. I never worked with the load balancer, but maybe you need a different
"URL" containing a '/' at the end?
    icon2.gif   Re: Too many redirects when running behind load balancer?, posted by Stefan Ritt on Tue Jul 19 12:48:42 2022 
Yes I see the redirects. You say with the example logbook it works, right? Is it the password protection which triggers the problem or anything else?
Does it work if you take out the password protection? The key is to identify which setting in your config file triggers the problem, so you can bracket
the problem down between the example logbook and your logbook definition.
    icon2.gif   Re: OSX Issues, posted by Stefan Ritt on Fri Jul 29 14:22:00 2022 
I just tried the same on my latpop (MacOSX 12.4) and it worked flawlessly:

ritt@MBP14 build % echo "blah" | ./elog -h 127.0.0.1 -p 8080 -l demo -r 2 -x
Message successfully transmitted, ID=3
    icon2.gif   Re: Unable to add user, posted by Stefan Ritt on Mon Aug 8 08:26:11 2022 
I recommend to clear all your browser cookies for the elog server. Sometimes an old cookie confuses the
access mechanism.
    icon2.gif   Re: Need help with permission, posted by Stefan Ritt on Mon Sep 26 12:38:29 2022 
Permissions are handled by the operating system and have nothing to do with elog. Make sure you run elog under an account which has write access to the
desired directories. Consult Ubuntu documentation how to do that. Sometimes it's helpful to start elog interactively with the -v flag to see some verbose
output. Maybe you can spot something there.
    icon2.gif   Re: Need help with permission, posted by Stefan Ritt on Mon Sep 26 12:45:50 2022 
Sometimes this can also be an SELinux issue, if you have that service running. Try "journalctl | grep denied" to see denied resources and consult
the SELinux documentation on how to fix that.




Stefan
ELOG V3.1.5-3fb85fa6