Richard Schiff | 12 Jun 22:22 2013

HELP! eZproxy crashed.... what does this error message mean?

In many years I have not had eZproxy crash.  It just did.  Here is what happened as described in the message
file.  Anyone know what it means?

Just restarted eZp and it seems to be working....  But would like to know what happened.

2013-06-12 12:51:42 Guardian terminated EZproxy process because its HandleRaw thread's latency is
greater than 5.000000 seconds (main location 2000, raw 
2013-06-12 12:51:42 location 11, stopSockets location 2).
2013-06-12 12:51:42 The EZproxy thread had seized.
2013-06-12 12:51:42 The HandleRaw thread had seized.
2013-06-12 12:51:42 The StopSockets thread had seized.
2013-06-12 12:51:42 The AthensLogging thread had not seized.
2013-06-12 12:51:42 The RefreshShibbolethMetadata thread had not seized.
2013-06-12 12:51:42 The Cluster thread had not seized.
2013-06-12 12:51:42 The DNS thread had not seized.
2013-06-12 12:51:42 The SaveUsage thread had not seized.
2013-06-12 12:51:42 Guardian is unable to start EZproxy.
2013-06-12 13:03:20 EZproxy 5.5.3 GA [Windows] [2011-12-16T21:21:15Z]
2013-06-12 13:03:20 EZproxy is configured to run as a service.
2013-06-12 13:03:20 For further information or updates, visit http://www.oclc.org/ezproxy/ or
contact ezproxy <at> oclc.org.
2013-06-12 13:03:20 Guardian initialized
2013-06-12 13:03:20 Guardian starting EZproxy
2013-06-12 13:03:20 EZproxy 5.5.3 GA [Windows] [2011-12-16T21:21:15Z]
2013-06-12 13:03:20 EZproxy is configured to run as a service.
2013-06-12 13:03:20 For further information or updates, visit http://www.oclc.org/ezproxy/ or
contact ezproxy <at> oclc.org.

Thanks,

(Continue reading)


Gmane