Troubleshooting
This chapter lists some useful troubleshooting techniques that you can use when building Control API applications.
General Debugging Techniques
File Locations
The WSDL interface specifications are located in ZEUSHOME/zxtm/etc/wsdl/.
ZEUSHOME is the installation directory for your Traffic Manager software, typically /usr/local/zeus or /opt/zeus depending on your product variant.
Alternatively, download the WSDL files from the SOAP API page in the Online Help.
Log Files
In the event of a problem, review the following error logs:
- Traffic Manager core software: ZEUSHOME/log/errors
Validation errors and incorrect configuration problems are reported in this log file.
- Admin Server and Admin UI: ZEUSHOME/admin/log/errors
The Admin Server processes the SOAP requests and sends the new configuration to the Traffic Manager software. Any SOAP protocol or transport errors are reported here.
Snooping the SOAP Traffic
A Control API application sends SOAP requests to the Traffic Manager Admin Server, which typically listens using SSL on port 9090. If your SOAP toolkit does not support debugging or tracing, use a network snooping tool such as WireShark1 to inspect the SOAP request and response to verify that the request is sent correctly, and that the response does not contain any errors messages that are not reported by your application’s interface code.
If your SOAP transaction is encrypted with SSL, to enable inspection you must first disable SSL on the Admin Server by performing the following steps:
- Edit the file ZEUSHOME/admin/website and comment out the line “security!enabled yes”. To do this, prefix the line with a hash (#), as per the following:
# security!enabled yes- Restart the Traffic Manager software by typing the following command2:
$ZEUSHOME/restart-zeus($ZEUSHOME is the Traffic Manager software installation directory for your product variant.)
- Modify your Control API application to use an “http://” URL rather than an “https://” URL.