I have a case with a deployment server where I renamed an app but didn't update the serverclass.conf.
What happened is that Splunk restarts and does log an error in splunkd.log about the missing app.
I would like to check ahead of time to make sure I don't restart Splunk or reload with a buggy serverclass.conf.
Has anyone written such a checker?
/opt/splunk/bin/splunk reload deploy-server
Hi @woodcock . I did a test today with a missing class (test using Splunk 6.6)
Your session is invalid. Please login.
Splunk username: xxxx
Login successful, running command...
There was no reported error that I was missing an app. I had actually renamed an app.
Splunk allowed me to restart with the missing app.
Bummer. That is the only possibility.
Other than maybe btool, which will not classify (just report).