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  Wed Nov 16 01:45:37 2011, Zach, Update, elog, restarted 
    Reply  Wed Nov 16 02:36:35 2011, Koji, Update, elog, restarted 
       Reply  Wed Nov 16 10:13:13 2011, jamie, Update, elog, restarted 
          Reply  Wed Nov 16 12:21:33 2011, Koji, Update, elog, googlebot (Re: restarted) 
Message ID: 5908     Entry time: Wed Nov 16 10:13:13 2011     In reply to: 5903     Reply to this: 5911
Author: jamie 
Type: Update 
Category: elog 
Subject: restarted 


Basically, elog hangs up by the visit of googlebot.

Googlebot repeatedly tries to obtain all (!) of entries by specifying  "page0" and "mode=full".
Elogd seems not to have the way to block an access from the specified IP.
We might be able to use http-proxy via apache. (c.f. http://midas.psi.ch/elog/adminguide.html#secure)

 There are much more simple ways to prevent page indexing by googlebot: http://www.google.com/support/webmasters/bin/answer.py?answer=156449

However, I really think that's a less-than-idea solution to get around the actual problem which is that the elog software is a total piece of crap.  If google does not index the log then it won't appear in google search results.

But if there is one url that when requested causes the elog to crash then maybe it's a better solution to cut of just that url.

ELOG V3.1.3-