Socket error communicating with splunkd (error=The read operation timed out), path = /services/deployment/server/config/_reload
I get this error whenever i try to reload my deployment server to push out new configs. It wont let me make any changes. I have opened up a ticket with Splunk support (Case# - 201659) but to no avail. Has anyone else seen this type of issue and know how to fix it or what is causing the issue?
Hi, This might be in your environment using in 1 server 2 components such like we were using 2 component in 1 server ( SH & DS ), so we have faced same issue and then separated both in separate servers and then the command was executing perfectly.
This happened to us a lot after we upgraded to splunk 6.4 version, We ended up needing to use the deployment command "splunk reload deploy-server -timeout 200" where 200 is 200 seconds. You are just telling splunk to give the deployment a little more time before it times out. This could be required if you are deploying a large number of apps to a large number of servers. Hope that helps!
Hi. Has anyone figured what causes the socket error message? I'm getting the same error, but I feel like adding the timeout flag on the reload deploy-server command is just hiding the problem, not actually fixing it. I've noticed that almost all my RAM is used for cache, but I don't know if this is related or not.
I have the same problem. Take a look at this posting:
The above does not work for me, I end up being presented with the following:
"Too many HTTP threads (659) already running, try again later
The server can not presently handle the given request."
Did you ever find a solution?