| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
Text |
 |
|
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
|
|
|
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.
|
|
|
69299
|
Wed Feb 3 17:28:16 2021 |
| Gabriel Lopez | gabelopez@bnl.gov | Bug report | Linux | 3.1.4 | Re: Path disclosure on unfound file | Hello, This is coming up as a high vulnerability
in our scans. Are there plans to update the
rpm for this fix? If so is there an ETA? |
|
|
69298
|
Tue Feb 2 08:25:46 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.4 | Re: Different Top Groups or Groups have the same logbook name | That's correct.
|
|
|
69297
|
Tue Feb 2 08:17:15 2021 |
| MATT TERRON | matao11235@gmail.com | Question | Linux | Windows | 3.1.4 | Re: Different Top Groups or Groups have the same logbook name | So both Top Group names and Logbook
names should be unique inside one .cfg file,
is that correct? |
|
|
69296
|
Tue Feb 2 07:43:49 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.4 | Re: Different Top Groups or Groups have the same logbook name | Unfortunately you have to name these top
groups differently, because they are internally
used for the database name. |
|
|
69295
|
Tue Feb 2 04:01:21 2021 |
| MATT TERRON | matao11235@gmail.com | Question | Linux | Windows | 3.1.4 | Different Top Groups or Groups have the same logbook name | I have built different top groups for different
departments. But occasionally these different
top groups have the same logbook name, say |
|
|
69294
|
Thu Jan 14 14:05:19 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: elog slowness | Have you tried to restart the elogd server?
The CLOSE_WAIT could be dangling network
connections, which were not properly closed |
|