<?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: What are the possible return values from the Splunk init script? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-possible-return-values-from-the-Splunk-init-script/m-p/11844#M730</link>
    <description>&lt;P&gt;I assume you mean the script which ends up as /etc/init.d/splunk or similar?&lt;BR /&gt;
This thing invokes the launcher (bin/splunk) and passes its return values along.&lt;/P&gt;

&lt;P&gt;The values don't appear to be that useful right now.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;0 obviously is success.&lt;/LI&gt;
&lt;LI&gt;4 seems to suggest permissions problems&lt;/LI&gt;
&lt;LI&gt;8 refers to environment problems&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;The new 4.1 command line work incorporates this table:&lt;/P&gt;

&lt;PRE&gt;
#define EXIT_NO_ARGS 8
#define EXIT_CMD_IGNORE 9
#define EXIT_FAILURE_USAGE 10
#define EXIT_FAILURE_DEPRECATED_CMD 11
#define EXIT_FAILURE_PARSE_CMD_LINE 12
#define EXIT_FAILURE_NO_HELP_EXISTS 14
#define EXIT_FAILURE_NO_DISPLAY_FUNC 15
#define EXIT_FAILURE_NO_CMD_EXISTS 16
#define EXIT_FAILURE_NOT_IMPLEMENTED 18
#define EXIT_FAILURE_NO_OBJ_EXISTS 19
#define EXIT_FAILURE_FGETS_READ 20
#define EXIT_FAILURE_REQD_ARG_MISSING 21
#define EXIT_FAILURE_REST_CALL 22
#define EXIT_FAILURE_DISPLAY_FUNC_ERR 23
#define EXIT_FAILURE_LOGIN 24
#define EXIT_FAILURE_URI_FORMAT 25
&lt;/PRE&gt;

&lt;P&gt;However we incorporate third party libraries. For example in some circumstances openssl (how the splunk executable communicates with splunkd)  will exit(2) on its own.  Compiling a complete list right now is not likely to be useful.&lt;/P&gt;

&lt;P&gt;Instead I would suggest:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Try launching splunk yourself, ideally with the same user that the script does, or run the script yourself (sh -x -v /etc/init.d/splunk start) to see what happens.&lt;/LI&gt;
&lt;LI&gt;Review $SPLUNK_HOME/var/log/splunk/splunkd_stderr.log and splunkd.log&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Wed, 21 Apr 2010 02:07:53 GMT</pubDate>
    <dc:creator>jrodman</dc:creator>
    <dc:date>2010-04-21T02:07:53Z</dc:date>
    <item>
      <title>What are the possible return values from the Splunk init script?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-possible-return-values-from-the-Splunk-init-script/m-p/11843#M729</link>
      <description>&lt;P&gt;I have a Splunk forwarder instance that appears to be returning a value of 2 during start up. &lt;/P&gt;

&lt;P&gt;I am curious as to what the possible return values are for the init script and what they mean.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Apr 2010 23:06:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-possible-return-values-from-the-Splunk-init-script/m-p/11843#M729</guid>
      <dc:creator>JHill</dc:creator>
      <dc:date>2010-04-20T23:06:58Z</dc:date>
    </item>
    <item>
      <title>Re: What are the possible return values from the Splunk init script?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-are-the-possible-return-values-from-the-Splunk-init-script/m-p/11844#M730</link>
      <description>&lt;P&gt;I assume you mean the script which ends up as /etc/init.d/splunk or similar?&lt;BR /&gt;
This thing invokes the launcher (bin/splunk) and passes its return values along.&lt;/P&gt;

&lt;P&gt;The values don't appear to be that useful right now.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;0 obviously is success.&lt;/LI&gt;
&lt;LI&gt;4 seems to suggest permissions problems&lt;/LI&gt;
&lt;LI&gt;8 refers to environment problems&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;The new 4.1 command line work incorporates this table:&lt;/P&gt;

&lt;PRE&gt;
#define EXIT_NO_ARGS 8
#define EXIT_CMD_IGNORE 9
#define EXIT_FAILURE_USAGE 10
#define EXIT_FAILURE_DEPRECATED_CMD 11
#define EXIT_FAILURE_PARSE_CMD_LINE 12
#define EXIT_FAILURE_NO_HELP_EXISTS 14
#define EXIT_FAILURE_NO_DISPLAY_FUNC 15
#define EXIT_FAILURE_NO_CMD_EXISTS 16
#define EXIT_FAILURE_NOT_IMPLEMENTED 18
#define EXIT_FAILURE_NO_OBJ_EXISTS 19
#define EXIT_FAILURE_FGETS_READ 20
#define EXIT_FAILURE_REQD_ARG_MISSING 21
#define EXIT_FAILURE_REST_CALL 22
#define EXIT_FAILURE_DISPLAY_FUNC_ERR 23
#define EXIT_FAILURE_LOGIN 24
#define EXIT_FAILURE_URI_FORMAT 25
&lt;/PRE&gt;

&lt;P&gt;However we incorporate third party libraries. For example in some circumstances openssl (how the splunk executable communicates with splunkd)  will exit(2) on its own.  Compiling a complete list right now is not likely to be useful.&lt;/P&gt;

&lt;P&gt;Instead I would suggest:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Try launching splunk yourself, ideally with the same user that the script does, or run the script yourself (sh -x -v /etc/init.d/splunk start) to see what happens.&lt;/LI&gt;
&lt;LI&gt;Review $SPLUNK_HOME/var/log/splunk/splunkd_stderr.log and splunkd.log&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Wed, 21 Apr 2010 02:07:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-are-the-possible-return-values-from-the-Splunk-init-script/m-p/11844#M730</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2010-04-21T02:07:53Z</dc:date>
    </item>
  </channel>
</rss>

