Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   editor dosn't work, posted by Sara Vanini on Thu Jun 2 12:52:10 2011 
    icon2.gif   Re: editor dosn't work, posted by David Pilgram on Thu Jun 2 14:57:39 2011 
       icon2.gif   Re: editor dosn't work, posted by Sara Vanini on Thu Jun 2 16:50:17 2011 
          icon2.gif   Re: editor dosn't work, posted by David Pilgram on Thu Jun 2 20:20:19 2011 
Message ID: 67079     Entry time: Thu Jun 2 20:20:19 2011     In reply to: 67078
Icon: Reply  Author: David Pilgram  Author Email: David.Pilgram@epost.org.uk 
Category: Bug report  OS: Linux  ELOG Version: 2.7 
Subject: Re: editor dosn't work 

Sara Vanini wrote:

David Pilgram wrote:

Sara Vanini wrote:

Hi,

when I try to edit an entry of my ELOG, the display shows the editor window blank, without all the previous content of the entry, and it is not possibile to write in it. It worked since yesterday, when ELOG tried to save a new entry but the disk was full. ELOG was srewed up. I deleted the buggy entry and now I can display all the previuos entries, but I cannot edit anymore... Please help!

Sara

 

 I've a little experience of digging myself out of (in my case, self-induced) problems using ELOG.   I'm also aware that I may be the least experienced/qualified user..

First:  Archive your work directories.  Then at least whatever you do from here, you've got the status quo to fall back on.  Also, record anything you can remember (ID number, thread, etc) of the deleted entry/entries.

I've found that ELOG can hang in an infinite loop if it tries to find an entry that is no longer there - and that depends upon how you approach the point where the missing entry would be.  ELOG's own delete works fine in normal circumstances.  I'm talking about abnormal circumstances, for example when idiots (me) are playing around with the yymmdda.log files, or *possibly* if the disk is full, and you then try deleting the entry that caused the full disk problem.  Whether that is what you are seeing, I cannot say at present. 

However, to progress this:  When you are stuck, unable to edit anything, in a[nother] terminal, try the process report

ps -A

two or three times, with a short interval between commands.  (Or other switches if you know how to select to view the elogd process on your system).   If elogd is using seconds of CPU time between each ps command, it's probably in an infinite loop.  If you need to be sure, wait a minute and check again.  If so, you'll have to stop the daemon, possibly requiring a computer reboot.  In my experience, ELOG does not get stuck in an infinite loop when just indexing the pages when the daemon starts, but experts may well know better.

This may at least diagnose whether you cannot edit because ELOG is stuck in an infinite loop, or has some other cause.

If it is the infinite loop, the trick is to find which entry causes the loop without getting stuck in that loop next time around. 

David Pilgram.

 Hi David,

you have been very helpful indeed. The problem was the one you spot, I've deleted the  buggy entry removing the ***.log file, and this caused disaster..... now it is working again, thanks a lot, I have all my PhD thesis in ELOG....

Sara

 

Don't get too excited yet!

 

When you reply to an entry in ELOG, then some additional data is added to that original entry. 

 

So, if you reply today (say 02/06/11) to an entry made yesterday, then you will find that the file 110602a.log has a large change (the new entry in full, plus elog extra codes), *and* an additional line added into 110601a.log.  Deleting 110602a.log will not remove the line in 110601a.log, and that could still cause problems, that is, wandering into an infinite loop.

 

To save a lot of effort, I'll suggest that you (a) keep the back-ups up to date, and keep two (the latest and the one before that); (b) proceed carefully at least to start with.  If you fall into the infinite loop again, then flag it up and I (or someone else) will be able to give further pointers.

 

David Pilgram.

 

 

So unless you are sure that

ELOG V3.1.5-fe60aaf