|
(→General Errors (Job Failures, etc.))
|
(Added in full path)
|
| Line 7: | |||
| == Agent Communication Issues (Timeouts, Transfer of Logs Failure, etc.) == | == Agent Communication Issues (Timeouts, Transfer of Logs Failure, etc.) == | ||
| - | * '''ah3agent.out''' from afflicted agent | + | * '''%AGENT_HOME%\var\log\ah3agent.out''' from afflicted agent |
| - | * '''ah3server.out''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.out''' from server |
| - | * '''ah3server.err''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.err''' from server |
| * '''installed.properties''' files from both the server and the afflicted agent. | * '''installed.properties''' files from both the server and the afflicted agent. | ||
| * Command trace output (designated by the black '''C:\>''' icon in the UI). | * Command trace output (designated by the black '''C:\>''' icon in the UI). | ||
| Line 18: | |||
| == General Errors (Job Failures, etc.) == | == General Errors (Job Failures, etc.) == | ||
| - | * '''ah3agent.out''' from afflicted agent | + | * '''%AGENT_HOME%\var\log\ah3agent.out''' from afflicted agent |
| - | * '''ah3server.out''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.out''' from server |
| - | * '''ah3server.err''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.err''' from server |
| * Command trace output (designated by the black '''C:\>''' icon in the UI). | * Command trace output (designated by the black '''C:\>''' icon in the UI). | ||
| ** It is also '''VERY HELPFUL''' to test and see if you get the same error outside of anthill. So, if you have a failed job step (such as a changelog or info step), try logging onto the agent box using the same account the agent is running as. Then try the step outside of anthill to see if the same error occurs. For example: <pre>Subversion command line: svn info --username anthillpro --password ***** --revision {2013-02-20 19:26:26 +0000} https://svn-repo/root | ** It is also '''VERY HELPFUL''' to test and see if you get the same error outside of anthill. So, if you have a failed job step (such as a changelog or info step), try logging onto the agent box using the same account the agent is running as. Then try the step outside of anthill to see if the same error occurs. For example: <pre>Subversion command line: svn info --username anthillpro --password ***** --revision {2013-02-20 19:26:26 +0000} https://svn-repo/root | ||
| Line 52: | |||
| == Script, Report, and UI Errors == | == Script, Report, and UI Errors == | ||
| - | * '''ah3server.out''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.out''' from server |
| - | * '''ah3server.err''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.err''' from server |
| * Screenshot of the UI of where the failure occurred | * Screenshot of the UI of where the failure occurred | ||
| * IF UI error (''jasper exception, catalina exception, etc.'') click on '''more info''' and provide the contents in the ticket | * IF UI error (''jasper exception, catalina exception, etc.'') click on '''more info''' and provide the contents in the ticket | ||
| Line 60: | |||
| * '''An emergency ticket should always be filed for ''production'' server outages.''' | * '''An emergency ticket should always be filed for ''production'' server outages.''' | ||
| - | * '''ah3server.out''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.out''' from server |
| - | * '''ah3server.err''' from server | + | * '''%SERVER_HOME%\var\log\ah3server.err''' from server |
| * Server startup script | * Server startup script | ||
| ** '''%SERVER_HOME%\bin\ah3server.cmd''' on Microsoft Windows platform. | ** '''%SERVER_HOME%\bin\ah3server.cmd''' on Microsoft Windows platform. | ||
| Line 72: | |||
| === Critical Note on Server Restart === | === Critical Note on Server Restart === | ||
| - | Before you even consider restarting the server, you will most likely want to do a quick scan of the '''ah3server.out''' logs for any sort of memory errors, specifically ''OutOfMemory'' errors. If you see an ''OutOfMemory'' error, we will also want a heap dump. You can get more information on how to do this by visiting the [[Dumps from a Java Process]] page. | + | Before you even consider restarting the server, you will most likely want to do a quick scan of the '''%SERVER_HOME%\var\log\ah3server.out''' logs for any sort of memory errors, specifically ''OutOfMemory'' errors. If you see an ''OutOfMemory'' error, we will also want a heap dump. You can get more information on how to do this by visiting the [[Dumps from a Java Process]] page. |
| == Stuck Requests/Build Lives == | == Stuck Requests/Build Lives == | ||
