<?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: Which log to check for API incident in Ansible</title>
    <link>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171830#M707</link>
    <description>&lt;P&gt;Thanks,useful for the next time.&lt;/P&gt;&lt;P&gt;It seemed related to using the same name for a rule and a section. Once I stopped doing that the error went away.&lt;/P&gt;</description>
    <pubDate>Fri, 17 Feb 2023 05:33:24 GMT</pubDate>
    <dc:creator>boneyard</dc:creator>
    <dc:date>2023-02-17T05:33:24Z</dc:date>
    <item>
      <title>Which log to check for API incident</title>
      <link>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171483#M705</link>
      <description>&lt;P&gt;Encountered an issue where I couldn't update a rule from a playbook with the error below. Turned out to be an issue with using the same name in the rule as in a section. Still im looking for which log file I should check to look further into that incident ID.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;failed: [mgmt-1.domain.ext] (item={'id': '3', 'type': 'rule', 'name': 'Stealth rule', 'source': 'Any', 'destination': 'grp_firewall', 'service': 'Any', 'action': 'Drop', 'log': 'Log', 'state': 'absent'}) =&amp;gt; {"ansible_loop_var": "item", "changed": false, "item": {"action": "Drop", "destination": "grp_firewall", "id": "3", "log": "Log", "name": "Stealth rule", "service": "Any", "source": "Any", "state": "present", "type": "rule"}, "msg": "Checkpoint device returned error 500 with message {'code': 'generic_internal_error', 'message': 'Internal error. For more info search for incident [888485d3-31d0-4d14-84ab-958345123523] in log file'}"}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 18:48:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171483#M705</guid>
      <dc:creator>boneyard</dc:creator>
      <dc:date>2023-02-14T18:48:51Z</dc:date>
    </item>
    <item>
      <title>Re: Which log to check for API incident</title>
      <link>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171509#M706</link>
      <description>&lt;P&gt;$FWDIR/log/api.elg.&lt;BR /&gt;Given this is a 500 error, the fix for this might just be a reboot.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Feb 2023 22:02:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171509#M706</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-02-14T22:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: Which log to check for API incident</title>
      <link>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171830#M707</link>
      <description>&lt;P&gt;Thanks,useful for the next time.&lt;/P&gt;&lt;P&gt;It seemed related to using the same name for a rule and a section. Once I stopped doing that the error went away.&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 05:33:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Ansible/Which-log-to-check-for-API-incident/m-p/171830#M707</guid>
      <dc:creator>boneyard</dc:creator>
      <dc:date>2023-02-17T05:33:24Z</dc:date>
    </item>
  </channel>
</rss>

