I accidentally ran another web server on the same port as the Splunk Web server (8000) and since then, I've been unable to start Splunk. The start process gets stuck at "Waiting for webserver at http://127.0.0.1:8000"; and I am left unable to access the web UI. What I've tried: I've stopped the other web server I've changed Splunk web and Splunkd to a variety of different ports, no difference I've checked my local firewall, there are no rules which could affect this I've tried with and without SSL I've restarted several times Splunk says the http port is open during startup There's nothing else on the ports I've tried All I've done for this to happen is run something on the same port, but that should have stopped being an issue as soon as I stopped the other listener, or certainly after having changed Splunk to different ports. ... View more

I'm trying to connect to a preconfigured JMS queue inside Jboss Hornetq using the JMS Messaging Modular Input add-on. I'm receiving the following error: ERROR ExecProcessor - message from "python D:/Splunk/etc/apps/jms_ta/bin/jms.py" Stanza jms://queue/MyQueue: Error connecting : javax.naming.NameNotFoundException: -- service jboss.naming.context.java.jboss.exported.MyQueue With the following configuration: Queue name -- queue/MyQueue JMS Provider URL -- remote://localhost:4447 JNDI initial context factory -- org.jboss.naming.remote.client.InitialContextFactory JMS Connection factory -- jms/RemoteConnectionFactory I'm inclined to trust the above configuration - it corresponds to my app server configuration. What I'm currently suspecting is that jboss.naming.context.java.jboss.exported.MyQueue from the error message is relevant - I've seen the actual JNDI used in other applications resolves to jboss.naming.context.java.jboss.exported.jms.queue.MyQueue - could the missing ".jms.queue" in my jndi be indicative of anything? From the research I've done, I found some people have had a similar problem with a missing ".jms.queue", some eccentricity of Jboss has resulted in malformed JNDI with some applications - could this be what's happening? Has anyone else tried to connect to Jboss with the JMS app? ... View more