<?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: [EventsViewer module] Cannot access search data;; job 1299545325.41 is a zombie and is no longer with us in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55452#M13536</link>
    <description>&lt;P&gt;This message is telling you the search is a zombie.&lt;/P&gt;

&lt;P&gt;The specific line of code that makes this determination in splunkd is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;bool isZombie = !(isDone || ScopedAliveProcessToken::isAlive(ddir / ALIVE_TOKEN));
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Ie, if it is not done, and not still alive, it is a zombie.  In other words, this is a search that crashed (or somehow otherwise stopped talking to the outside world), but still left some stuff lying around (which will be cleaned up later).  So the search artifacts exist in some state, and you can identify that the job once existed, but it probably isn't useful for information for making IT decisions etc about.&lt;/P&gt;

&lt;P&gt;The token is typically a named pipe, so you could have a case where the named pipe failed to be created or opened (permissions, fd exhaustion) but most likely there was a crash.&lt;/P&gt;

&lt;P&gt;Check the var/log/splunk directory for crashlogs, and if you're getting them, create a diag and work with support.  (both of these are talked about here)&lt;/P&gt;

&lt;P&gt;and eventually create a support case.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2011 12:20:04 GMT</pubDate>
    <dc:creator>jrodman</dc:creator>
    <dc:date>2011-03-08T12:20:04Z</dc:date>
    <item>
      <title>[EventsViewer module] Cannot access search data;; job 1299545325.41 is a zombie and is no longer with us</title>
      <link>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55451#M13535</link>
      <description>&lt;P&gt;I reinstalled splunk to a different volume and now I get this message when trying to search for any string.  How can I fix this ?    &lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 08:58:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55451#M13535</guid>
      <dc:creator>timstiles</dc:creator>
      <dc:date>2011-03-08T08:58:05Z</dc:date>
    </item>
    <item>
      <title>Re: [EventsViewer module] Cannot access search data;; job 1299545325.41 is a zombie and is no longer with us</title>
      <link>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55452#M13536</link>
      <description>&lt;P&gt;This message is telling you the search is a zombie.&lt;/P&gt;

&lt;P&gt;The specific line of code that makes this determination in splunkd is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;bool isZombie = !(isDone || ScopedAliveProcessToken::isAlive(ddir / ALIVE_TOKEN));
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Ie, if it is not done, and not still alive, it is a zombie.  In other words, this is a search that crashed (or somehow otherwise stopped talking to the outside world), but still left some stuff lying around (which will be cleaned up later).  So the search artifacts exist in some state, and you can identify that the job once existed, but it probably isn't useful for information for making IT decisions etc about.&lt;/P&gt;

&lt;P&gt;The token is typically a named pipe, so you could have a case where the named pipe failed to be created or opened (permissions, fd exhaustion) but most likely there was a crash.&lt;/P&gt;

&lt;P&gt;Check the var/log/splunk directory for crashlogs, and if you're getting them, create a diag and work with support.  (both of these are talked about here)&lt;/P&gt;

&lt;P&gt;and eventually create a support case.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 12:20:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55452#M13536</guid>
      <dc:creator>jrodman</dc:creator>
      <dc:date>2011-03-08T12:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: [EventsViewer module] Cannot access search data;; job 1299545325.41 is a zombie and is no longer with us</title>
      <link>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55453#M13537</link>
      <description>&lt;P&gt;Wont the search crash logs be over in /var/run/dispatch/1299545325.41/ ?   Or does it write crash logs out to the splunk's logs too?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 15:32:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55453#M13537</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-03-08T15:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: [EventsViewer module] Cannot access search data;; job 1299545325.41 is a zombie and is no longer with us</title>
      <link>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55454#M13538</link>
      <description>&lt;P&gt;are there any errors/warnings in $SPLUNK_HOME/var/run/splunk/dispatch/1299545325.41/search.log?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 16:50:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55454#M13538</guid>
      <dc:creator>Ledion_Bitincka</dc:creator>
      <dc:date>2011-03-08T16:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: [EventsViewer module] Cannot access search data;; job 1299545325.41 is a zombie and is no longer with us</title>
      <link>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55455#M13539</link>
      <description>&lt;P&gt;@nick - nope, all crashlogs go to $SPLUNK_HOME/var/logs/&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2011 16:52:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/EventsViewer-module-Cannot-access-search-data-job-1299545325-41/m-p/55455#M13539</guid>
      <dc:creator>Ledion_Bitincka</dc:creator>
      <dc:date>2011-03-08T16:52:37Z</dc:date>
    </item>
  </channel>
</rss>

