Hi,

I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view and post messages. However, if a wrong user/password is provided, the server still returns HTTP status code "200 OK", although login failed. Instead, it should return something like "401 Unauthorized". This behavior later causes problems since the python client thinks login was successful. After experimenting around I think this could be caused by a server side misconfiguration. Any ideas?

I am not sure if this imformation is important: We use LDAP as user/password provider for elog.

Hi,

I have set the options "Restrict edit time = 24" and "Admin restrict edit time = 0" in [global]. This way can only edit entries for 24 hours while the admin can forever. I now want a single logbook where all users have unlimited time to edit entries. However, setting "Restrict edit time = 0" in this specific logbook behaves differently to the admin setting as it simply sets the time to 0. Is this behavior intended or a bug? I guess a workaround is to specify the edit limitation not in global but in all logbooks seperately.

Hi Chris,

my old entry was related to the admin options of edit time.
The option "Admin restrict edit time" was implemented later, see ab8b98c

As a workaround you should be able to give "Restrict edit time" a ridiculous high number in the specific logbook, which should overwrite the global.
In the documentation is no rule specified for diabling global settings for specific logbooks, as far as i know.

Best wishes,
Sebastian

Hi,

In our setup we have multiple logbooks. I want a convenient way to search all logbooks for an attribute (in our case with the name Sample-ID) by just clicking it in the list display of any logbook.Therefore, in the [global] section I put "List Change Sample-ID = <a href="https://ourelog.com/$logbook/?all=1&Sample-ID=$Sample-ID"</a>. This transforms the attribute in list display into a hyperlink to the search results page. So far this works fine. In the results page, of course the option also applies, meaning the attribute is replaced by the link as well. But here something odd happens and the replacement does not work. The intended behavior is to replace $logbook in the link with the name of the logbook. Sometimes, however, the replacement yields something like "logbook" (missing $ and thus not replacing anything) or even weirder something like "60logbook". I have no idea what causes this.

I am on ubuntu 24.04.1, I needed to git clone, make and make install,

HEAD is 3fb85fa6 - (HEAD -> master, origin/master, origin/HEAD) Fixed compiler warning (3 weeks ago)

It crashes on every attachment:  thank you. Jaro

root@vaio:~# systemctl status elogd
× elogd.service - The ELOG Server
     Loaded: loaded (/usr/lib/systemd/system/elogd.service; enabled; preset: ena>
     Active: failed (Result: core-dump) since Thu 2024-09-12 10:39:23 CEST; 3s a>
   Duration: 5.402s
       Docs: man:elogd(8)
             man:elog(8)
    Process: 724285 ExecStart=/usr/local/sbin/elogd -D -c /usr/local/elog/elogd.>
   Main PID: 724286 (code=dumped, signal=ABRT)
        CPU: 32ms

Sep 12 10:39:18 vaio systemd[1]: Starting elogd.service - The ELOG Server...
Sep 12 10:39:18 vaio elogd[724286]: elogd 3.1.5 built Sep 11 2024, 17:02:36
Sep 12 10:39:18 vaio elogd[724286]: revision 3fb85fa6
Sep 12 10:39:18 vaio elogd[724286]: File "/var/run/elogd.pid" exists, overwritin>
Sep 12 10:39:18 vaio systemd[1]: Started elogd.service - The ELOG Server.
Sep 12 10:39:18 vaio elogd[724286]: CKeditor detected
Sep 12 10:39:18 vaio elogd[724286]: ImageMagick detected
Sep 12 10:39:18 vaio elogd[724286]: Server listening on port 9000 ...
Sep 12 10:39:23 vaio systemd[1]: elogd.service: Main process exited, code=dumped>
Sep 12 10:39:23 vaio systemd[1]: elogd.service: Failed with result 'core-dump'.
root@vaio:~# systemctl restart elogd