40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Thu Nov 19 16:04:48 2009, Alberto, Configuration, elog, Elog debugging output - Down time programmed today to make changes 
    Reply  Thu Nov 19 18:49:55 2009, Alberto, Configuration, elog, Elog debugging output - Down time programmed today to make changes 
Message ID: 2302     Entry time: Thu Nov 19 16:04:48 2009     Reply to this: 2303
Author: Alberto 
Type: Configuration 
Category: elog 
Subject: Elog debugging output - Down time programmed today to make changes 

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.

ELOG V3.1.3-