Hello all,
Once a week it seems, I get the following error which requires a reboot, after which it works for a few days. This all started with the upgrade from 4.3.6 to 5.0.3:
500 Internal Server Error
ResponseNotReady
You are using 192.blahblahblah, which is connected to splunkd @000...
Any ideas would be greatly appreciated. This is happening on both single Splunk instances as well as distributed topology. All machines are Windows Server 2008 R2 VMs.
Thanks!
Are you binding proxy IP and port to splunk instance?
This error is likely due to Splunk being unable to talk to itself. It's a known issue with Windows, see:
This answer has the most detailed information, in terms of users' experience.
http://answers.splunk.com/answers/68368/splunk-web-throws-responsenotready-error
I too am getting this error after updating to 5.0.3 and have a case open. All my systems run on RHEL 6. No answer from Splunk yet.
Are you seeing splunk daemon not responding? This may happen with a busy/locked port [8089]