<?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: R80.10 threat extraction high cpu usage in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3429#M14253</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No not yet, I thought I may find an answer here before raising with tac&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 20 May 2017 20:52:08 GMT</pubDate>
    <dc:creator>David_Robinson</dc:creator>
    <dc:date>2017-05-20T20:52:08Z</dc:date>
    <item>
      <title>R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3427#M14251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ive been testing R80.10 with all blades enabled and 2 or 3 days ago I noticed high cpu usage on a 'cat' process in top, to the point where I'm now unable to push policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i used pstree to identify the parent process being scrubd, which after a little research found it related to threat extraction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dad manage to successfully push policy if I killed the 'cat' processed with 'kill -9'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Removing the threat extraction blade restores cpu usage to&amp;nbsp; normality.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i took a migrate export and tried importing the backup to a vm to see if the issue arose, unfortunately it did.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;does anyone have any ideas on how I can fix this without rebuilding from scratch?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 May 2017 21:26:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3427#M14251</guid>
      <dc:creator>David_Robinson</dc:creator>
      <dc:date>2017-05-19T21:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3428#M14252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you opened an SR with TAC on this issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 May 2017 20:48:25 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3428#M14252</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2017-05-20T20:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3429#M14253</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No not yet, I thought I may find an answer here before raising with tac&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 May 2017 20:52:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3429#M14253</guid>
      <dc:creator>David_Robinson</dc:creator>
      <dc:date>2017-05-20T20:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3430#M14254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am experiencing the exact same issue. SmartConsole reports Threat Extraction blade is unresponsive, there is a "/bin/cat /dev/urandom" process eating up 100% of one CPU core.&lt;/P&gt;&lt;P&gt;Doing a kill -9 on the process spawns a second similar one. Killing the second one stops the spawning, but renders Threat Extraction useless.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you happen to find any solution to this yet?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Jul 2017 19:38:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3430#M14254</guid>
      <dc:creator>Bogdan_Tatomir2</dc:creator>
      <dc:date>2017-07-16T19:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3431#M14255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry for rushing in with the question. I found the culprit - &lt;SPAN style="background-color: #ffffff; color: #000000; font-size: 14px;"&gt;Threat Extraction Web API.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; color: #000000; font-size: 14px;"&gt;Also there is a solution available at&amp;nbsp;&lt;SPAN&gt;sk118353 .&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; color: #000000; font-size: 14px;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; color: #000000; font-size: 14px;"&gt;&lt;SPAN&gt;For me it fixed the issue. Hope this helps!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Jul 2017 20:32:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3431#M14255</guid>
      <dc:creator>Bogdan_Tatomir2</dc:creator>
      <dc:date>2017-07-16T20:32:12Z</dc:date>
    </item>
    <item>
      <title>Re: R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3432#M14256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's great to hear!&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.checkpoint.com/migrated-users/46159"&gt;https://community.checkpoint.com/people/dave.45cc086d-5044-468e-82c2-8ee173df935e&lt;/A&gt;‌ does this fix the issue for you?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Jul 2017 20:46:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3432#M14256</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2017-07-16T20:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: R80.10 threat extraction high cpu usage</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3433#M14257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since my setup was in a lab environment I decided to rebuild it clean and configure it as a distributed config rather than a stand-alone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have not had the issue so far.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Jul 2017 21:26:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-10-threat-extraction-high-cpu-usage/m-p/3433#M14257</guid>
      <dc:creator>David_Robinson</dc:creator>
      <dc:date>2017-07-16T21:26:42Z</dc:date>
    </item>
  </channel>
</rss>

