![]() ![]() Moreover the "Interval Input" field is a nice "select field", where if you choose the "Cron Schedule" another selection of boxes appear to guide you in the process of setting the right schedule. I'm trying to setup my personal Modular Input, but the way it renders in the Manager (the "Add Data" section) is simply awfull: the Splunk default ones are just fancy and with great interfaces, while mine is just simple.Īll the tutorial on the Splunk documentation explain how to write the "manager.xml" file, and that's fine, but with that I cannot, for example, have a multi-step configuration, like for the "Scripts" one where I have "Select Source -> Input Settings -> Review -> Done". ![]() Here's the SplunkD log I get:ġ0-27-2016 17:35:52.069 -0400 ERROR ModularInputs - Argument validation for scheme=alexa: Can't determine timestampTolerance value, will revert to default value.ġ0-27-2016 17:35:52.155 -0400 INFO ExecProcessor - Removing status item "/opt/splunk/etc/apps/alexa/bin/alexa.py (isModInput=yes)ġ0-27-2016 17:35:52.157 -0400 INFO ExecProcessor - New scheduled exec process: python /opt/splunk/etc/apps/alexa/bin/alexa.pyġ0-27-2016 17:35:52.840 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" Probing socket connection to SplunkD failed.Either SplunkD has exited ,or if not, check that your DNS configuration is resolving your system's hostname (splunklin) correctly : Connection refusedġ0-27-2016 17:35:53.474 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" SLF4J: Failed to load class "".ġ0-27-2016 17:35:53.474 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" SLF4J: Defaulting to no-operation (NOP) logger implementationġ0-27-2016 17:35:53.474 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" SLF4J: See for further details.ġ0-27-2016 17:36:02.841 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" Probing socket connection to SplunkD failed.Either SplunkD has exited ,or if not, check that your DNS configuration is resolving your system's hostname (splunklin) correctly : Connection refusedġ0-27-2016 17:36:12.842 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" Probing socket connection to SplunkD failed.Either SplunkD has exited ,or if not, check that your DNS configuration is resolving your system's hostname (splunklin) correctly : Connection refusedġ0-27-2016 17:36:12.842 -0400 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/alexa/bin/alexa.py" Determined that Splunk has probably exited, HARI KARI. ![]() ![]() Right after I hit save netstat shows listening for about 10 seconds, and then craps out. The modular input sets the endpoint to /alexa. So it can actually resolve either name to the internal IP address (pinging either one works). Name resolution might have been an issue, but I believe i resolved this by editing /etc/hosts (it's Centos) with the following line: The firewall NATs 443 to internal 443 on my Splunk server by IP. The Splunk server is called "splunklin" and I use dynamic DNS to direct external traffic to (changed for anonymity). Splunkd.log shows: ERROR AdminManagerExternal - Stack trace from python handler:\nTraceback (most recent call last):\n File "/opt/splunk/lib/python2.7/site-packages/splunk/admin.py", line 70, in init\n hand.execute(info)\n File "/opt/splunk/lib/python2.7/site-packages/splunk/admin.py", line 530, in execute\n if self.requestedAction = ACTION_EDIT: self.handleEdit(confInfo)\n File "/opt/splunk/etc/apps/splunk-add-on-jira-alerts/bin/jira_alerts_install_endpoint.py", line 41, in handleEdit\n if not validate_jira_settings(jira_settings):\n File "/opt/splunk/etc/apps/splunk-add-on-jira-alerts/bin/jira_helpers.py", line 22, in validate_jira_settings\n timeout=10\n File "/opt/splunk/lib/python2.7/site-packages/requests/models.py", line 763, in json\n return json.loads(self.text, **kwargs)\n File "/opt/splunk/lib/python2.7/json/_init_.py", line 338, in loads\n return _default_code(s)\n File "/opt/splunk/lib/python2.7/json/decoder.py", line 366, in decode\n obj, end = self.raw_decode(s, idx=_w(s, 0).end())\n File "/opt/splunk/lib/python2.7/json/decoder.Hi there, it seems when I try to run the Talk to Splunk with Amazon Alexa app, create a modular input, it starts to listen on 443 (I can see this from netstat), but then stops listening after a few seconds and logs errors (below). Getting the following error in the setup page: Error while posting to url=/servicesNS/nobody/splunk-add-on-jira-alerts/admin/jira_alerts_install/jiraĪll credentials are entered in the input boxes. ![]()
0 Comments
Leave a Reply. |