| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
Text |
 |
|
69155
|
Fri Jun 5 13:24:01 2020 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.4-2 | Re: SSL does not work | When you compile elog from the soruces,
you need the OpenSSL library to be installed.
The CMake build process will then find it |
|
|
69160
|
Thu Jun 11 08:23:01 2020 |
| Hisataka YOSHIDA | hisataka@rcnp.osaka-u.ac.jp | Bug report | Linux | 3.1.4-2 | Re: SSL does not work | Dear Stefan,
Thank you for your comment. I successfuly
compiled the latest elog from source code, |
|
|
69192
|
Tue Aug 4 13:29:23 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.4-2 | Re: "New User" option does not work when Authentication=Webserver | Unfortunately I locallly don't have
Webserver authentication, so I cannot check
or debug. If you send me a diff that works |
|
|
69205
|
Wed Aug 26 20:41:50 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.4-2 | Re: SSL does not work | Today I succeeded with the help of L.JR
to produce a new RPM which contains SSL,
KRB5, PAM and LDAP support. It's uploaded |
|
|
69238
|
Tue Oct 20 16:05:40 2020 |
 | Bruno Schuler | bruno.schuler@empa.ch | Question | Windows | 3.1.4-2 | Upload attachment with py_elog | Hello,
How can one add an attachment to
a new or existing entry with py_elog? |
|
|
69300
|
Thu Feb 18 09:14:28 2021 |
| Stefano Lacaprara | stefano.lacaprara@pd.infn.it | Bug report | Linux | 3.1.4-2 | elog server go to high CPU and hangs | Dear expert,
I'm running the latest git version of elog
ELOG V3.1.4-395e101a on ubuntu 20.04.2.
|
|
|
69301
|
Thu Feb 18 12:05:52 2021 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 3.1.4-2 | Re: elog server go to high CPU and hangs | Dear Stefano,
Try the entry I wrote some time ago elog:68655
|
|
|
69302
|
Thu Feb 18 12:06:12 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.4-2 | Re: elog server go to high CPU and hangs | Usually a restart of the elogd server helps.
If the problem persists, one of the logbooks
might be corrupt. Try to disable one logbook |
|