Re: Parsing log files, posted by Stefan Ritt on Fri Jan 8 15:35:35 2021
|
Well, you could put the old options back to the config file, do the export, then remove them again.
But have a look at the Elog database files ZZMMDDa.log in your logbook directory, they are pure ASCII files, which are relatively simple to parse.
Hi |
|
Re: elog slowness, posted by Stefan Ritt on Thu Jan 14 14:05:19 2021
|
Have you tried to restart the elogd server? The CLOSE_WAIT could be dangling network connections, which were not properly closed by the browser.
Giuseppe
Cucinotta wrote:
We run elog on a server to provide a logbook for our laboratory. |
|
Re: Different Top Groups or Groups have the same logbook name , posted by Stefan Ritt on Tue Feb 2 07:43:49 2021
|
Unfortunately you have to name these top groups differently, because they are internally used for the database name.
MATT
TERRON wrote:
I have built different top groups for different departments. But occasionally |
|
Re: Different Top Groups or Groups have the same logbook name , posted by MATT TERRON on Tue Feb 2 08:17:15 2021
|
So both Top Group names and Logbook names should be unique inside one .cfg file, is that correct?
Stefan
Ritt wrote:
Unfortunately you have to name these top groups differently, because |
|
Re: Different Top Groups or Groups have the same logbook name , posted by Stefan Ritt on Tue Feb 2 08:25:46 2021
|
That's correct.
Stefan
Ritt wrote:
Unfortunately you have to name these top groups differently, because |
|
Re: Path disclosure on unfound file, posted by Gabriel Lopez on Wed Feb 3 17:28:16 2021
|
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? Any update would
be much appreciated. Currently running elog-3.1.4-2
Stefan |
|
Re: elog server go to high CPU and hangs, posted by David Pilgram on Thu Feb 18 12:05:52 2021
|
Dear Stefano,
Try the entry I wrote some time ago elog:68655
|
|
Re: elog server go to high CPU and hangs, posted by Stefan Ritt on Thu Feb 18 12:06:12 2021
|
Usually a restart of the elogd server helps. If the problem persists, one of the logbooks might be corrupt. Try to disable one logbook at a time to figure
out which one it is. Then
remove that one and set it up freshly.
|