Getting Data In

Timeout talking to Deployment Server Windows

jwhughes58
Contributor

I'm seeing this message in the splunkd.log file just before a Universal Forwarder starts a shutdown.

11-25-2017 18:38:11.690 -0800 INFO  NetUtils - Connect timeout - waited for 5 seconds. ip=aaa.bbb.ccc.ddd port=8089
11-25-2017 18:38:11.690 -0800 WARN  HTTPClient - Connect to=deployment_server:8089 timed out; exceeded 5sec
11-25-2017 18:38:11.690 -0800 WARN  HTTPClient - Download file cancelled due to: Connect to=deployment_server:8089 timed out; exceeded 5sec

I'm trying to figure out if the value of 5 seconds can be changed. I haven't found any file with 5 seconds in it. Any ideas where the value of 5 seconds comes from?

TIA,
Joe

0 Karma

woodcock
Esteemed Legend

You can specify a different check-in interval on a per client, or per class basis by tuning the phoneHomeIntervalInSecs and handshakeRetryIntervalInSecs parameters in deploymentclient.conf:
http://docs.splunk.com/Documentation/Splunk/latest/Admin/Deploymentclientconf

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...