We want the elog process to run in verbose mode so that we can see what's going. The idea is to track the events that trigger the elog crashes.
Following an entry on the Elog Help Forum, I added this line to the elog starting script start-elog-nodus:
./elogd -p 8080 -c /cvs/cds/caltech/elog/elog-2.7.5/elogd.cfg -D -v > elogd.log 2>&1
which replaces the old one without the part with the -v argument.
The -v argument should make the verbose output to be written into a file called elogd.log in the same directory as the elog's on Nodus.
I haven't restarted the elog yet because someone might be using it. I'm planning to do it later on today.
So be aware that:
We'll be restarting the elog today at 6.00pm PT. During this time the elog might not be accessible for a few minutes.
|