EZproxy stops with error that the Guardian terminated EZproxy
Symptom
- EZproxy stops and messages.txt shows an error similar to "Guardian terminated EZproxy process because its EZproxy thread's latency is greater than X.XX seconds"
Applies to
- EZproxy Stand-Alone
Resolution
While there could be other issues causing this, a common issue is EZproxy is just appending to the messages.txt file. If this is never cleaned up, there could be years of logging in the file. Once it hits a certain size the system could have issues writing to the messages.txt file, at which point the system will shut down EZproxy.
To avoid this, use the suggested configuration for messages.txt so the file rotates daily. First, move or rename the existing messages.txt, the set this as the only line in the messages.txt:
MessagesFile -strftime messages-%Y-%m-%d.txt
Then restart your EZproxy.
For stand-alone EZproxy systems that need additional help, contact OCLC Support