The venerable old-skool Splunk forums are now closed. Feel free to search for old content here, but new posts are no longer supported.

Instead, please visit the thriving community at answers.splunk.com to ask and answer questions about your Splunk deployment and how to get the most out of it.

Forums: SplunkAdministration: changes which trigger upgrade process

Previous Topic: Admin password in free edition  |   Next Topic: Best practice for pre-filtering a bunch of msgs?


Posts 1–4 of 4
1
posted by: ualbanytech  |  posts
date: March 15, 2010
permalink

Does anyone know if there is a particular file Splunk looks for to determine if the Splunk version has changed?

Background. Using Google Slack project (wrapper around rsync or ssh) to update my forwarders.

Periodically, something is causing Splunk to think its version has changed and I get the license agreement prompt and upgrade confirmation prompt.

I can bypass the license agreement with --accept-license but have not found a way to bypass the upgrade confirmation (want force "y").

This causes a problem since we regularly restart our services through crontabs and Splunk fails to start when this situation arises.

2
posted by: gkanapathy  |  posts
date: March 15, 2010
permalink

You can add --answer-yes to bypass any prompt with a yes answer, which includes the upgrade and creation of new indexes at startup.

Also, it's the presence of file called "ftr" or maybe ".ftr" (first time run) in the Splunk home that does this, but that shouldn't matter with the previous tip.

3
posted by: ualbanytech  |  posts
date: March 16, 2010
permalink

Very nice. Thanks!

4
posted by: ualbanytech  |  posts
date: March 19, 2010
permalink

Just wanted to add I just found the watchdog object which may help people.

http://www.splunk.com/base/Documentation/4.0.10/Installation/StartSplunkforthefirsttime

Section
"Start and disable individual processes"