Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 3 of 801  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject
  69819   Mon Aug 5 20:45:15 2024 Question Truupepijuels@gmail.comQuestionOther3.1.5Elog on FreeBSD

Anyone using elog on FreeBSD nowadays?  I know it used to be in the ports tree about 10 years ago but seems to be abandoned.  Tried to compile from source on 14.1, but no luck there.

  69818   Wed Jul 31 14:22:52 2024 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.4-3Re: Invalid Content-Length in header when running behind a load balancer

I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?

Stefan

André wrote:

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 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.

If anyone manages to figure out what's wrong, I am happy to get rid of the extra reverse proxy layer!

Tamas Gal wrote:

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.

With the new version 3.1.4-3, I get another error: "Invalid Content-Length in header" when I click on "submit" of a new post. Viewing the logbooks works fine. The instance is currently live and running here: https://elog.test.km3net.de but I might change it anytime due to debugging etc.

This is a kind of difficult thing to debug (I spent the whole day and no progress). The only thing I've found was this post: https://techcommunity.microsoft.com/t5/iis-support-blog/invalid-content-length/ba-p/3038724 where it seems that some responses are not RFC conform and were rejected in the load-balancer.

The load balancer I use is HAProxy, the same as in my old setup where I got the infinite redirects, and I can't find any setting which would work. To my understanding, the most basic setup should work just fine. The SSL termination is on the load-balancer side so ELOG doesn't even have to know anything about it. The configuration is below. I am running a single instance, so there is not even replication with session keep-alive via cookies or anything fancy.

I also want to mention that I am runnin around 30 different services behind the load balancer and none of them are having any issues with the SSL termination or the load-balancing itself, that's why assume that something in ELOG is either non-conform or buggy.

Any thoughts? I'd really like to use the same infrastructure for the ELOG service as for every other service (automatic certificate renewal via letsencrypt, load-balancing, easy movement to other nodes, SSL termination etc.), to minimise the complexity of our Docker Swarm system.

backend be_elog.km3net.de
    mode http
    server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none

 

Btw. I am running ELOG with -v but I don't see any error whatsoever in the logs:

km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "ios_specific_templates_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "rl_anonymous_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "rl_group_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "rl_group_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "rl_trait"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "rl_user_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Received unknown cookie "logged_out_marketing_header_id"
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Returned 3437 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Returned 3518 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | GET / HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Returned 120 bytes
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | GET /demo/ HTTP/1.1
km3net-elog_elog.1.fm8i1eia9l9t@ecap-s021    | Returned 3518 bytes

 

 

 

  69817   Wed Jul 31 14:21:21 2024 Reply Stefan RittI cstefan.ritt@psi.chBug reportAll3.1.5Re: HTTP headers should be parsed case insensitive

I changed elog to interprete the content-length header case in-sensitive and committed the change. Can you try again?

Stefan

André wrote:

I'm trying to run elog behind haproxy, but get the error "Invalid Content-Length in header" on posting.

As stated in the manual, haproxy rewrites all headers to lower case.

elogd parses the content-length header case sensitive which is against the HTTP RFC. This might also apply to other headers that get parsed.

For now I'm using the workaround from the manual:

global
  h1-case-adjust content-length Content-Length
  h1-case-adjust content-type Content-Type

backend elog
  option h1-case-adjust-bogus-server
  server elog 127.0.0.1:8080

But as the manual states, this should not be  used as a permanent solution.

 

  69816   Fri Jul 26 14:33:50 2024 Reply Carl Unsworthcarl.unsworth@stfc.ac.ukBug reportLinuxV3.1.5-23df00dRe: Old attachments erroneously appearing on new Elog entries.

Great, thank you again. I have now installed the latest and the problem appears to be gone.

Stefan Ritt wrote:

I updated the EL9 rpms, so please try again.

 

  69815   Fri Jul 26 14:09:19 2024 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.5-23df00dRe: Old attachments erroneously appearing on new Elog entries.

I updated the EL9 rpms, so please try again.

  69814   Fri Jul 26 13:14:38 2024 Reply Carl Unsworthcarl.unsworth@stfc.ac.ukBug reportLinuxV3.1.5-23df00dRe: Old attachments erroneously appearing on new Elog entries.

Thanks very much for the quick response Stefan. My apologies, I thought I was on the latest version or I would have upgraded before contacting you.
The file I installed from was the rpm "elog-3.1.5-20240226.el9.x86_64.rpm" which still seems to be the latest version on the Dropbox downloads page.
Do I need to use the tar distribution to get the latest?

Stefan Ritt wrote:

This bug has been fixed in meantime, please upgrade to the current version.

 

  69813   Fri Jul 26 13:01:54 2024 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.5-23df00dRe: Old attachments erroneously appearing on new Elog entries.

This bug has been fixed in meantime, please upgrade to the current version.

  69812   Fri Jul 26 12:53:23 2024 Question Carl Unsworthcarl.unsworth@stfc.ac.ukBug reportLinuxV3.1.5-23df00dOld attachments erroneously appearing on new Elog entries.

Hi, I'm not sure if this is an Elog bug, something wrong in my configuration/database.

When I create a new article on Elog it always shows an attachment from one of the first entries ever made to this log book made. This is in addition to any attachments which were actually added during article creation.

I just made an example entry to demonstrate. First attachment here shows how the entry looks in the GUI, it has an attached text file called "jail.local", 2nd attachment is how that entry looks in the database file - no attachment.

Does anyone have any idea what's happening?

Attachment 1: Screenshot_from_2024-07-26_11-46-44.png
Screenshot_from_2024-07-26_11-46-44.png
Attachment 2: Screenshot_from_2024-07-26_11-47-58.png
Screenshot_from_2024-07-26_11-47-58.png
ELOG V3.1.5-3fb85fa6