To determine what is causing the service to fail to start, we need to find the correct log file.

For clustered environments

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:

• Commons-Daemon(ceationDate).log                     
• Stderr(ceationDate).log                     
• Stdout(ceationDate).log

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, defined in the cluster XML file. If you see that the node-specific log has been initialised, 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.

For non-clustered environments

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:

• Commons-Daemon(ceationDate).log
• Stderr(ceationDate).log
• Stdout(ceationDate).log

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