Last default time bug, posted by Sebastian Schenk on Mon Mar 1 16:02:02 2021
|
Hello all,
I have the issue, that we can't list entries older than 1 year, if "Last default = 31" (or any other number, but
they are restricted to 1, 3, 7, 31, 92, 182, 364) is active. |
Path disclosure on unfound file, posted by Bruce Bush on Wed May 6 17:35:14 2015
|
Greetings,
Running elog 3.1.0 on CentOS 6.6. When I try to access a nonexistent file, elog reveals a path in the 404 page. For example:
Not Found
The requested file /usr/local/elog/themes/default/blortblortblort7854.htm |
Re: Path disclosure on unfound file, posted by Stefan Ritt on Wed Jun 10 09:12:06 2015
|
What URL did you use? If I try here on this forum I get:
which looks fine to me. |
Re: Path disclosure on unfound file, posted by Travis Unkel on Fri Aug 18 01:02:41 2017
|
I am having the same issue. If you go to midas.psi.ch/elogs/12345.htm you get the path disclosure issue.
Stefan |
Re: Path disclosure on unfound file, posted by prinnydood on Thu Dec 31 18:35:19 2020   
|
I can confirm this issue exists on version 3.1.3, which I have installed elog on Debian 10.
The issue also exists on version 3.14 (1.20190113git283534d97d5a.el7), which I tested on an AmazonLinux EC2 instance.
This is what I found: |
Re: Path disclosure on unfound file, posted by Stefan Ritt on Fri Jan 8 13:47:14 2021
|
Ok, I fixed the code in the current commit (395e101add19f0fe8a11a25d0822e511f34d94d1). The path gets stripped, and we see a
prinnydood |
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: Path disclosure on unfound file, posted by Stefan Ritt on Fri Feb 19 09:59:04 2021
|
I made a new RPM: https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-3.el7.x86_64.rpm
Gabriel
Lopez wrote:
Hello, This is coming up as a high vulnerability in our scans. Are |
Re: Path disclosure on unfound file, posted by Gabriel Lopez on Fri Feb 19 19:48:11 2021
|
Thank you for your work. Works like a charm!
Stefan
Ritt wrote:
I made a new RPM: https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-3.el7.x86_64.rpm |
export/archive a logbook, posted by Jacky Li on Thu Feb 18 19:21:57 2021
|
Hi,
I have an elogd server serves many logbooks. May I know what is a good way to export or achive one its logbooks? Thank you.
Jacky |
Re: export/archive a logbook, posted by Stefan Ritt on Fri Feb 19 08:35:53 2021
|
Find -> Export to: CSV (or any other format) -> Search
Jacky
Li wrote:
Hi, |
elog server go to high CPU and hangs, posted by Stefano Lacaprara on Thu Feb 18 09:14:28 2021
|
Dear expert,
I'm running the latest git version of elog ELOG V3.1.4-395e101a on ubuntu 20.04.2.
I'm experiencing frequent hangs of the elog server: the status is always reported as running, but the web server is not responding.
|
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.
|
Different Top Groups or Groups have the same logbook name , posted by MATT TERRON on Tue Feb 2 04:01:21 2021
|
I have built different top groups for different departments. But occasionally these different top groups have the same logbook name, say 'Maintenance
Log'. So is there a way I can have the same logbook name under different 'Top Groups', rather than rename these logbooks as 'Department1
Maintenance Log' all the way to 'Department_X Maintenance Log'? |
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 |
elog slowness, posted by Giuseppe Cucinotta on Thu Jan 14 11:43:00 2021
|
We run elog on a server to provide a logbook for our laboratory. We noticed that elog is very slow on loading pages: browser pages spend a lot of
time in charging (actually one can speed the procedure refreshing the page but it is quite annoying).
I checked the server load with top and it doesn't show any abnormal CPU or memory usage. Then I ran lsof and I noticed that there are |
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. |
hidden files, posted by Lahreche Abdelmadjid on Sun Jan 10 11:13:31 2021
|
Hello;
Could I make change on program only on the " elogd.cfg" ?
Or is there onother files, because I think there is hidden files ? |
outdated debian package, posted by Chris Körner on Fri Dec 18 18:08:54 2020
|
Hi everyone,
I am currently trying to setup elog as a docker container. I wonder if there is any reason why the elog debian package is stuck at version 3.1.3?
Would it be possible to update it to the latest version? |