<?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: Splunkforwarder 7.3.3 linux enable boot-start bug in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502756#M17243</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Summary of the issue:&lt;/STRONG&gt;&lt;BR /&gt;
Splunk 6.0.0 - Splunk 7.2.1 defaults to using &lt;STRONG&gt;init.d&lt;/STRONG&gt; when enabling boot start&lt;BR /&gt;
Splunk 7.2.2 - Splunk 7.2.9 defaults to using &lt;STRONG&gt;systemd&lt;/STRONG&gt; when enabling boot start&lt;BR /&gt;
Splunk 7.3.0 - Splunk 8.x defaults to using &lt;STRONG&gt;init.d&lt;/STRONG&gt; when enabling boot start&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;systemd&lt;/STRONG&gt; defaults to prompting for root credentials upon stop/start/restart of Splunk&lt;/P&gt;

&lt;P&gt;Here is a simple fix if you have encountered this issue and prefer to use the traditional &lt;STRONG&gt;init.d&lt;/STRONG&gt; scripts vs &lt;STRONG&gt;systemd&lt;/STRONG&gt;. &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Splunk Enterprise/Heavy Forwarder example&lt;/STRONG&gt; (note: replace the splunk user below with the account you run splunk as):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sudo /opt/splunk/bin/splunk disable boot-start
sudo /opt/splunk/bin/splunk enable boot-start -user splunk -systemd-managed 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Splunk Universal Forwarder example&lt;/STRONG&gt; (note: replace the splunk user below with the account you run splunk as):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sudo /opt/splunkforwarder/bin/splunk disable boot-start
sudo /opt/splunkforwarder/bin/splunk enable boot-start -user splunk -systemd-managed 0
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 31 Dec 2019 19:04:17 GMT</pubDate>
    <dc:creator>bandit</dc:creator>
    <dc:date>2019-12-31T19:04:17Z</dc:date>
    <item>
      <title>Splunkforwarder 7.3.3 linux enable boot-start bug</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502751#M17238</link>
      <description>&lt;P&gt;What is the point of the "splunk enable boot-start" enabling then immediately disabling the service at boot-start?&lt;/P&gt;

&lt;H4&gt;cat /etc/system-release&lt;/H4&gt;

&lt;P&gt;Oracle Linux Server release 7.6&lt;/P&gt;

&lt;H4&gt;/opt/splunkforwarder/bin/splunk version&lt;/H4&gt;

&lt;P&gt;Splunk Universal Forwarder 7.3.3 (build 7af3758d0d5e)&lt;/P&gt;

&lt;H4&gt;systemctl enable splunk.service&lt;/H4&gt;

&lt;P&gt;Created symlink from /etc/systemd/system/multi-user.target.wants/splunk.service to /usr/lib/systemd/system/splunk.service.&lt;/P&gt;

&lt;H4&gt;reboot&lt;/H4&gt;

&lt;P&gt;...&lt;/P&gt;

&lt;H4&gt;/opt/splunkforwarder/bin/splunk status&lt;/H4&gt;

&lt;P&gt;splunkd is running (PID: 1772).&lt;BR /&gt;
splunk helpers are running (PIDs: 1776).&lt;/P&gt;

&lt;H4&gt;/opt/splunkforwarder/bin/splunk enable boot-start&lt;/H4&gt;

&lt;P&gt;Note: Forwarding request to 'systemctl enable splunk.service'.&lt;BR /&gt;
Note: Forwarding request to 'systemctl disable splunk.service'.&lt;BR /&gt;
Removed symlink /etc/systemd/system/multi-user.target.wants/splunk.service.&lt;BR /&gt;
Init script installed at /etc/init.d/splunk.&lt;BR /&gt;
Init script is not configured to run at boot.&lt;/P&gt;

&lt;H4&gt;reboot&lt;/H4&gt;

&lt;P&gt;...&lt;/P&gt;

&lt;H4&gt;/opt/splunkforwarder/bin/splunk status&lt;/H4&gt;

&lt;P&gt;splunkd is not running.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 16:59:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502751#M17238</guid>
      <dc:creator>janglin</dc:creator>
      <dc:date>2019-12-09T16:59:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkforwarder 7.3.3 linux enable boot-start bug</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502752#M17239</link>
      <description>&lt;P&gt;(sorry about the font ... it cut&amp;amp;pasted that way)&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 17:01:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502752#M17239</guid>
      <dc:creator>janglin</dc:creator>
      <dc:date>2019-12-09T17:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkforwarder 7.3.3 linux enable boot-start bug</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502753#M17240</link>
      <description>&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk enable boot-start -systemd-managed 0&lt;/STRONG&gt;&lt;BR /&gt;
