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. |
Re: Invalid Content-Length in header when running behind a load balancer, posted by Tamas Gal on Wed Jan 25 19:51:29 2023
|
I put the ELOG service behind an Apache reverse proxy which is now sitting behind the HAProxy. It works like this, but it's just a workaround. I
am pretty sure that ELOG has problems to communicate with HAProxy correctly and it seems that Apache is more forgiving. So that the chain HAProxy ->
Apache -> ELOG and vice versa is working. |
|
Re: Invalid Content-Length in header when running behind a load balancer, posted by André on Mon Jul 22 16:30:04 2024
|
I have the same problem. I found a temporary solution: https://elog.psi.ch/elogs/Forum/69807
Tamas
Gal wrote:
I put the ELOG service behind an Apache reverse proxy which is now sitting |
|
Re: Invalid Content-Length in header when running behind a load balancer, posted by Stefan Ritt on Wed Jul 31 14:22:52 2024
|
I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?
Stefan
André |
Redirect in Execute new needs space after ">", posted by Andreas Luedeke on Thu Oct 21 11:00:46 2021
|
EDIT: forget the tip below. Instead just call script files: inline scripting in the ELOG config shows very strange behavior. Doing the same in external
scripts works reliable.
|
"New User" option does not work when Authentication=Webserver, posted by Jan Just Keijser on Fri May 29 09:27:32 2020
|
Our setup uses "Authentication=Webserver" + no automatic user registration. Thus, logbook admins should add a user by clicking "Config"
and then "New user". However, no matter what they fill in in the "new user " dialog, as soon as they hit "Save" an error
pops up saying that their username (the admin one, not the new one) already exists. I found the following code: |
|
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. |
|
Re: SSL does not work, posted by Stefan Ritt on Fri Jun 5 13:24:01 2020
|
When you compile elog from the soruces, you need the OpenSSL library to be installed. The CMake build process will then find it and include it in the
compile process. When you use the "make" build process, you have to make sure that SSL is enabled there:
USE_SSL = 1 |