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_input" defined inside the app "website_input": 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_input/bin/

To test this, go to the path /opt/splunk/etc/apps/website_input/bin/ using the CLI:

cd /opt/splunk/etc/apps/website_input/bin/

Next, run Splunk's python against the file:

/opt/splunk/bin/splunk cmd python

This should show an error, such as:

Traceback (most recent call last):
  File "", line 1, in <module>
NameError: name 'somethingnotdefined' is not defined


ant-contrib-0.6.jar (117 KB) Luke Murphey, 02/06/2017 11:46 PM

yuicompressor-2.4.7.jar (870 KB) Luke Murphey, 02/07/2017 07:55 AM

yuicompressor-2.4.8.jar (769 KB) Luke Murphey, 02/07/2017 07:56 AM

splunkbuild.jar (11.6 KB) Luke Murphey, 02/18/2017 06:24 AM