Cannot open localhost 8000 on my company's computer

[kangje168]

Hi there,

I was using Splunk Entreprise on my company's computer in this afternoon, sudenly after I installed the apps for windows, I can not get access to the localhost 8000/ any more. Due to this is on my company's computer, I am not autorised to restart or stop Splunkd or Splunkweb in the Service. Any solution?

Thanks in advance.

[kangje168 · Accepted solution]

No worry guys, my computer died several days ago and IT made a new system for me. Now, splunk back ///

[gmchenry]

I installed and tried this on my laptop. Open up a command prompt, and if you go to where Splunk is installed (on mine it was c:\Program Files\Splunk) then go into the "bin" subdirectory you should be able to stop/start/restart from there.

When you do the restart it should pop a line up that says:
" the Splunk web interface is at http://hostname:xxxx"
The xxxx should be the port to use. Default is usually 8000 but on this instance, another process was using it (msirest.exe) and it had redirected to port 8001.

[kangje168]

Yes, I tried your method, cmd returns "mgmt port 8089 is already bound, splunk need to use this port"

[davebrooking]

In the command prompt window, and from the bin subdirectory mentioned by gmchenry can you enter the command

splunk status

Does that say splunkd is in a Running or a Stopped state?

I had a similar problem some time ago whereby Splunkd had crashed, and so was in a stopped state, but it hadn't cleaned up all its child processes. This left at least one orphan process which maintained its association with port 8089. I think the root cause of my particular problem (SPL-86939) was fixed in 6.1.4.

It is also possible that a process totally unrelated to Splunk is also needing to use port 8089 and so the two are programs are conflicting over port 8089. If that's the case you'll need to change one of the programs to use a different port.

To find the process that is associated with a port you can use the netstat command

netstat -ano

This blog item may help you identify the process that is associated with the port (I've not tested the details in the blog item, and so can't comment on its validity).

[somesoni2]

Splunkd service could be down. Either work with your windows admin to get it started and/or check splunkd.log for specific errors.

[kangje168]

Emmm; the in the service window; it shows that splunkd is working