Troubleshooting » History » Version 2
Luke Murphey, 05/19/2016 05:36 PM
| 1 | 1 | Luke Murphey | h1. Troubleshooting |
|---|---|---|---|
| 2 | 1 | Luke Murphey | |
| 3 | 1 | Luke Murphey | Below are some pointers to help in debugging the application: |
| 4 | 1 | Luke Murphey | |
| 5 | 1 | Luke Murphey | h2. Search for modular input errors |
| 6 | 1 | Luke Murphey | |
| 7 | 1 | Luke Murphey | Run a search for the following and see if the logs indicate a problem with the modular input: |
| 8 | 1 | Luke Murphey | |
| 9 | 1 | Luke Murphey | <pre> |
| 10 | 1 | Luke Murphey | index=_internal sourcetype=web_availability_modular_input |
| 11 | 1 | Luke Murphey | </pre> |
| 12 | 1 | Luke Murphey | |
| 13 | 1 | Luke Murphey | h2. Search for REST handler errors |
| 14 | 1 | Luke Murphey | |
| 15 | 1 | Luke Murphey | Run a search for the following and see if the logs indicate a problem with the REST handler: |
| 16 | 1 | Luke Murphey | |
| 17 | 1 | Luke Murphey | <pre> |
| 18 | 1 | Luke Murphey | index=_internal source=*website_monitoring_rest_handler.log |
| 19 | 1 | Luke Murphey | </pre> |
| 20 | 2 | Luke Murphey | |
| 21 | 2 | Luke Murphey | h2. Input fails and generates a "ConnectionError" |
| 22 | 2 | Luke Murphey | |
| 23 | 2 | Luke Murphey | This can happen when the following is |
| 24 | 2 | Luke Murphey | |
| 25 | 2 | Luke Murphey | # The IP address is invalid (if referring to the host by IP) |
| 26 | 2 | Luke Murphey | # The domain name cannot be resolved |
| 27 | 2 | Luke Murphey | # The port number provided is invalid (if a port is specified) |
| 28 | 2 | Luke Murphey | # Network connectivity is lost or a firewall blocks the connection |