ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69547
|
Tue Jul 19 12:36:04 2022 |
| Tamas Gal | tgal@km3net.de | Question | Linux | 3.1.3 | Re: Too many redirects when running behind load balancer? | My problem is that I don't even reach the page where I can enter a password. If you go to https://elog.test.km3net.de and click on a logbook, you'll see that it immediately goes into a redirect loop. I already logged the routing but there is nothing else...
Stefan Ritt wrote: |
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?
Tamas Gal wrote: |
I also tried the default configuration (example config) and it that works behind the load balancer. So I guess it's related to the password-page, which causes this redirect loop? Our logbooks are all password protected, so when a logbook URL is clicked, it should first present the login-form, and that's where it chokes.
|
|
|
69546
|
Tue Jul 19 11:40:59 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: Too many redirects when running behind load balancer? | 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?
Tamas Gal wrote: |
I also tried the default configuration (example config) and it that works behind the load balancer. So I guess it's related to the password-page, which causes this redirect loop? Our logbooks are all password protected, so when a logbook URL is clicked, it should first present the login-form, and that's where it chokes.
|
|
69545
|
Tue Jul 19 11:24:36 2022 |
| Tamas Gal | tgal@km3net.de | Question | Linux | 3.1.3 | Re: Too many redirects when running behind load balancer? | I also tried the default configuration (example config) and it that works behind the load balancer. So I guess it's related to the password-page, which causes this redirect loop? Our logbooks are all password protected, so when a logbook URL is clicked, it should first present the login-form, and that's where it chokes. |
69544
|
Tue Jul 19 11:17:44 2022 |
| Tamas Gal | tgal@km3net.de | Question | Linux | 3.1.3 | Re: Too many redirects when running behind load balancer? | Thanks for the quick reply! Sorry, I forgot to paste the "global" part of the config, I have that URL already set:
[global]
;Main Settings
;=============
Usr = elog
Grp = elog
port = 8080
SSL = 0
URL = https://elog.test.km3net.de
Title image = <img border=0 src="KM3NeT_logo.png" alt="KM3NeT logo" height="35px">
;SMTP host = smtp.fau.de
Display mode = summary
Thumbnail size = 500>
List Menu text = clock.html
Menu text = clock.html
Stefan Ritt wrote: |
Probably you need a setting
URL = https://elog.test.km3net.de
or so in your elogd.cfg file.
Stefan
|
|
69543
|
Tue Jul 19 11:13:09 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: Too many redirects when running behind load balancer? | Probably you need a setting
URL = https://elog.test.km3net.de
or so in your elogd.cfg file.
Stefan
Tamas Gal wrote: |
We were running ELOG for many many years in our experiments and the instance was operated on a Debian XEN server as a container. I am now trying to migrate it into our Docker Swarm cluster and I am using the https://hub.docker.com/r/de1lz/elog-docker Docker image, which works very well with our logbooks when I run it as a single container. However, when I put the container behind my load balancer (HAProxy) using the simple HTTP mode (which works very well for all the other HTTP-based services) with this simple configuration:
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
I get a "too many redirects" error when I try to access one of the logbooks. The starting page works fine, but every other link leads to a pile-up of redirects.
Here is the current instance running, where you can see the behaviour: https://elog.test.km3net.de (all log entries deleted and only two logbooks activated)
My question is: what kind of redirect could go wrong here? I don't know how the internal HTTP server of ELOG works, but maybe someone faced similar issues.
My ELOG configuration is also pretty basic, and as I wrote above, everything works when I run it without the load balancer (single instance at the moment). Here is the top part of the configuration, it contains a few dozens of logbooks but they are configured the very same way.
;User Settings
;=============
Password file = login.xml
Admin user = km3net_admin
Self register = 0
Allow password change = 0
Allow config = km3net_admin
;Group Settings:
;====
Group ELOGKM3NET = Operations IT, Operations FR
[Operations IT]
Subdir = Operations_IT
Theme = default
Default encoding = 0
Comment = KM3NeT IT Detector Operations
Attributes = Author, Type, Subject
Options Author = A, B, C
Options Type = PPM-DOM, PPM-DU, Comment, Power cut, New run
Extendable Options = Type
Required Attributes = Author, Type, Subject
Page Title = ELOG - $subject
;Sort Attributes = Author, Type
Quick filter = Date, Type, Author
Resubmit default = 2
Reverse sort = 1
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Help, Logout
Preset on first reply Subject = Re: $Subject
Preset on reply author =
|
|
69542
|
Tue Jul 19 11:01:00 2022 |
| Tamas Gal | tgal@km3net.de | Question | Linux | 3.1.3 | Too many redirects when running behind load balancer? | We were running ELOG for many many years in our experiments and the instance was operated on a Debian XEN server as a container. I am now trying to migrate it into our Docker Swarm cluster and I am using the https://hub.docker.com/r/de1lz/elog-docker Docker image, which works very well with our logbooks when I run it as a single container. However, when I put the container behind my load balancer (HAProxy) using the simple HTTP mode (which works very well for all the other HTTP-based services) with this simple configuration:
backend be_elog.km3net.de
mode http
server-template km3net-elog- 1 km3net-elog_elog:8080 check resolvers docker init-addr libc,none
I get a "too many redirects" error when I try to access one of the logbooks. The starting page works fine, but every other link leads to a pile-up of redirects.
Here is the current instance running, where you can see the behaviour: https://elog.test.km3net.de (all log entries deleted and only two logbooks activated)
My question is: what kind of redirect could go wrong here? I don't know how the internal HTTP server of ELOG works, but maybe someone faced similar issues.
My ELOG configuration is also pretty basic, and as I wrote above, everything works when I run it without the load balancer (single instance at the moment). Here is the top part of the configuration, it contains a few dozens of logbooks but they are configured the very same way.
;User Settings
;=============
Password file = login.xml
Admin user = km3net_admin
Self register = 0
Allow password change = 0
Allow config = km3net_admin
;Group Settings:
;====
Group ELOGKM3NET = Operations IT, Operations FR
[Operations IT]
Subdir = Operations_IT
Theme = default
Default encoding = 0
Comment = KM3NeT IT Detector Operations
Attributes = Author, Type, Subject
Options Author = A, B, C
Options Type = PPM-DOM, PPM-DU, Comment, Power cut, New run
Extendable Options = Type
Required Attributes = Author, Type, Subject
Page Title = ELOG - $subject
;Sort Attributes = Author, Type
Quick filter = Date, Type, Author
Resubmit default = 2
Reverse sort = 1
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Help, Logout
Preset on first reply Subject = Re: $Subject
Preset on reply author =
|
69541
|
Thu Jul 7 10:56:39 2022 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Windows | 3.1.3 | Re: Paid version | There is only an open source version.
Vasio wrote: |
Good day all ,
does Elog has a paid version that is not open soureced
regards
William Vasio
|
|
69540
|
Tue Jul 5 19:10:48 2022 |
| Florian Heigl | me@florianheigl.me | Question | Mac OSX | 3.1.4 | OSX Issues | Hi, I have an issue with my local elog setup. it's usable but one function is just not working.
Problem
I'm getting weird error messages when trying to write or read entries from the CLI client.
I have googled a lot and most elog client examples are not giving the actual output, more like elog -h <host> -p <myport> -a ... -x -m "myfile" but I hope I got the options right.
Upgrading did not change the behaviour.
Question?
- anyone see problems in the commands I tried below
- with OSX in general
- have a recent setup on OSX that just works
Env
I'm running elog on my OSX laptop for tracking issues / improvements on client's IT systems. It's proven really good for storing my notes.
One "kink" is I kinda need both of them on the laptop since I cannot assume to have working network connectivity, i.e. when documenting network outages or datacenter maintenance where everything is off.
One thing I couldn't get to work was the CLI. Today I upgraded to the latest build, and tried again.
Env: OSX 12.4 (x86_64)
elog Client compiled from latest source tree (bcd7b50edd3d687425e6c5b0906dc02c8690a24e)
with minimal adjustments (turn off SSL since I can't get it right on OSX, rename two .c files in mxml to .cxx)
Outputs
$ echo "blah" | ./elog -h 127.0.0.1 -p 8080 -l intern -r 2 -x
Cannot retrieve host name: Undefined error: 0
$ echo "blah" | ./elog -h 127.0.0.1 -p 8080 -l intern -r 2 -x
Cannot retrieve host name: Undefined error: 0
$ host 127.0.0.1
1.0.0.127.in-addr.arpa domain name pointer localhost.
$ elog -?
elogd 3.1.4 built Oct 8 2020, 03:14:21 revision 7c3fd00b
$ elog -?
elogd 3.1.4 built Jul 5 2022, 18:23:30 revision bcd7b50e
As per the messages, I'm not entirely sure if it's an issue with the client or the server. upgrading both components made no difference.
Config
Theme = default
Comment = Logbuch Findings etc
Attributes = Context, Type, Category, Subject, ObjectPath
Options Context = global, intern, [redacted]
Options Type = Anpassung, Finding, Problem, Update, Auftrag, Planung
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Context, Type, ObjectPath
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Context, Type
make output
$ gmake
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -I/opt/local/include -o elog src/elog.cxx mxml.o crypt.o -L/opt/local/lib
ld: warning: directory not found for option '-L/opt/local/lib'
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -I/opt/local/include -w -c -o auth.o src/auth.cxx
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -I/opt/local/include -o elogd src/elogd.cxx auth.o mxml.o crypt.o -L/opt/local/lib
ld: warning: directory not found for option '-L/opt/local/lib'
c++ -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -Wno-unused-result -Imxml -I/opt/local/include -o elconv src/elconv.cxx -L/opt/local/lib
ld: warning: directory not found for option '-L/opt/local/lib'
$ ls -ltr
[...]
-rw-r--r-- 1 floh staff 4811 5 Jul 17:58 CMakeLists.txt
drwxr-xr-x 25 floh staff 800 5 Jul 17:58 doc
drwxr-xr-x 10 floh staff 320 5 Jul 17:58 scripts
drwxr-xr-x 13 floh staff 416 5 Jul 17:58 src
drwxr-xr-x 10 floh staff 320 5 Jul 18:15 mxml
-rw-r--r-- 1 floh staff 36424 5 Jul 18:15 mxml.o
-rw-r--r-- 1 floh staff 8784 5 Jul 18:15 crypt.o
-rw-r--r-- 1 floh staff 5886 5 Jul 18:23 Makefile
-rwxr-xr-x 1 floh staff 90840 5 Jul 18:23 elog
-rw-r--r-- 1 floh staff 2976 5 Jul 18:23 auth.o
-rwxr-xr-x 1 floh staff 1390664 5 Jul 18:23 elogd
-rwxr-xr-x 1 floh staff 52112 5 Jul 18:23 elconv
$ sudo gmake install
Password:
install: elog -> /usr/local/bin/elog
install: elconv -> /usr/local/bin/elconv
install: elogd -> /usr/local/sbin/elogd
install: man/elog.1 -> /usr/local/man/man1//elog.1
install: man/elconv.1 -> /usr/local/man/man1//elconv.1
install: man/elogd.8 -> /usr/local/man/man8//elogd.8
install: scripts/ckeditor-config.js -> /usr/local/elog/scripts//ckeditor-config.js
install: scripts/dnd.js -> /usr/local/elog/scripts//dnd.js
install: scripts/elcode.js -> /usr/local/elog/scripts//elcode.js
install: scripts/im.js -> /usr/local/elog/scripts//im.js
install: scripts/jquery-1.11.1.min.js -> /usr/local/elog/scripts//jquery-1.11.1.min.js
install: scripts/load-ckeditor.js -> /usr/local/elog/scripts//load-ckeditor.js
Installing CKeditor to /usr/local/elog/scripts/ckeditor
Installing resources to /usr/local/elog/resources
Installing themes to /usr/local/elog/themes
Installing example logbook to /usr/local/elog/logbooks/demo
install: logbooks/demo/2001/011108a.log -> /usr/local/elog/logbooks/demo/2001/011108a.log
install: elogd.plist -> /Library/LaunchDaemons/ch.psi.elogd.plist
The elogd service can now be started with
sudo launchctl load /Library/LaunchDaemons/ch.psi.elogd.plist
|
|