Clustered Environments:

1. If the GoAnywhere service is failing to start, the first place to look is the Tomcat logs.

• Tomcat logs (from each server) [installDir]/goanywhere/tomcat/logs/Catalina.out

• If running on Windows, look for:

1. Commons-Daemon(ceationDate).log
2. Stderr(ceationDate).log
3. Stdout(ceationDate).log

2. If no errors are found in the Tomcat logs, and you see the following logged event in the Catalina.out
log (stdout.log for windows) “Initializing global log file '[globalLogLocation]\GoAnywhere\userdata\logs\goanywhere.log'” then you want to then check the
GoAnywhere log location.

• GoAnywhere.log from the global log location defined for the cluster

3. In the GoAnywhere log, if you see that the node specific log has been initialized, then you will want to look at the System Specific GoAnywhere log file. I have copied an example of what that looks like in the GoAnywere.log file as well.

• “Switching global log file over to system specific log file '\\[globalLogLocation]\\userdata\logs\goanywhere_[systemName].log'.”
• System Specific goanywhere_[systemName].log files from the global log location.

Non-Clustered Environments:

1. If the GoAnywhere service is failing to start, the first place to look is the Tomcat logs.

• Tomcat logs (from each server) [installDir]/goanywhere/tomcat/logs/Catalina.out
• If running on Windows, look for:

1. Commons-Daemon(ceationDate).log
2. Stderr(ceationDate).log
3. Stdout(ceationDate).log

2. If no errors are found in the Tomcat logs, and you see the following logged event in the Catalina.out log (stdout.log for windows) “Initializing global log file '[InstallDir]\GoAnywhere\userdata\logs\goanywhere.log” then you want to then check the GoAnywhere log location.

• GoAnywhere.log [InstallDir]\GoAnywhere\userdata\logs\goanywhere.log