elogd service crashes after windows update, posted by Tom Roberts on Fri May 18 00:57:33 2018
|
We have been using elog on Windows 10 for a long time. Today, after a Windows update, the elogd service started crashing (error 1067, unexpected termination).
It ran fine just before the Windows update (which took > 1 hour, so it was a major one). Uninstalling and re-installing did not help, including replacing
my elogd.cfg with the default. Installing on another PC (that also has this update) fails in the same way. I have a good backup of my logbook. |
about shiftcheck, posted by Xuan Wu on Tue May 15 04:41:23 2018 
|
Hi all,
I try to implement a shift check list for our facility. The attributes called "a1, a2, b1, b2 etc" are used in original shiftcheck.html，
However, we would like to use "1.1, 1.2, 2.1, 2.2 etc". So I try to change the name of checkbox in shiftcheck.html and the attributes in |
Re: about shiftcheck, posted by Andreas Luedeke on Tue May 15 10:35:32 2018
|
An attribute is similar to a variable. Do you know any programming language that allows to start a variable with a digit? I don't.
The solution is very obvious: start your attributes with a letter.
Cheers, Andreas |
|
Re: about shiftcheck, posted by Xuan Wu on Wed May 16 02:20:24 2018
|
That's true. Thanks for your explanation.
Cheers, Xuan
Andreas |
|
Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Fri May 4 14:43:35 2018
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision |
|
Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Fri May 4 16:05:32 2018
|
I am not sure I understand your bug report.
I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?
Cheers, Andreas |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Sat May 5 11:22:50 2018
|
Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.
You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX
The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer |
|
Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Sat May 5 20:55:23 2018
|
Well, in my example the ID link worked just fine.
There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would
need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem. |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Mon May 7 18:10:20 2018
|
ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX
format and it indeed had a silly hard coded length of that string.
Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog |
Re: Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Tue May 8 16:17:28 2018
|
Thank you all for your kind responses. Please consider this thread resolved: no bug in elog
Chris
Rasmussen wrote:
ah yes, that was a helpful clue. Our elogd.cfg file led me to a |
|
Re: Elog ID entry bug at >99999 entries, posted by Stefan Ritt on Mon May 7 14:24:18 2018
|
As Andreas said we have to reproduce the problem. What is special in your case is the elog:SequencerEvents/XXXXX.
This is non-standard and must be created through your configuration of elog or by an external script. I just guess that you have something like
Preset ID = elog:SequencerEvents/##### |
|
Email Config, posted by Stefan Werler on Wed Apr 18 12:07:50 2018
|
Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing? |
|
Re: Email Config, posted by Stefan Ritt on Wed Apr 18 12:30:51 2018
|
SMTP host = ...
as written in the documentation!
Automatic email after expiration is not possible. |
|
Re: Email Config, posted by Stefan Werler on Wed Apr 18 13:18:07 2018
|
many thanks
Stefan
Ritt wrote:
SMTP host = ... |
|
Re: Email Config, posted by Andreas Luedeke on Wed Apr 18 13:43:36 2018
|
SMTP host = ...
MUST be set in the [global] section of your configuration - it will likely not work when you try to set it for a specific
logbook.
I don't see how ELOG can send an automatic email after a date expired. |
|
problem with chkeditor, posted by Andrea Mazzolari on Wed Apr 4 19:56:48 2018
|
Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see
there. Why this ? For example, it does not offer the possibility to upload images. |
|
Re: problem with chkeditor, posted by Stefan Ritt on Wed Apr 11 11:55:47 2018
|
Can you post a picture here?
Andrea
Mazzolari wrote:
Hi All, |
|
Re: problem with chkeditor, posted by Andrea Mazzolari on Sat Apr 14 15:11:31 2018
|
If i try to upload an image here, i got the error "Image Source URL Is Missing"...
can you help me further ?
Best regards, |
|
Re: problem with chkeditor, posted by Andreas Luedeke on Mon Apr 16 17:27:35 2018
|
Yes, I can help with that: you've tried to put the picture into the text body. Try to make it a normal attachment, that'll work always.
Andrea
Mazzolari wrote:
If i try to upload an image here, i got the error "Image Source |
|
"Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Michael Kelsey on Wed Apr 11 18:14:35 2018
|
Hello! The CDMS collaboration is using e-Log as one of it's issue tracking systems. In the last few months, I have noticed a problem
when either creating or editing entries from my usual Safari browser (currently 11.1 on MacOSX 10.13.4): The [Submit] button triggers
a spinning beach ball, with no connection to our e-Log server, and after several minutes, Safari complains the the page had to be reloaded, discarding |
|
Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Michael Hibbard on Thu Apr 12 14:13:18 2018
|
I dont' have a solution, but I just wanted to bring more attention to your post. I too am having the same issue with the ELOG system and the Safari
browser. I have noticed that ELOG is most stabel and function on the client end from the IE browser. A few weeks ago I also had to switch from using ELOG
on the client end from Safari to Firefox. |
|
Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Stefan Ritt on Sat Apr 14 08:50:40 2018
|
I'm not 100% sure, but I believe it should work without the
while (in_asend);
So can you please remove that line (it's in src/elogd.c) and recompile elogd and test it? |
|
Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Michael Kelsey on Sun Apr 15 08:03:21 2018
|
Thank you for your suggestion, Stefan! The sysadmin who handles our e-Log server implemented your suggestion earlier today (Saturday). I
have been able to successfully create and modify e-Log entries with Safari since then. Since the "slow script" issue has been intermittent
in the past, I plan to continue testing and monitoring for the next day or so. Nevertheless, it appears that removing the waiting loop has alleviated |
|
Re: "Slow script" problem posting/editing from Safari -- browser hangs, times out, posted by Stefan Ritt on Mon Apr 16 08:19:16 2018
|
Ok, I removed the code from the official code now.
A bit background: The "autosave" mechanism in elog saves regularly the current content in a "draft" message, so that the
data does not get lost if the browser for example crashes. The saving is done asynchronously via some AJAX call. This call takes some time, since it's |
|
"Drop attachments here..." only functional in IE, posted by Michael Hibbard on Thu Apr 5 06:00:09 2018
|
Hello, the "drop attachments here..." feature is very useful, especially when I have multiple files. I can drag them all over in one operation,
however I have noticed that this feature only works well in the IE browser.
It does not work reliably in Safari/Chrome/Firefox. I have tired in both 3.1.3 and 3.1.2. I also have the same symptom on the Demo log book of |
|
Create past Elog entry., posted by Michael Hibbard on Mon Apr 2 23:31:51 2018
|
Hello, Sorry if this has been addressed elsewhere, but I could not find info.
I am wanting to submit a new elog entry (that should have been) for a past date, to predate log entrys currently in my system.
I assume I must manually create a new .log file. What ID# should I assign to this entry? Should I sub-increment (i.e 33.1)? I presume the |
|
Re: Create past Elog entry., posted by David Pilgram on Tue Apr 3 09:39:07 2018
|
Hi Michael,
Elog purists, look away now.
There is an "official" way to do this, which is to have fields for entry date (so can be in the past), but the yymmdda.log file will |
Re: Create past Elog entry., posted by Michael Hibbard on Tue Apr 3 22:34:49 2018
|
Thank you David, Andreas. Very useful forum.
David
Pilgram wrote:
Hi Michael, |
|
Re: Create past Elog entry., posted by Andreas Luedeke on Tue Apr 3 10:19:07 2018
|
David answered the question already.
I would distinguish if this is a once-in-a-year event, where you are willing to edit the logfiles as an administrator to fix it -
or
if it happens more weekly, and you want to enable the users to fix it themself.
If it happens once a year and you don't |