<?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: Starting splunk forwarder at boot in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Starting-splunk-forwarder-at-boot/m-p/57226#M11175</link>
    <description>&lt;P&gt;Hi Amanteja,&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;1&lt;/STRONG&gt; - To enable automatic start on boot: &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/bin/splunk enable boot-start&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;2&lt;/STRONG&gt; - Restarting a failed process is a OS specific (non-Splunk) configuration option. A quick Google search came up with this for RedHat, but may not be totally suitable for your environment:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/2.1/html/Cluster_Manager_Installation_and_Administration/s1-service-errorstate.html"&gt;https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/2.1/html/Cluster_Manager_Installation_and_Administration/s1-service-errorstate.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;3&lt;/STRONG&gt; - This is an OS setting. Splunk will pick up whatever IP address is assigned by the host.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;4&lt;/STRONG&gt; - The license page is only displayed upon the first start of the Universal Forwarder. If started with the following prompts, this will not be seen again:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/bin/splunk start --answer-yes --no-prompt --accept-license&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;5&lt;/STRONG&gt; - To pick up the desired configuration, I would have the host pick up the configuration from a central Deployment Server. Details of how to do this can be found here:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Aboutdeploymentserver"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Aboutdeploymentserver&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Happy Splunking &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 08 Sep 2013 01:48:25 GMT</pubDate>
    <dc:creator>rturk</dc:creator>
    <dc:date>2013-09-08T01:48:25Z</dc:date>
    <item>
      <title>Starting splunk forwarder at boot</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Starting-splunk-forwarder-at-boot/m-p/57225#M11174</link>
      <description>&lt;P&gt;Here is the situation&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;We have a splunk forwarder installed (from rpm), but never started in an Amazon AMI&lt;/LI&gt;
&lt;LI&gt;What we want is that when a new machine is spun up using that image the following things should happen

&lt;OL&gt;
&lt;LI&gt;Splunk forwarder should always start at boot up&lt;/LI&gt;
&lt;LI&gt;If the splunk deamon dies it should be restarted &lt;/LI&gt;
&lt;LI&gt;It should pick up the IP of the host correctly&lt;/LI&gt;
&lt;LI&gt;The license screen should be bypassed.&lt;/LI&gt;
&lt;LI&gt;The input and output conf files appropriate to send to the splunk host shoudl be put in place &lt;/LI&gt;
&lt;/OL&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;What are the suggestions to do that?&lt;BR /&gt;
How can we check whether the data is being sent successfully to the hosts?&lt;/P&gt;</description>
      <pubDate>Sat, 07 Sep 2013 15:11:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Starting-splunk-forwarder-at-boot/m-p/57225#M11174</guid>
      <dc:creator>amanteja</dc:creator>
      <dc:date>2013-09-07T15:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: Starting splunk forwarder at boot</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Starting-splunk-forwarder-at-boot/m-p/57226#M11175</link>
      <description>&lt;P&gt;Hi Amanteja,&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;1&lt;/STRONG&gt; - To enable automatic start on boot: &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/bin/splunk enable boot-start&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;2&lt;/STRONG&gt; - Restarting a failed process is a OS specific (non-Splunk) configuration option. A quick Google search came up with this for RedHat, but may not be totally suitable for your environment:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/2.1/html/Cluster_Manager_Installation_and_Administration/s1-service-errorstate.html"&gt;https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/2.1/html/Cluster_Manager_Installation_and_Administration/s1-service-errorstate.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;3&lt;/STRONG&gt; - This is an OS setting. Splunk will pick up whatever IP address is assigned by the host.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;4&lt;/STRONG&gt; - The license page is only displayed upon the first start of the Universal Forwarder. If started with the following prompts, this will not be seen again:&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/bin/splunk start --answer-yes --no-prompt --accept-license&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;5&lt;/STRONG&gt; - To pick up the desired configuration, I would have the host pick up the configuration from a central Deployment Server. Details of how to do this can be found here:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Aboutdeploymentserver"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Aboutdeploymentserver&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Happy Splunking &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 08 Sep 2013 01:48:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Starting-splunk-forwarder-at-boot/m-p/57226#M11175</guid>
      <dc:creator>rturk</dc:creator>
      <dc:date>2013-09-08T01:48:25Z</dc:date>
    </item>
  </channel>
</rss>