Note: Forwarding request to 'systemctl enable splunk.service'.&lt;BR /&gt;
Created symlink from /etc/systemd/system/multi-user.target.wants/splunk.service to /usr/lib/systemd/system/splunk.service.&lt;BR /&gt;
Note: Forwarding request to 'systemctl disable splunk.service'.&lt;BR /&gt;
Removed symlink /etc/systemd/system/multi-user.target.wants/splunk.service.&lt;BR /&gt;
Init script installed at /etc/init.d/splunk.&lt;BR /&gt;
Init script is not configured to run at boot.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk enable boot-start -systemd-managed 1&lt;/STRONG&gt;&lt;BR /&gt;
splunk is currently running, please stop it before running enable/disable boot-start&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk stop&lt;/STRONG&gt;&lt;BR /&gt;
Stopping splunkd...&lt;BR /&gt;
Shutting down.  Please wait, as this may take a few minutes.&lt;BR /&gt;
                                                           [  OK  ]&lt;BR /&gt;
Stopping splunk helpers...&lt;BR /&gt;
                                                           [  OK  ]&lt;BR /&gt;
Done.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk enable boot-start -systemd-managed 1&lt;/STRONG&gt;&lt;BR /&gt;
Initd script /etc/init.d/splunk exists. splunk is currently enabled as init.d bootstart service.&lt;BR /&gt;
Please run "splunk disable boot-start" first to disable it as init.d boot-start service&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk disable boot-start&lt;/STRONG&gt;&lt;BR /&gt;
Disabled.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk enable boot-start -systemd-managed 1&lt;/STRONG&gt;&lt;BR /&gt;
Systemd unit file installed at /etc/systemd/system/SplunkForwarder.service.&lt;BR /&gt;
Configured as systemd managed service.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk status&lt;/STRONG&gt;&lt;BR /&gt;
splunkd is not running.&lt;/P&gt;

&lt;P&gt;reboot ...&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/opt/splunkforwarder/bin/splunk status&lt;/STRONG&gt;&lt;BR /&gt;
splunkd is running (PID: 1221).&lt;BR /&gt;
splunk helpers are running (PIDs: 2324).&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 15:43:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502753#M17240</guid>
      <dc:creator>janglin</dc:creator>
      <dc:date>2019-12-12T15:43:43Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkforwarder 7.3.3 linux enable boot-start bug</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502754#M17241</link>
      <description>&lt;P&gt;It is a real pain for automation if we have to check whether a client is using systemd or init.d in order to configure the splunkforwarder to start properly on bootup.  This should be something that the "splunk enable boot-start" command figures out automagically.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 15:47:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502754#M17241</guid>
      <dc:creator>janglin</dc:creator>
      <dc:date>2019-12-12T15:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkforwarder 7.3.3 linux enable boot-start bug</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502755#M17242</link>
      <description>&lt;P&gt;Hi janglin-&lt;/P&gt;

&lt;P&gt;Splunk is in a tough spot right now regarding this.  Splunk needs to support both types of system start ups while acknowledging that a good chunk of the industry is slowing moving toward SystemD. &lt;BR /&gt;
There's some good documentation on it now &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.0/Admin/RunSplunkassystemdservice"&gt;here&lt;/A&gt; (apologies if you already saw this). &lt;/P&gt;

&lt;P&gt;Here's another page (older) that enables &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.0/Admin/ConfigureSplunktostartatboottime"&gt;init.d boot&lt;/A&gt; at start time.&lt;/P&gt;

&lt;P&gt;I hope this helps. &lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2019 18:54:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502755#M17242</guid>
      <dc:creator>BainM</dc:creator>
      <dc:date>2019-12-12T18:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkforwarder 7.3.3 linux enable boot-start bug</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502756#M17243</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Summary of the issue:&lt;/STRONG&gt;&lt;BR /&gt;
Splunk 6.0.0 - Splunk 7.2.1 defaults to using &lt;STRONG&gt;init.d&lt;/STRONG&gt; when enabling boot start&lt;BR /&gt;
Splunk 7.2.2 - Splunk 7.2.9 defaults to using &lt;STRONG&gt;systemd&lt;/STRONG&gt; when enabling boot start&lt;BR /&gt;
Splunk 7.3.0 - Splunk 8.x defaults to using &lt;STRONG&gt;init.d&lt;/STRONG&gt; when enabling boot start&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;systemd&lt;/STRONG&gt; defaults to prompting for root credentials upon stop/start/restart of Splunk&lt;/P&gt;

&lt;P&gt;Here is a simple fix if you have encountered this issue and prefer to use the traditional &lt;STRONG&gt;init.d&lt;/STRONG&gt; scripts vs &lt;STRONG&gt;systemd&lt;/STRONG&gt;. &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Splunk Enterprise/Heavy Forwarder example&lt;/STRONG&gt; (note: replace the splunk user below with the account you run splunk as):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sudo /opt/splunk/bin/splunk disable boot-start
sudo /opt/splunk/bin/splunk enable boot-start -user splunk -systemd-managed 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Splunk Universal Forwarder example&lt;/STRONG&gt; (note: replace the splunk user below with the account you run splunk as):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sudo /opt/splunkforwarder/bin/splunk disable boot-start
sudo /opt/splunkforwarder/bin/splunk enable boot-start -user splunk -systemd-managed 0
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 31 Dec 2019 19:04:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunkforwarder-7-3-3-linux-enable-boot-start-bug/m-p/502756#M17243</guid>
      <dc:creator>bandit</dc:creator>
      <dc:date>2019-12-31T19:04:17Z</dc:date>
    </item>
  </channel>
</rss>

