<?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 Splunk service didn't start automatically after server  reboot in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399601#M9321</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We have Splunk Enteprise v. 6.6.3 Heavy Forwarders.&lt;BR /&gt;
1) We configured Splunk to start on reboot as our splunk_user by running&lt;BR /&gt;&lt;BR /&gt;
          "$SPLUNK_HOME$/bin/splunk enable boot-start -user splunk_user"&lt;BR /&gt;
2)  /etc/init.d/splunk script was created and &lt;BR /&gt;
     SPLUNK_OS_USER was set to splunk_user in /opt/splunk/etc/splunk-launch.conf&lt;BR /&gt;
3)  our heavy forwarders are set to be rebooted once per month and it was going ok .&lt;BR /&gt;
Splunk services were getting restarted automatically every time &lt;/P&gt;

&lt;P&gt;4) Recently we worked with our Linux Admins to increase ulimit -n on one of heavy forwarders.&lt;BR /&gt;
Our Unix admins made the required change on system level.&lt;BR /&gt;
They also updated /etc/init.d/splunk script by adding  the following to splunk_start()  and &lt;BR /&gt;
splunk_restart() functions:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  ulimit -Hn &amp;lt;value&amp;gt;
  ulimit -Sn  &amp;lt;value&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then Splunk was stopped and server was rebooted and this time Splunk service didn't start automatically &lt;BR /&gt;
We had to start it manually. &lt;/P&gt;

&lt;P&gt;What could be the reason and what's the best way to troubleshoot this and fix  it  if needed to prevent this from happening again&lt;/P&gt;

&lt;P&gt;Thank you in advance!&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 01:24:10 GMT</pubDate>
    <dc:creator>mlevsh</dc:creator>
    <dc:date>2020-09-30T01:24:10Z</dc:date>
    <item>
      <title>Splunk service didn't start automatically after server  reboot</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399601#M9321</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We have Splunk Enteprise v. 6.6.3 Heavy Forwarders.&lt;BR /&gt;
1) We configured Splunk to start on reboot as our splunk_user by running&lt;BR /&gt;&lt;BR /&gt;
          "$SPLUNK_HOME$/bin/splunk enable boot-start -user splunk_user"&lt;BR /&gt;
2)  /etc/init.d/splunk script was created and &lt;BR /&gt;
     SPLUNK_OS_USER was set to splunk_user in /opt/splunk/etc/splunk-launch.conf&lt;BR /&gt;
3)  our heavy forwarders are set to be rebooted once per month and it was going ok .&lt;BR /&gt;
Splunk services were getting restarted automatically every time &lt;/P&gt;

&lt;P&gt;4) Recently we worked with our Linux Admins to increase ulimit -n on one of heavy forwarders.&lt;BR /&gt;
Our Unix admins made the required change on system level.&lt;BR /&gt;
They also updated /etc/init.d/splunk script by adding  the following to splunk_start()  and &lt;BR /&gt;
splunk_restart() functions:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  ulimit -Hn &amp;lt;value&amp;gt;
  ulimit -Sn  &amp;lt;value&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then Splunk was stopped and server was rebooted and this time Splunk service didn't start automatically &lt;BR /&gt;
We had to start it manually. &lt;/P&gt;

&lt;P&gt;What could be the reason and what's the best way to troubleshoot this and fix  it  if needed to prevent this from happening again&lt;/P&gt;

&lt;P&gt;Thank you in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:24:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399601#M9321</guid>
      <dc:creator>mlevsh</dc:creator>
      <dc:date>2020-09-30T01:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk service didn't start automatically after server  reboot</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399602#M9322</link>
      <description>&lt;P&gt;We spoke about it at this thread and it might help you -  &lt;A href="https://answers.splunk.com/answers/683828/how-do-we-enable-a-forwarder-boot-start.html"&gt;How do we enable a forwarder boot-start?&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 20:04:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399602#M9322</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-07-17T20:04:26Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk service didn't start automatically after server  reboot</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399603#M9323</link>
      <description>&lt;P&gt;@ddrillic , thank you!&lt;BR /&gt;
I actually went through that thread and especially noted your post:&lt;BR /&gt;
"Very interesting - yesterday we checked a server that had this /etc/init.d/splunk file but the splunk process was not started 15 days ago when the server was rebooted. We ended up rebooting the server a couple of times and in these cases, Splunk did come up. Confusing ; -) "&lt;/P&gt;

&lt;P&gt;So it is still not clear for us why  splunk auto restart worked before and didn't work this time &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 20:21:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399603#M9323</guid>
      <dc:creator>mlevsh</dc:creator>
      <dc:date>2019-07-17T20:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk service didn't start automatically after server  reboot</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399604#M9324</link>
      <description>&lt;P&gt;So, what does your &lt;CODE&gt;/var/log/messages&lt;/CODE&gt; tell you? Looks like the recent change of &lt;CODE&gt;/etc/init.d/splunk&lt;/CODE&gt; did not work.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 20:27:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399604#M9324</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2019-07-17T20:27:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk service didn't start automatically after server  reboot</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399605#M9325</link>
      <description>&lt;P&gt;Thank you for the attention @mlevsh and the quote ; -) &lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 20:39:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-service-didn-t-start-automatically-after-server-reboot/m-p/399605#M9325</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-07-17T20:39:04Z</dc:date>
    </item>
  </channel>
</rss>

