I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
The logbooks appeared to be empty; new entries started with index "1".
The first time the origin of the problem were network troubles;
the second time it had been caused by a severe problem of our AFS file system service.
I never experienced this consequence for ELOG in the past when we had AFS problems.
Since the logbooks are used for the operation log of a user facility they continued to do new entries.
The next day I had to re-number the new entries and restart elogd and everything was fine.
I could understand if elogd crashes when the filesystem of the logbook goes away.
And when it restarts with an (temporarily) empty filesystem, that would explain what happened.
But it did not restart and the log file does not contain any information about any problem,
just that suddenly all new entries in each logbook started with ID "1" again.
Stefan, any idea?
Anyone else ever experienced that with the new ELOG version (or older ones)? |