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. |
xmalloc error when filling entries and chaning page, posted by Antonio Iuliano on Wed Dec 12 10:44:57 2018 
|
Dear ELOG experts,
the ELOG server on our lab crashes continuosly, when we add a new entry or even if we click the arrows to navigate between entries. Following
the FAQ on the website, I have used gdb and found the following error: |
Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 15:46:14 2018
|
I have a setting which makes ELOG a perfect solution, but there's a situation that
I'm struggling to get my head around. We have 3 separate laboratories, each one containing a number of temperature chambers, which run almost constantly
over a number of shifts. Each temperature chamber has it's own logbook (laptop). So far, pretty simple. |
|
Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 16:00:45 2018
|
Sure that's easy. Install elog on each laptop separately, so they run without network. Then, set up a central elog server, and use "mirroring"
as explained in the documentation at https://elog.psi.ch/elog/config.html#mirroring
So when ever the entwork comes back, you execute a manual mirror operation, and your new entries will be pushed to the central elog server. |
|
Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 17:22:31 2018
|
Thanks Stephan! I guess I was making it harder than it is. I'm still a little fuzzy -- in this instance, am I correct in saying that each
laptop would be considered a "master", and the remote (network) server considered the "slave"? Also, I'm not sure quite sure
-- which server should be assigned responsibility for performing periodic synchronization between the laptop and the central elog server? |
|
Re: Logbook architecture and availability, posted by Stefan Ritt on Fri Dec 14 20:05:08 2018
|
I would call the laptops the "master" being responsible for pushing data to the central server which you can call "slave"
Stefan |
|
Re: Logbook architecture and availability, posted by Frank Baptista on Fri Dec 14 20:52:46 2018
|
Thank you again -- very much appreciated!
|