Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 510 of 808  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  68270   Fri Feb 26 17:35:54 2016 Entry Juergen Diefenbachdiefenba@uni-mainz.deBug reportLinux3.1.1Execute new|edit doesn't seem to work
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.

When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script will then automatically stage all changes and create an appropriate git commit message. For a "new" entry in the logbook the commit message is a bit more verbose. When editing or deleting a message only a short commit message like "Edit message 25" should be created. Therefore I really need to distinguish between "new", "edit", and "delete".

However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. Frown

What I did so far to understand what goes wrong is I looked into elogd.c and found in
void submit_elog(LOGBOOK * lbs)
that bedit is sometimes true and sometimes false, when creating a new entry, although it should be false then (right?).
This is why elogd then sometimes retrieves the wrong shell command from getcfg(lbs->name, "Execute edit"...) instead of getcfg(lbs->name, "Execute new"...) around line 23610 (not exact due to some eprintf()s inserted here and there to look at bedit and so on).

When deleting an entry, everything works fine: the shell command defined via "Execute delete=" is run, but this happens somewhere else in the code so it's not a surprise.

Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you!
  68276   Mon Mar 7 13:03:13 2016 Reply Juergen Diefenbachdiefenba@uni-mainz.deBug reportLinux3.1.1Re: Execute new|edit doesn't seem to work

Andreas Luedeke wrote:
I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0

If that is the case then Stefan will know where to look Wink

Cheers
Andreas


Alright, I tried "Save drafts = 0" in the config file and now it seems to work all the time as expected!
Thank you, Andreas!

In principle I could live with this as I don't think I need to have drafts enabled.

Cheers,
Jürgen
  Draft   Wed Sep 16 01:27:20 2015  Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.9.0(elogd)elog client overwriting attached files when editing existing log

Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.

I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0

elog -h localhost -p 8080 -l test -f  file1.png -f file2.png -e 249 -v -x

This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.

Can anyone provide some tips? I am not sure if its a problem with the client or server.

Thank you in advance!

Joseph


            

  68116   Wed Sep 16 02:47:33 2015 Question Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.9.0(elogd)elog client overwriting attached files when editing existing log

Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.

I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0

elog -h localhost -p 8080 -l test -f  file1.png -f file2.png -e 249 -v -x

This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.

Can anyone provide some tips? I am not sure if its a problem with the client or server.

Thank you in advance!

Joseph


            

  68792   Fri May 4 14:43:35 2018 Warning Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.9.2Elog ID entry bug at >99999 entries

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

Attachment 1: sequencer_events.png
sequencer_events.png
  68798   Tue May 8 16:17:28 2018 Agree Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.9.2Re: Elog ID entry bug at >99999 entries

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 .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

Andreas Luedeke wrote:

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.

Cheers, Andreas

Chris Rasmussen wrote:

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 event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message

Andreas Luedeke wrote:

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

Joseph McKenna wrote:

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

 

 

 

 

 

  66285   Wed Apr 1 18:03:22 2009 Question Joseph Lejoseph.p.le@nasa.govQuestionWindows2.7.5-218is it posible to configure text message area contain two sections

Hi,

I try to configure the elog as servers log book.  I need to devide the text entry area by 2 section: 1 for issue so I can put in detail what is the issue of my servers.  the other section below the 1st one for solution.  is it posible to do so?

Joseph.

  66286   Wed Apr 1 18:03:44 2009 Question Joseph Lejoseph.p.le@nasa.govQuestionWindows2.7.5-218is it posible to configure text message area contain two sections

Hi,

I try to configure the elog as servers log book.  I need to devide the text entry area by 2 section: 1 for issue so I can put in detail what is the issue of my servers.  the other section below the 1st one for solution.  is it posible to do so?

Joseph.

ELOG V3.1.5-3fb85fa6