Running "reload deploy-server" from CLI shows "read operation timed out" error

Available Languages

Updated:September 29, 2026
Document ID:SPLK046344

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise

Description

While running the reload deploy-server command from CLI to push a change the following error will shows up 
Socket error communicating with splunkd (error=('The read operation timed out',)), path = /services/deployment/server/config/_reload

Investigation

At the splunkd_access.log file, it was confirmed that the request to splunkd was exceeding the default 30-sec timeout. 
127.0.0.1 - user [09/Jul/2021:13:10:31.450 +0700] "POST /services/deployment/server/config/_reload HTTP/1.0" 200 3828 - - - 34649m 

Resolution

This is happening because the default timeout value (30 seconds) is being exceeded resulting in the reload deploy-server command timing out.  The -timeout option is needed to explicitly increase the timeout. 
# splunk reload deploy-server -timeout 200
 With the -timeout option, the change should push properly.
Reloading serverclass(es).

This timeout value is not configurable and needs to be called out as an argument.

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products