- After making changes to the config.txt file, the EZproxy server fails to start
If you encounter issues with the EZproxy server not starting after modifying the config.txt file, follow these steps to identify and resolve the problem:
- Review Config.txt Changes:
- Return to the edit you made in the config.txt file
- If the change involves pointing to an IncludeFile, ensure the filename is spelled correctly and exists in the specified location
- Make any necessary corrections and attempt to restart the EZproxy server. If successful, the issue is resolved.
2. Check messages.txt for Errors:
- If the server still fails to start, inspect the messages.txt file for error messages
- Refer to the OCLC Support Center for articles related to the errors you observe
3. Start EZproxy in Debug Mode:
- If the messages.txt file appears clean, start EZproxy in debug mode
- Open a terminal screen, navigate to the EZproxy directory, and issue the command:
- Check the OCLC Support Center for articles regarding any errors encountered in debug mode
4. Contact Support:
- If errors persist or are unresolved, and there are no relevant articles in the OCLC Support Center, contact OCLC Support.
- Provide a copy of your config.txt file, messages.txt file, and any errors produced by
For comprehensive assistance and timely resolution, contact support, ensuring that you furnish all necessary files and information related to the issue.
Here are some steps to take to find out what the error is and fix it:
- Go to the edit you made in the Config.txt file and if it is pointing to a file, make sure you spelled it correctly, or that the file is in the location you are pointing.
- Try to restart your EZproxy server again. If it works, you solved the issue.
- If it does not work, check your messages.txt file.
- To find out what the error is, open a command prompt window, change your current directory to the EZproxy directory, and then issue the command:
5. EZproxy will either start, or it will display an error message. If it displays an error message, this problem must be corrected before it will be possible to run EZproxy. Once this command can start EZproxy, try restarting the EZproxy service.