<?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: Unable to search using CLI in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81889#M20763</link>
    <description>&lt;P&gt;Splunk may be running but maybe not the installation-instance that you think.  Use your favorite method to determine the full path of the currently running &lt;CODE&gt;splunkd&lt;/CODE&gt; process and make sure you call &lt;CODE&gt;splunk&lt;/CODE&gt; in that path.&lt;/P&gt;</description>
    <pubDate>Wed, 27 May 2015 05:02:19 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-05-27T05:02:19Z</dc:date>
    <item>
      <title>Unable to search using CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81886#M20760</link>
      <description>&lt;P&gt;When running trying to run a search via the CLI (Redhat Linux) I get the following message:&lt;/P&gt;

&lt;P&gt;"Splunk is not running, and it must be for this operation. To start splunk, run "splunk start"."&lt;/P&gt;

&lt;P&gt;However the Splunk is up and running and fully functional via the Webgui.  Any ideas on how to get this working?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2010 08:05:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81886#M20760</guid>
      <dc:creator>mcwomble</dc:creator>
      <dc:date>2010-11-02T08:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to search using CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81887#M20761</link>
      <description>&lt;P&gt;Have there been any recent configuration changes to Splunk?  Which account started Splunk?  Which account owns the files in $SPLUNK_HOME/var/run/splunk?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2010 10:04:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81887#M20761</guid>
      <dc:creator>bwooden</dc:creator>
      <dc:date>2010-11-02T10:04:03Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to search using CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81888#M20762</link>
      <description>&lt;P&gt;Started by root&lt;BR /&gt;
Ownership of $SPLUNK_HOME/var/run/splunk is root&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2010 03:54:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81888#M20762</guid>
      <dc:creator>mcwomble</dc:creator>
      <dc:date>2010-11-05T03:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to search using CLI</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81889#M20763</link>
      <description>&lt;P&gt;Splunk may be running but maybe not the installation-instance that you think.  Use your favorite method to determine the full path of the currently running &lt;CODE&gt;splunkd&lt;/CODE&gt; process and make sure you call &lt;CODE&gt;splunk&lt;/CODE&gt; in that path.&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2015 05:02:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-search-using-CLI/m-p/81889#M20763</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-27T05:02:19Z</dc:date>
    </item>
  </channel>
</rss>

