Dear Stefan,
Thanks for your reply.
I started running elog in February and it never failed. Then it started failing regularly towards the end of September. There were no system changes until then, except the daily automatic Yum updates (SLC4). Then I upgraded to the latest version (tar ball of 2.7.5). Then yesterday it crashed again. I saw that it crashed around the time when a user was doing something - inputting new data. I can monitor when it crashes and correlate it with user activity. But it is not easy to reproduce since I don't know exactly what the user is typing.
It would be necessary to record the user input forms and then replay them against a known server state. But that is not so easy.
I will think about doing something else - maybe running inside a debugger as you suggest.
Soren
Stefan Ritt wrote: |
soren poulsen wrote: |
Hi
I am experiencing trouble with Elog crashing. I think it crashes during input operations (new entries are being added).
Are there any preferred methods to troubleshoot this ? Any log files I could look at ?
For now, I let "monit" supervise the process and restart it if it crashes. But I would like to get to the root cause of the problem.
Soren Poulsen
CERN
|
Dear Soren,
sorry for the trouble, but it's very hard to diagnose this remotely. This forum here runs fine for many months, so in principle Elog should be stable (at least the current version 2.7.5). If you have an older version, please upgrade. If you have a way to reproduce the problem reliably, you can send me your config file and explain step-by-step how you make Elog crash. Then I can try to reproduce it here. Otherwise the only chance I see is to run elog from inside the debugger, and once it crashes record the stack trace and send it to me. If you don't know how to use the gnu debugger, I'm sure you find someone at CERN who knows.
Best regards,
Stefan
|
|
soren poulsen wrote: |
Hi
I am experiencing trouble with Elog crashing. I think it crashes during input operations (new entries are being added).
Are there any preferred methods to troubleshoot this ? Any log files I could look at ?
For now, I let "monit" supervise the process and restart it if it crashes. But I would like to get to the root cause of the problem.
Soren Poulsen
CERN
|
Dear Soren,
sorry for the trouble, but it's very hard to diagnose this remotely. This forum here runs fine for many months, so in principle Elog should be stable (at least the current version 2.7.5). If you have an older version, please upgrade. If you have a way to reproduce the problem reliably, you can send me your config file and explain step-by-step how you make Elog crash. Then I can try to reproduce it here. Otherwise the only chance I see is to run elog from inside the debugger, and once it crashes record the stack trace and send it to me. If you don't know how to use the gnu debugger, I'm sure you find someone at CERN who knows.
Best regards,
Stefan |
Hi
I am experiencing trouble with Elog crashing. I think it crashes during input operations (new entries are being added).
Are there any preferred methods to troubleshoot this ? Any log files I could look at ?
For now, I let "monit" supervise the process and restart it if it crashes. But I would like to get to the root cause of the problem.
Soren Poulsen
CERN |
Originally, all information about our machines was stored in a spreadsheet with one sheet for the hardware of the machines and one for the software. By now, I've sucessfully moved the software part to an elog logbook and am now looking at transferring the hardware part as well.
As both lists are machine-name based, one of the options would be to merge both lists, as this would place all machine-related info into one logbook. The downside of this is that I get so many columns in list view that the result is quite unwieldy. Hence, I would like to hide some columns - ideally creating a "hardware view" and a "software view".
From the documentation, the only option I could find that seemed suitable was "List conditions". Unfortunately, I do not quite understand from the manual how this is supposed to work, so I'm quite possibly doing something wrong. I've tried this:
; General settings
List conditions = 1
; Attributes
Attributes = Type, Created, StatusA, StatusB, Archived
; Options & Tooltips
Options Type = Type1{10}, Type2{11}
; Conditionals
{10}List display = Edit, Type, Created, Status
{11}List display = Edit, Type, Created, StatusA, StatusB, Archived
but no matter how I set "Type", it does not seem to have any effect on the List display. One thing I don't understand for example is how does elog decide in List view which entry sets the condition? If all entries are set to the same value (in this example e.g. "Type1")? The first entry? Or am I missing something altogether? 
Also, if there are alternative ways how I could accomplish my goal, I'd also be most grateful for suggestions.
Thanks in advance,
Thomas |
Hi Stefan.
I have been "playing" around with this great tool and found an interesting "issue" ...
I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".
When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.
When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.
How can I apply my own Bottom Text to the Standard Login Screen ?
Thanks & Regards, Barend
|
Hi, thanks for everyone involved for giving us the elog.
A question:
Is there an easy way (without intermediate save) to send screenshots (with irfan, snagit or hardcopy) as a new entry to an elog running on a remote machine?
Thanks, thorsten |