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.