Logfile not registering entry numbers?, posted by Sergio Navarrete on Fri Oct 19 08:38:06 2018
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply? |
Re: Logfile not registering entry numbers?, posted by Andreas Luedeke on Fri Oct 19 13:08:30 2018
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For
new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving |
|
Re: Logfile not registering entry numbers?, posted by David Pilgram on Mon Oct 29 14:26:28 2018
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking
for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate
line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now. |
|
Re: Logfile not registering entry numbers?, posted by Stefan Ritt on Wed Apr 1 15:57:27 2020
|
I finally found some time to fix that bug. Was just that the log file hat #0, the bug should not have had any ohter side effects. Now the logfile is
fine.
David |
|
Re: Logfile not registering entry numbers?, posted by Sergio Navarrete on Thu Dec 16 08:23:22 2021
|
It seems that the latest Windows binary still predates this fix. Will there be a new installer soon? Thanks for your support.
Stefan
Ritt wrote:
I finally found some time to fix that bug. Was just that the log file |
|
Log4j exploit, posted by Alan Grant on Tue Dec 14 19:16:57 2021
|
Is there any potential impact/concern with the Log4j exploit in Elog applications?
|
|
Re: Log4j exploit, posted by Stefan Ritt on Tue Dec 14 21:55:16 2021
|
ELog does not use the Log4j library so no issue there. If you run a web server like Apache in front of ELog, you however have to check if you use log4j
there.
Alan |
Dump screenshot to new elog entry, posted by Anthony J Krishock on Sun Dec 12 01:18:46 2021
|
Hello,
I am interested in finding a preferrably single-click way to capture a screenshot and posting it automatically to a new elog entry . I would
be doing this from Windows. Is this possible? |
|
Re: Dump screenshot to new elog entry, posted by Andreas Luedeke on Sun Dec 12 08:12:57 2021
|
I am no Windows expert. An option is to write your own application and use the "elog" command to post the output of the application to your
ELOG.
There is as well a python library to access ELOG via http: https://github.com/paulscherrerinstitute/py_elog |
$attribute replacement fails occasionally, posted by Chris Körner on Sat Nov 27 21:48:41 2021
|
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>. |
Re: $attribute replacement fails occasionally, posted by Chris Körner on Sat Dec 4 13:03:32 2021 
|
This problen drives me crazy. Under some circumstances the List Change <attribute> function does not replace $attribute. It happens at random circumstances
when I use the Find function to search all logbooks. In the resulting list, it fails reproducibly for certain entries of certain logbooks. But I cannot
find what is special about those lokbooks or entries. In different Find requests it works perfectly fine. |
|
Display edit time, posted by Devrim Esenturk on Wed Nov 24 08:12:17 2021
|
Hi
I have a large logbook to keep office demo equipments listed. So editing entries are very often, I would like to see last editing time on my
entry as entry time shown as each entry. Is there any way to do this? I checked all attributes and commands but couldn't find any. |
|
Re: Display edit time, posted by Stefan Ritt on Wed Nov 24 08:38:33 2021
|
Creat an attribute "last edit" and set it to the last edit time. Something like this:
Attributes = ...., Last edit
Preset Last edit = $date |
|
Body of new messages not getting saved when submitted, posted by Harry Martin on Sun Nov 21 23:20:15 2021
|
I've been using elog for a few years now. I've had the current setup working for me up until today.
If I create a new message (entry, whatever they are called), or if I attempt to update an existing message, only the header information is saved.
The body (the part I can see in the editor) does not get saved. |
|
Re: Body of new messages not getting saved when submitted, posted by Sebastian Schenk on Sun Nov 21 23:49:42 2021
|
Hello Harry,
the elog server (elogd) is a standalone application written in C and contains a full webserver and logfile management system.
There are no other dependencies to apache or python. |
|
Re: Body of new messages not getting saved when submitted, posted by Harry Martin on Mon Nov 22 00:44:21 2021
|
Thank you for your quick response, Sebastion. The new version of ckeditor is 4.5.7 -- is this version compatible with elog 3.1.2? It is possible
that I am using an outdated elog or outdated ckeditor due to the fact that this server is a bit old; I am looking to upgrade this machine soon, but I have
several other issues to resolve first. |
|
Re: Body of new messages not getting saved when submitted, posted by Harry Martin on Mon Nov 22 19:28:28 2021
|
(disregard my recent post here about missing package -- that wasn't the elog server!)
I can see that ckeditor was upgraded 11/19, which is would be prior to my recent attempts to use elog. It was apparently a security update,
so I am not sure it is sensible to downgrade. OTOH, I am the only person here, and I have all sides carefully barracaded, so I don't think it |
|
Re: Body of new messages not getting saved when submitted, posted by Harry Martin on Mon Nov 22 19:45:08 2021
|
After downgrading ckeditor, my elog installation is working again. Thanks for your help.
Harry
Martin wrote:
(disregard my recent post here about missing package -- that wasn't |
|
Restrict edit time = 0 behavior intended?, posted by Chris Körner on Mon Nov 15 11:35:55 2021
|
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 |
|
Re: Restrict edit time = 0 behavior intended?, posted by Chris Körner on Mon Nov 15 11:48:25 2021
|
Actually this is related to post 68993 from Sebastian Schenk in Jul 2019. Are there any new workarounds
I may have missed?
Chris |
|
Re: Restrict edit time = 0 behavior intended?, posted by Sebastian Schenk on Mon Nov 15 14:02:42 2021
|
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 |
|
Re: Restrict edit time = 0 behavior intended?, posted by Chris Körner on Tue Nov 16 15:14:42 2021
|
Hi Sebastian,
thanks for the reply. It is just a bit confusing that these similar settings behave so differently. For me it is no big deal to set the
time for every logbook independently instead of [global], but it leaves more room for configuration errors. |
Shared logbook and elog.cfg file across multiple installations, posted by Anthony on Mon Nov 15 15:41:04 2021
|
Hi,
I'm wondering if it's possible to have a shared logbook and elog.cfg between multiple instances of elog. Ideally, I'd like
to have my logbooks folder and elog.cfg hosted on a nextcloud instance while running the elog service locally. I've tried this using symlinks |
|
Re: Shared logbook and elog.cfg file across multiple installations, posted by Sebastian Schenk on Mon Nov 15 17:40:08 2021
|
Hi Anthony,
the elog has a mirroring function, which synchornizes config and logs between multiple instances.
See the bottom section of https://elog.psi.ch/elog/config.html |
|
Re: Shared logbook and elog.cfg file across multiple installations, posted by Anthony on Tue Nov 16 13:05:05 2021
|
Thank you Sebastian!
I admittidely haven't looked through the page in a while, so I completely missed this feature. This should solve the problem, although
in a slightly different implementation than what I was trying for. |