I encountered a similar situation recently. Although the problem disappeared before I could debug it further. Try running 'netstat -anb' and see what is binding port 8000. (Or whatever SplunkWeb is supposed to bind to). Unfortunately, I was only running 'netstat -an' when I found that something had port 8000 stuck in TIME_WAIT. By the time I discovered 'netstat -anb' to see what process was stealing this port, it had already disappeared, and SplunkWeb managed to start. ... View more