PS: maybe this dump could give a clue..... what's the directory of  size

12288

.

created on Jun  1 14:08  ... ? has it screwed up elog?

Sara

[vanini@nbvanini ~]$ ls -latr /usr/local/elog/logbooks/work/

-rw-r--r-- 1 elog elog   3443 May 30 12:31 110530a.log
-rw-r--r-- 1 elog elog  38956 May 30 14:17 110322a.log
-rw-r--r-- 1 elog elog  48804 May 31 10:05 110302a.log
-rw-r--r-- 1 elog elog  75644 May 31 17:09 110427a.log
-rw-r--r-- 1 elog elog   4079 May 31 18:58 110531a.log
-rw-r--r-- 1 elog elog  77316 Jun  1 10:43 110113a.log
drwxr-xr-x 2 elog elog  12288 Jun  1 14:08 .
-rw-r--r-- 1 elog elog   2904 Jun  1 14:20 110601a.log
 

Since you used the -a switch for ls, the current directory '.' i.e. work/ is included in the list. I have the same kind of output. No worries.

Are you experiencing problems with ELOG?

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