Troubleshooting » History » Version 3
Below are some pointers to help in debugging the application:
Search for modular input errors¶
Run a search for the following and see if the logs indicate a problem with the modular input:
Search for REST handler errors¶
Run a search for the following and see if the logs indicate a problem with the REST handler:
Input fails and generates a "ConnectionError"¶
This can happen when the following is
- The IP address is invalid (if referring to the host by IP)
- The domain name cannot be resolved
- The port number provided is invalid (if a port is specified)
- Network connectivity is lost or a firewall blocks the connection
Troubleshooting modular inputs that don't appear in the Splunk Manager¶
Look in the messages link in the top right of the page to see if you have a message like this:
Unable to initialize modular input "web_ping" defined inside the app "website_monitoring": Introspecting scheme=web_input: script running failed (exited with code 1).
You can search the internal log for related errors that indicate the modular input could not start:
index=_internal "ModularInputs - Unable to initialize modular input"
The best way to identify the source of the error if the modular input cannot be loaded by Splunk is to try to load it via Splunk's python interpreter directly.
Here is an example. Consider the modular input is in the following path: /opt/splunk/etc/apps/website_monitoring/bin/web_ping.py
To test this, go to the path /opt/splunk/etc/apps/website_monitoring/bin/ using the CLI:
Next, run Splunk's python against the file:
/opt/splunk/bin/splunk cmd python web_ping.py
This should show an error, such as:
Traceback (most recent call last): File "web_input.py", line 1, in <module> somethingnotdefined NameError: name 'somethingnotdefined' is not defined