<?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 Why is my scripted input excluded from the results? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-scripted-input-excluded-from-the-results/m-p/17468#M2264</link>
    <description>&lt;P&gt;I am running a scripted input that outputs the "apachectl -S" configuration.  I have set the proper permissions, tested it via "splunk cmd ", and found that it will index other information if added to the script.   I noticed that my splunkd.log file shows the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" VirtualHost configuration:
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" wildcard NameVirtualHosts and _default_ servers:
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" _default_:443          127.0.0.1 (/etc/httpd/conf.d/ssl.conf:81)
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" Syntax OK
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Is there a reason why this particular script output is not showing up?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jul 2010 00:00:33 GMT</pubDate>
    <dc:creator>Simeon</dc:creator>
    <dc:date>2010-07-16T00:00:33Z</dc:date>
    <item>
      <title>Why is my scripted input excluded from the results?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-scripted-input-excluded-from-the-results/m-p/17468#M2264</link>
      <description>&lt;P&gt;I am running a scripted input that outputs the "apachectl -S" configuration.  I have set the proper permissions, tested it via "splunk cmd ", and found that it will index other information if added to the script.   I noticed that my splunkd.log file shows the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" VirtualHost configuration:
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" wildcard NameVirtualHosts and _default_ servers:
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" _default_:443          127.0.0.1 (/etc/httpd/conf.d/ssl.conf:81)
07-14-2010 17:26:03.881 ERROR ExecProcessor - message from "/home/splunk/etc/apps/search/bin/apachectl.sh" Syntax OK
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Is there a reason why this particular script output is not showing up?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2010 00:00:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-scripted-input-excluded-from-the-results/m-p/17468#M2264</guid>
      <dc:creator>Simeon</dc:creator>
      <dc:date>2010-07-16T00:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my scripted input excluded from the results?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-scripted-input-excluded-from-the-results/m-p/17469#M2265</link>
      <description>&lt;P&gt;For the above scenario, the "apachectl -S" command is writing to standard error and not standard out.  When running the script manually, everything looks okay since it is sent directly to the terminal.  To fix this problem, you must edit your script to send the standard error data to the standard out.  To do this, add "2&amp;gt;&amp;amp;1" to the command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;apachectl -S 2&amp;gt;&amp;amp;1
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 16 Jul 2010 00:03:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-my-scripted-input-excluded-from-the-results/m-p/17469#M2265</guid>
      <dc:creator>Simeon</dc:creator>
      <dc:date>2010-07-16T00:03:16Z</dc:date>
    </item>
  </channel>
</rss>

