<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why does Splunk enter version upgrade setup whenever we try to restart services on our Splunk forwarder? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156347#M31705</link>
    <description>&lt;P&gt;Seriously? How is this check performed and why isn't it working properly? I'm seeing this as well--looks like a bug to me!&lt;/P&gt;

&lt;P&gt;What's more it keeps happening even if I agree to the 'upgrade', which does nothing, because there isn't one.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jun 2015 03:42:39 GMT</pubDate>
    <dc:creator>cmeo</dc:creator>
    <dc:date>2015-06-17T03:42:39Z</dc:date>
    <item>
      <title>Why does Splunk enter version upgrade setup whenever we try to restart services on our Splunk forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156345#M31703</link>
      <description>&lt;P&gt;We have been trying to restart splunk services on a forwarder as it had stopped working some time back, but when you try any option (start/stop), splunk seems to enter an upgrade setup and the following message turns up:&lt;/P&gt;

&lt;P&gt;Do you agree with this license? [y/n]: y&lt;/P&gt;

&lt;P&gt;This appears to be an upgrade of Splunk.&lt;BR /&gt;
--------------------------------------------------------------------------------)&lt;/P&gt;

&lt;P&gt;Splunk has detected an older version of Splunk installed on this machine. To&lt;BR /&gt;
finish upgrading to the new version, Splunk's installer will automatically&lt;BR /&gt;
update and alter your current configuration files. Deprecated configuration&lt;BR /&gt;
files will be renamed with a .deprecated extension.&lt;/P&gt;

&lt;P&gt;You can choose to preview the changes that will be made to your configuration&lt;BR /&gt;
files before proceeding with the migration and upgrade:&lt;/P&gt;

&lt;P&gt;If you want to migrate and upgrade without previewing the changes that will be&lt;BR /&gt;
made to your existing configuration files, choose 'y'.&lt;BR /&gt;
If you want to see what changes will be made before you proceed with the&lt;BR /&gt;
upgrade, choose 'n'.&lt;/P&gt;

&lt;P&gt;Perform migration and upgrade without previewing configuration changes? [y/n] n&lt;/P&gt;

&lt;P&gt;-- Migration information is being logged to '/apps/splunk/var/log/splunk/migration.log.2015-04-23.11-49-27' --&lt;/P&gt;

&lt;P&gt;Migrating to:&lt;BR /&gt;
VERSION=6.1.2&lt;BR /&gt;
BUILD=213098&lt;BR /&gt;
PRODUCT=splunk&lt;BR /&gt;
PLATFORM=Linux-x86_64&lt;/P&gt;

&lt;P&gt;********** BEGIN PREVIEW OF CONFIGURATION FILE MIGRATION **********&lt;/P&gt;

&lt;P&gt;An error occurred: In order to migrate, Splunkd must not be running.&lt;BR /&gt;
[splunkadm@s220823vaps7016 bin]$&lt;/P&gt;

&lt;P&gt;Has anyone else faced this? Please suggest what can be done to fix this. Please note this is happening on only the particular forwarder.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2015 05:56:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156345#M31703</guid>
      <dc:creator>saikatr</dc:creator>
      <dc:date>2015-04-24T05:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Splunk enter version upgrade setup whenever we try to restart services on our Splunk forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156346#M31704</link>
      <description>&lt;P&gt;Hi saikatr&lt;BR /&gt;
 - retry  stopping splunkd &lt;BR /&gt;
 - if it already no work just copy all your apps which are in app directory &lt;BR /&gt;
 - then  uninstall splunk instance and re install another instance.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2015 09:32:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156346#M31704</guid>
      <dc:creator>chimell</dc:creator>
      <dc:date>2015-04-24T09:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Splunk enter version upgrade setup whenever we try to restart services on our Splunk forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156347#M31705</link>
      <description>&lt;P&gt;Seriously? How is this check performed and why isn't it working properly? I'm seeing this as well--looks like a bug to me!&lt;/P&gt;

&lt;P&gt;What's more it keeps happening even if I agree to the 'upgrade', which does nothing, because there isn't one.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2015 03:42:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156347#M31705</guid>
      <dc:creator>cmeo</dc:creator>
      <dc:date>2015-06-17T03:42:39Z</dc:date>
    </item>
    <item>
      <title>Re: Why does Splunk enter version upgrade setup whenever we try to restart services on our Splunk forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156348#M31706</link>
      <description>&lt;P&gt;I am getting this with the docker container version of the splunk forwarder. I'm struggling to find a proper and consistent fix.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 17:39:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-does-Splunk-enter-version-upgrade-setup-whenever-we-try-to/m-p/156348#M31706</guid>
      <dc:creator>stringa</dc:creator>
      <dc:date>2017-06-06T17:39:37Z</dc:date>
    </item>
  </channel>
</rss>

