<?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 FWM process failure in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2809#M102245</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;we've had the same problem on R80.20, just solved it.&lt;/P&gt;&lt;P&gt;You must rename your managemet server, hostname must not start with CP_MGMT, either lower or upper case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to expert mode and execute "more $FWDIR/log/fwm.elg". You should see the following message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;write_using_CPMI_and_add_to_downgrade_hash: Update failed: Illegal name for 'CP_MGMT_R80' @ 'network_objects' - Object name can not start with 'cp_mgmt'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We changed hostname to something else (originally ours was CP_MGMT_R80 as you can see in the message above), rebooted the managemet server and it solved the problem. It took some time for server to start, even after "cpwd_admin list" showed all processes in E state (executing).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Feb 2019 09:40:10 GMT</pubDate>
    <dc:creator>Tomislav_Futivi</dc:creator>
    <dc:date>2019-02-22T09:40:10Z</dc:date>
    <item>
      <title>R80 FWM process failure</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2807#M102243</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Installed R80 MDS on VMware ESXi, 8 Gigs RAM and 4 cores/40 Gig HDD. Initial Wizard worked just fine as well as Gaia Portal, but when I try to connect via SmartConsole, I see following:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="SmartC_error.jpg" class="j-img-floatstart image-1 jive-image" height="213" src="https://community.checkpoint.com/legacyfs/online/checkpoint/54833_SmartC_error.jpg" style="width: 455px; height: 213.556px; float: left;" width="455" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I logged into Expert mode, I can see following output, seems like FWM process is not loaded or badly crashed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: justify;"&gt;&lt;IMG alt="cpwd.jpg" class="image-2 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/54835_cpwd.jpg" style="width: 620px; height: 221px;" /&gt;&lt;/P&gt;&lt;P&gt;When I am trying to launch FWM manually with DEBUGGING enabled it fails with some non-Google-able output, see attached screenshot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did anyone see anything like it? I am thinking about fresh installation as the only way out of this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Alexander&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Nov 2016 15:26:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2807#M102243</guid>
      <dc:creator>Alexander_Andre</dc:creator>
      <dc:date>2016-11-08T15:26:48Z</dc:date>
    </item>
    <item>
      <title>Re: R80 FWM process failure</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2808#M102244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Have you got anywhere with this? Our situation is that we added a new take to upgrade the managers and now the secondary is unresponsive as a Checkpoint device.... it is manageable but the fwm process is not running and will not start.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Nov 2016 08:19:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2808#M102244</guid>
      <dc:creator>Anthony_Kahwati</dc:creator>
      <dc:date>2016-11-14T08:19:05Z</dc:date>
    </item>
    <item>
      <title>Re: R80 FWM process failure</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2809#M102245</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;we've had the same problem on R80.20, just solved it.&lt;/P&gt;&lt;P&gt;You must rename your managemet server, hostname must not start with CP_MGMT, either lower or upper case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to expert mode and execute "more $FWDIR/log/fwm.elg". You should see the following message:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;write_using_CPMI_and_add_to_downgrade_hash: Update failed: Illegal name for 'CP_MGMT_R80' @ 'network_objects' - Object name can not start with 'cp_mgmt'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We changed hostname to something else (originally ours was CP_MGMT_R80 as you can see in the message above), rebooted the managemet server and it solved the problem. It took some time for server to start, even after "cpwd_admin list" showed all processes in E state (executing).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Feb 2019 09:40:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/R80-FWM-process-failure/m-p/2809#M102245</guid>
      <dc:creator>Tomislav_Futivi</dc:creator>
      <dc:date>2019-02-22T09:40:10Z</dc:date>
    </item>
  </channel>
</rss>

