I am seeing this error happen frequently in our configuration with multiple DeploymentServers. Can anyone tell me what this mean, and maybe why it is happening?
Thank you!
This is normally nothing to worry about - what it usually means is you've just a splunk reload deploy-server
on your deployment server and clients are checking in and noticing that fact. There were some bugs in 5.0.2 around deployment server checkins. If you are running 5.0.2 for your deployment server, upgrade ASAP.
This is normally nothing to worry about - what it usually means is you've just a splunk reload deploy-server
on your deployment server and clients are checking in and noticing that fact. There were some bugs in 5.0.2 around deployment server checkins. If you are running 5.0.2 for your deployment server, upgrade ASAP.
This message is a prelude to the possibility restart, but is not always going to lead to one. When you issue the reload deploy-server
then that causes forwarders to look for new versions of deployed apps and redeploy if needed. If an app is defined as restartSplunkd=true
in serverclass.conf
then when that app is updated and forwarders that have it installed will restart.
I was concered since it appeared to he happening every few minutes causing restarts on all of the UF's it appears to have settled down at this point.
Thank you for the response!