ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66458
|
Wed Jul 22 15:35:57 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
Stefan Ritt wrote: |
well, I need to reproduce your problem in order to fix it. The failed assertation you get is due to some internal writing beyond array boundaries, but I have no clue which part of the code makes this. It might be related to the fact that you use the same index (via Subdir=...) for two logbooks. In this scenario, you are only allowed to modify/add entries to one logbook, not the other. The other one may only be used for reading. And even then it's not guaranteed that new entries show up in the second logbook immediately, you might have to restart the server in order to re-index the logbooks. Internally, the daemon does not know that two logbooks are "the same" and one instance will not realize if the other instance modifies the data "below its feet". Can you try to give up the double logbooks and see if the problem goes away?
|
Hm... I have implemented this set-up originally based on this: https://midas.psi.ch/elogs/Forum/66024. The "double logbook" is a machine log with a "software" (OS installations etc.) and a "hardware" (CPU, RAM, etc.) view. The "hardware" view has the "Subdir=" statement. Thinking about it, the "software" view is used most - I have several automatic scripts running which update the contents whenever a machine gets updated, re-installed and so on. The hardware part does not see much editing - until this week, when we decided to start an inventory... So, it's quite possible that we never noticed that this was iffy. For the rest of our goals, this set-up has worked fantastically - never noticed any problem with one view not updating, actually. Also, I do not remember any crashes with the other, single logbooks.
What I've done for now is to ask all team members to use only the software part (the one without the Subdir statement) to actually change content (the entry masks are the same in both versions) and use the hardware part just for viewing. I'll report back as soon as I get some feedback.
Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make this work (even) better, I'd be most grateful.
Regards,
Thomas |
66459
|
Wed Jul 22 16:30:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
T. Ribbrock wrote: |
Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make this work (even) better, I'd be most grateful.
|
Well, for that I have to reproduce the problem. So best would be if you strip it down to the bare minimum in order to reproduce this reliably. Then you zip everything and send it to me. Then tell me what I have to edit and submit in order to stimulate the crash. Once this is successful, I can fix it. |
66460
|
Wed Jul 22 16:52:13 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
Stefan Ritt wrote: |
T. Ribbrock wrote: |
Nonetheless, given that this set-up has been a great help for us - if you ever get the chance to make this work (even) better, I'd be most grateful.
|
Well, for that I have to reproduce the problem. So best would be if you strip it down to the bare minimum in order to reproduce this reliably. Then you zip everything and send it to me. Then tell me what I have to edit and submit in order to stimulate the crash. Once this is successful, I can fix it.
|
Thank you - I shall look into that, though it'll probably take a while to prepare it. |
66483
|
Wed Jul 29 14:48:34 2009 |
| T. Ribbrock | emgaron+elog@ribbrock.org | Bug report | Linux | 2.7.6r2233 | Re: Crashes when editing entries |
By now, I've installed 2244 and ran some rudimentary tests. So far, I was not able to reproduce the crash anymore. Looking good! |
69252
|
Tue Oct 27 16:15:26 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.4-ba84827 | Re: Create entry from command line - override Date? |
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category:
Subject: CURL test
Attachment:
Encoding: plain
========================================
Text body
|
69253
|
Tue Oct 27 16:37:07 2020 |
| David Wallis | wallis@aps.anl.gov | Question | Linux | V3.1.4-ba84827 | Re: Create entry from command line - override Date? |
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date", upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan Ritt wrote: |
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category:
Subject: CURL test
Attachment:
Encoding: plain
========================================
Text body
|
|
69254
|
Tue Oct 27 16:49:53 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.4-ba84827 | Re: Create entry from command line - override Date? |
"Date" must be on the first line on each entry and it must be named "Date".
Stefan
David Wallis wrote: |
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date", upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan Ritt wrote: |
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category:
Subject: CURL test
Attachment:
Encoding: plain
========================================
Text body
|
|
|
69255
|
Tue Oct 27 17:07:00 2020 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | V3.1.4-ba84827 | Re: Create entry from command line - override Date? |
You could transform your entries into the ELOG file format (either XML or CSV) and then use the import function. That would upload the correct dates from your entries.
If you use the "Orig Date" trick you've proposed, you'll see that datetime fields are stored as seconds of the epoch (since 1.1.1970). Not so easy to copy and paste them, but you can convert them with a script.
Cheers, Andreas
David Wallis wrote: |
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date", upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan Ritt wrote: |
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!!
Author: Stefan
Type: General
Category:
Subject: CURL test
Attachment:
Encoding: plain
========================================
Text body
|
|
|