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  Sat Dec 18 06:24:49 2010, rana, Update, elog, restarted 
    Reply  Sat Dec 18 23:33:06 2010, Koji, Update, elog, restarted 
       Reply  Sun Dec 19 11:19:42 2010, Koji, Update, elog, restarted 
          Reply  Sun Dec 19 22:45:28 2010, rana, Update, elog, restarted 
          Reply  Wed Jan 5 10:45:51 2011, Koji, Update, elog, restarted 
             Reply  Thu Jan 6 10:47:11 2011, Koji, Update, elog, ELOG fixed (re: restarted) 
Message ID: 4121     Entry time: Thu Jan 6 10:47:11 2011     In reply to: 4111
Author: Koji 
Type: Update 
Category: elog 
Subject: ELOG fixed (re: restarted) 

Fixed the 40m elog crashing with the threaded display.

This morning I found that Google bot crashed the elog again. I started the investigation and found the threaded mode is fine if we use the recent 10 entries.

I gradually copied the old entries to a temporary elog and found that a deleted elog entry on August 6 had a corrupted remnant in the elog file. This kept crashed the threaded mode.

Once this entry has been eliminated again, the threaded mode got functional.

I hope this eliminates those frequent elog crashing.

Quote:

Google bot  crashed the elog again. Then, I found that Google bot (and I) can crash elogd by trying to show the threaded view.
There looks similar issue reported to the elog forum, the author did not think this is a true bag.

Note: This happens only for the 40m elog. The other elogs (ATF/PSL/TCS/SUS/Cryo) are OK for the threaded view.

Quote:

Did it again. It seemed that Google bot came to the elog and tried to obtain "http://nodus.ligo.caltech.edu:8080/robots.txt". That was the last of the log.
Bot came from the AJW's homepage. Also Google FeedFecther came to the elog.

 

 

ELOG V3.1.3-