<?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: MineMeld sudden_death...how does it work? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166641#M53367</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Thanks, that seems logical. That moves me on to my next troubleshooting step.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I created a separate thread for this[1], but are you aware of any way to debug a specific miner?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to see the command that is running when a particular miner is connecting so that I can verify that it isn't the miner that is contributing to what appears to be a much smaller number of indicators than expected the miner with sudden_death:true.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[1] -&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/General-Topics/MineMeld-debugging-miner/m-p/166625" target="_blank"&gt;https://live.paloaltonetworks.com/t5/General-Topics/MineMeld-debugging-miner/m-p/166625&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 14 Jul 2017 20:14:00 GMT</pubDate>
    <dc:creator>BRosenba</dc:creator>
    <dc:date>2017-07-14T20:14:00Z</dc:date>
    <item>
      <title>MineMeld sudden_death...how does it work?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166593#M53363</link>
      <description>&lt;P&gt;I need some help understanding the sudden_death behavior with a MineMeld miner/prototype.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the documentation[1], I understand that sudden_death is designed to immediately age out indicators when they disappear from&amp;nbsp;a feed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it comparing the current indicator list to the latest run of the feed,&amp;nbsp;recording indicators in the current list but&amp;nbsp;no longer in the feed and then setting to age out at the next age out? If so, what happens if the indicator appears in a subsequent run of the feed? Will it be added back to the list of indicators, or is excluded because it previously disappeared?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your help understanding.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[1] -&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/MineMeld-Articles/Configuring-nodes/ta-p/77185" target="_blank"&gt;https://live.paloaltonetworks.com/t5/MineMeld-Articles/Configuring-nodes/ta-p/77185&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2017 15:31:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166593#M53363</guid>
      <dc:creator>BRosenba</dc:creator>
      <dc:date>2017-07-14T15:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: MineMeld sudden_death...how does it work?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166639#M53366</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1561"&gt;@BRosenba&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;If you have it set to sudden_death:true and the run is missing an indicator currently in the miner then the EMIT_WITHDRAW is immeditely issued and the indicator is removed from the miner.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If an IP is listed on the next pull then it will be given a new age_out run number. The process continues until the indicator is no longer listed in the feed that the miner node is looking at.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Generally I would say that sudden_death and age_out are not usually used in conjunction with each other, or at the very least it's ineffective to use both depending on what you are doing. If you have age_out:3d for example the indicator is going to be removed after 3 days but if it's still in the listing it will just get added to the list of indicators again. If you have sudden_death:true then the indicator will be removed whenever the miner completes a run and the indicator is now missing. If you have both enabled essentially you only have a sudden_death configuration because the listing is just going to get readded until it gets removed from the list that you are polling.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2017 19:44:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166639#M53366</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-07-14T19:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: MineMeld sudden_death...how does it work?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166641#M53367</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Thanks, that seems logical. That moves me on to my next troubleshooting step.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I created a separate thread for this[1], but are you aware of any way to debug a specific miner?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like to see the command that is running when a particular miner is connecting so that I can verify that it isn't the miner that is contributing to what appears to be a much smaller number of indicators than expected the miner with sudden_death:true.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[1] -&amp;nbsp;&lt;A href="https://live.paloaltonetworks.com/t5/General-Topics/MineMeld-debugging-miner/m-p/166625" target="_blank"&gt;https://live.paloaltonetworks.com/t5/General-Topics/MineMeld-debugging-miner/m-p/166625&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2017 20:14:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166641#M53367</guid>
      <dc:creator>BRosenba</dc:creator>
      <dc:date>2017-07-14T20:14:00Z</dc:date>
    </item>
    <item>
      <title>Re: MineMeld sudden_death...how does it work?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166700#M53375</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1561"&gt;@BRosenba&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I don't know a way to actually debug a miner node in the way that you are asking, if you could post the actual configuration that you are using I could take a look at it and see if anything sticks out.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 16 Jul 2017 23:53:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/minemeld-sudden-death-how-does-it-work/m-p/166700#M53375</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-07-16T23:53:43Z</dc:date>
    </item>
  </channel>
</rss>

