<?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 Searches cancelled remotely or expired in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297864#M175540</link>
    <description>&lt;P&gt;I am currently running Splunk Enterprise 6.5.2, though this problem has persisted in one of our instances for a bit.&lt;BR /&gt;&lt;BR /&gt;
Everytime a search is attempted, we immediately get the familiar messages that it was cancelled remotely.  &lt;/P&gt;

&lt;P&gt;I've read the other entries in Answers and none of the suggestions seemed to work.  &lt;/P&gt;

&lt;P&gt;We are running a single node instance and the server clock seems to be in order.&lt;BR /&gt;&lt;BR /&gt;
I have raised the value of ttl in the limits.conf, but to no avail:&lt;BR /&gt;
[server]&lt;BR /&gt;
ttl=1800&lt;/P&gt;

&lt;P&gt;What else should I be looking for to get this issue resolved?&lt;/P&gt;

&lt;P&gt;Thanks, &lt;BR /&gt;
Tom&lt;/P&gt;</description>
    <pubDate>Tue, 14 Feb 2017 13:40:59 GMT</pubDate>
    <dc:creator>tlabue</dc:creator>
    <dc:date>2017-02-14T13:40:59Z</dc:date>
    <item>
      <title>Searches cancelled remotely or expired</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297864#M175540</link>
      <description>&lt;P&gt;I am currently running Splunk Enterprise 6.5.2, though this problem has persisted in one of our instances for a bit.&lt;BR /&gt;&lt;BR /&gt;
Everytime a search is attempted, we immediately get the familiar messages that it was cancelled remotely.  &lt;/P&gt;

&lt;P&gt;I've read the other entries in Answers and none of the suggestions seemed to work.  &lt;/P&gt;

&lt;P&gt;We are running a single node instance and the server clock seems to be in order.&lt;BR /&gt;&lt;BR /&gt;
I have raised the value of ttl in the limits.conf, but to no avail:&lt;BR /&gt;
[server]&lt;BR /&gt;
ttl=1800&lt;/P&gt;

&lt;P&gt;What else should I be looking for to get this issue resolved?&lt;/P&gt;

&lt;P&gt;Thanks, &lt;BR /&gt;
Tom&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2017 13:40:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297864#M175540</guid>
      <dc:creator>tlabue</dc:creator>
      <dc:date>2017-02-14T13:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: Searches cancelled remotely or expired</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297865#M175541</link>
      <description>&lt;P&gt;This error means that the search artifact (the file package containing the search results) requested by Splunk Web could not be found in $SPLUNK_HOME/var/run/splunk/dispatch for the search that was just dispatched.&lt;/P&gt;

&lt;P&gt;This problem commonly happens when the $SPLUNK_HOME/var/run/dispatch directory is hosted on a network device with a time setting behind the system clock of the operating system where splunkd is running.&lt;/P&gt;

&lt;P&gt;What happens then is that the search artifacts are created in the dispatch directory with a modification time behind the system time known to splunkd.&lt;/P&gt;

&lt;P&gt;Verify the time difference between your indexers/search head and check your system clocks and make sure they are all in sync. (Using NTP)&lt;/P&gt;

&lt;P&gt;This is a known issue for some of the Splunk versions, and below is the workaround to fix this issue.&lt;/P&gt;

&lt;P&gt;Under $SPLUNK_HOME/etc/system/local/limits.conf, add&lt;/P&gt;

&lt;P&gt;[search]&lt;BR /&gt;
min_settings_period = 60&lt;/P&gt;

&lt;P&gt;Note: This is in seconds. Defaults to 1 second.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 21:29:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297865#M175541</guid>
      <dc:creator>mbadhusha_splun</dc:creator>
      <dc:date>2020-09-29T21:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Searches cancelled remotely or expired</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297866#M175542</link>
      <description>&lt;P&gt;It worked. thanks !!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Oct 2018 07:14:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297866#M175542</guid>
      <dc:creator>vinkumar_splunk</dc:creator>
      <dc:date>2018-10-09T07:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: Searches cancelled remotely or expired</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297867#M175543</link>
      <description>&lt;P&gt;I believe it's [search] stanza that would make it to work&lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME/etc/system/local/limits.conf&lt;BR /&gt;
[search]&lt;BR /&gt;
min_settings_period = 60&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 21:46:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297867#M175543</guid>
      <dc:creator>mic</dc:creator>
      <dc:date>2020-09-29T21:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: Searches cancelled remotely or expired</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297868#M175544</link>
      <description>&lt;P&gt;Thanks, mate. It was a typo.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Oct 2018 11:12:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Searches-cancelled-remotely-or-expired/m-p/297868#M175544</guid>
      <dc:creator>mbadhusha_splun</dc:creator>
      <dc:date>2018-10-31T11:12:22Z</dc:date>
    </item>
  </channel>
</rss>

