I have installed 'splunk-5.0.4-172409-x64-release.msi' in my local machine (Windows-7, 64 bit) as Local System User.
Installation is done successfully and I can see Splunkd and SplunkWeb services in my services window.
But when I tried to access the Splunk Web, I couldn't connect to the Splunk Web. And browser prompts "could not connect to localhost:8000". Then, I checked in Services wheather servicers are running or not. I found SplunkWeb is not Started but Splunkd. I mannually started SplunkWeb, still not able to connect to Splunk Web.
Any Idea?
First of all thanks to all who has responded on this thread. This issue kind of solved now. Seems there was some issue in my laptop. Once I restarted and installed the splunk it worked. Though, its good idea to use command line options for start/stop/restart.
First of all thanks to all who has responded on this thread. This issue kind of solved now. Seems there was some issue in my laptop. Once I restarted and installed the splunk it worked. Though, its good idea to use command line options for start/stop/restart.
You will find that on a windows machine it is better to use the Splunk.exe stop / start / restart command instead of Windows Service Manager.
This command tends to give more errors details when you start up the process.
BTW: This is a network application and it requires the ability to logon as Network Service so it can open the ports and be accessed by the network. Change the service from LSA to Network Services.
I've seen this a number of times, and I'm not sure why it happens, but to fix it I stop both services, and then start splunk from the commandline. This will start both splunkd and splunkweb.
splunk_home\bin\splunk.exe start
You may need to run the cmd window as administrator to review the output, and check for errors. If there is a problem starting one of the services it will tell you in the output.
If you see an error in the cmd window that you don't understand, then post it here.
Is windows firewall blocking the connection? You'll have to add an exception if so.
Check your var/log/splunk for some error messages. Specially in splunkd.log and web_service.log.