About keilinw

keilinw · ‎10-27-2016

Upon a brand new installation as root and starting as root, I get the following error message: Any ideas? Unable to initialize modular input "alexa" defined inside the app "alexa": Introspecting scheme=alexa: script running failed (exited with code 1).

keilinw · ‎10-26-2016

Running the Alexa listener requires Running Splunk as a privileged user which seems to violate some security principles. Perhaps we can set the listener up on a higher port, run as a non privileged user, and set up a proxy to pass the income 443 requests to the new high port?

keilinw · ‎10-26-2016

Inspired by this blog: http://blogs.splunk.com/2016/09/08/talk-to-splunk-with-amazon-alexa/ I followed the instructions found here: https://github.com/damiendallimore/SplunkModularInputsJavaFramework/blob/master/alexa/docs/README.md I've gotten most everything set up and working correctly. However, I don't see where the Splunk Alexa App is listening on any port: sudo netstat -plnt ... all the normal stuff plus: tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 4468/splunkd When configuring the Alexa Stanza, I've tried multiple variations of the endpoint setting. IE. localhost/alexa https://localhost/alexa localhost:443/alexa mydomain/alexa https://mydomain/alexa mydomain:443/alexa I also have tried restarting the server as well as the Splunk App separately. Yet no matter what I do, I never see anything on the server actually listening on port 443. Any ideas?

Posts	3
Solutions	0
Karma Given	0
Karma Received	0
Member Since	‎10-26-2016

Online Status	Offline
Date Last Visited	‎06-05-2020 02:04 AM

Talk to Splunk with Amazon Alexa not starting with...

Re: Talk to Splunk with Amazon Alexa: Why am I get...

Talk to Splunk with Amazon Alexa: How to verify th...