login cookie confusion, posted by Konstantin Olchanski on Wed Mar 2 18:35:48 2022
|
we had an elog with only one logbook and one password file,
we added a second logbook with a second password file and everything broke.
|
elog c++ and LDAP, posted by Laurent Jean-Rigaud on Wed Feb 16 22:24:18 2022
|
Hi Stefan,
I've seen that ELOG is build now with gcc-c++ now, so i tried to check rpmbuild script with all options. It seems that ldap api is different
with c++ (quick search : https://www.openldap.org/lists/openldap-software/200706/msg00177.html) and elogd can not been build anymore with ldap support. |
|
make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 8 00:52:47 2022
|
For the record, compiler messages from elog tip of branch elog/master.
Most of the stuff is the usual same-old that we mostly fixed in midas:
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Tue Feb 8 09:14:25 2022
|
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a
> destination of size 4096
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Tue Feb 15 13:45:02 2022
|
Well, I bit the bullet and fixed all of these warnings. Took me like two days of work, but now should be fine. You might want to test it again. I only have
gcc 9.2.0, there it compiles now without warning.
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 15 20:55:02 2022
|
> Well, I bit the bullet and fixed all of these warnings. Took me like two days of work, but now should be fine.
> You might want to test it again.
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Wed Feb 16 08:45:15 2022
|
I fixed these as well, please have a look again. BTW, midas had a few of these as well.
Stefan |
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Wed Feb 16 20:01:17 2022
|
> I fixed these as well, please have a look again. BTW, midas had a few of these as well.
confirmed. elog commit d828aa58305ee8ce2ae882c0ff3c34cfa66650e5
|
|
ELOG problems with certificates, posted by Ezio Zanghellini on Thu Feb 10 19:03:56 2022
|
Recently I have had problems with ELOG not accepting the certificates (in this case from https://letsencrypt.org/)
probably due to the old version of the SSL library of the binary distribution for Windows.
I have tried to follow the instructions to set up ELOG to work with Apache but they are probably old. |
|
"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: |
|
Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Tue Aug 4 13:29:23 2020
|
Unfortunately I locallly don't have Webserver authentication, so I cannot check or debug. If you send me a diff that works for you, I'm happy
to incorporate it.
Stefan |
Re: "New User" option does not work when Authentication=Webserver, posted by Jan Just Keijser on Wed Aug 18 09:05:51 2021 
|
here's the patch that I use to enable use creation and deletion in combination with Webserver authentication.
The idea behind the patch is that if the user logged in via "http_user" is an elog admin, then {s}he is allowed to save a random
user configuration, including creating or deleting a user. |
|
Re: "New User" option does not work when Authentication=Webserver, posted by Stefan Ritt on Thu Feb 10 17:32:42 2022
|
Thanks for your patch, I committed it.
Stefan |
Password File Config Issue, posted by Mark Delaney on Fri Feb 4 23:35:27 2022
|
I expanded an elog server from 1 to 3 logbooks. For each logbook there is a separate password file defined.
When I try to add a new user in one of the 2 new logbooks using config => new user, it adds the user to the password file for the original
logbook. |
|
Re: Password File Config Issue, posted by Stefan Ritt on Thu Feb 10 14:02:15 2022
|
Can you try the "top groups" option, which means putting each logbook into a separate top group as described in the documentation. For us this
works well, new users are only added to the right password file. There is however the problem that as admin you might be logged in to several logbooks
(as remembered in your browser via cookies), so you might want to log out from all logbooks first (or clear all cookies of elog), then log in to one logbook |
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. |
|
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 |
|
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 |
|
elog@Ubuntu 18.04, posted by Carsten Winkler on Sat Jan 29 09:05:47 2022
|
Hello,
I try to start elog at Ubuntu 18.04. When I run sudo /usr/local/sbin/elogd -D -c /usr/local/elog/elogd.cfg I
get following error: |
|
Re: elog@Ubuntu 18.04, posted by Stefan Ritt on Mon Jan 31 09:10:41 2022
|
Looks like you don't have shared libraries correctly configured on your system. Try "ldconfig" on your system or link elogd statically
(google how to do that).
Stefan |
|
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? |
|
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 |