Troubleshooting |
Top Previous Next |
If you have questions or need support please check the PAWS Developer Forums, and the PAWS FAQs.
The following are some basic troubleshooting guidelines for PAWS.
If a method request call is missing arguments (children elements), the service may not be invoked at all. However, a response indicating the failure, often with a stack trace, is returned in such cases.
To troubleshoot infrastructure issues, use these tools:
•Web Services -- Review the web service logs accessible via the CLI command file get activelog tomcat/logs/platform-api/log4j/*. •Web Server -- Verify Tomcat's availability via the CLI command utils service list. Review the Tomcat logs accessible via the CLI command file get activelog tomcat/logs/*. Execute Tomcat diagnostic tests using the CLI command utils diagnose test. The results of these tests are recorded in the Tomcat logs directory and the Tomcat catalina.out log file. If needed, restart Tomcat using the CLI command utils service.stop|start|restart Cisco Tomcat. •Operating System -- Use the Serviceability GUI, OS Administration GUI, and CLI as you would with any other OS related issue. If needed, Cisco TAC can provide lower level access to the OS via a remote support account.
In many cases you may need the current Session ID to troubleshoot the error. Search for Session IDs in these logs:
Action ID:Sequence ID:Server Group:Server:Reboot:Upgrade Action ID:Sequence ID:Server Group:Server:Cancel
If you need additional help with PAWS, you can open a developer support case.
Action ID:Sequence ID:Server Group:Server:Cancel
|