<?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: About traffic-stop-on-logdb-full feature in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/174355#M54795</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;other option on this screenshot "Enable Log on High DP load" is one of most badly worded option in Palo GUI.&lt;/P&gt;&lt;P&gt;Can you suggest internally to rename it. For example&amp;nbsp;&lt;SPAN&gt;"Log High DP load".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Currently it seems that logging will be stopped when DP is high but actually System log is written.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 01 Sep 2017 14:46:37 GMT</pubDate>
    <dc:creator>Raido_Rattameister</dc:creator>
    <dc:date>2017-09-01T14:46:37Z</dc:date>
    <item>
      <title>About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/173303#M54574</link>
      <description>&lt;P&gt;We're receiving multiple alerts "SYSTEM ALERT : critical : Traffic and logging are resumed since traffic-stop-on-logdb-full feature has been disabled ." for one fo the device, what needs to be done ? Please advise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Aug 2017 19:56:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/173303#M54574</guid>
      <dc:creator>Ayesha</dc:creator>
      <dc:date>2017-08-26T19:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/173351#M54577</link>
      <description>&lt;P&gt;you'll want to verify the stop traffic on log full setting as displayed below&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="log full.png" style="width: 800px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/10934i3D9D012F1BDFBDCA/image-size/large?v=v2&amp;amp;px=999" role="button" title="log full.png" alt="log full.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what version of PAN-OS are you running?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2017 07:18:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/173351#M54577</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-08-28T07:18:52Z</dc:date>
    </item>
    <item>
      <title>Re: About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/174355#M54795</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;other option on this screenshot "Enable Log on High DP load" is one of most badly worded option in Palo GUI.&lt;/P&gt;&lt;P&gt;Can you suggest internally to rename it. For example&amp;nbsp;&lt;SPAN&gt;"Log High DP load".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Currently it seems that logging will be stopped when DP is high but actually System log is written.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Sep 2017 14:46:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/174355#M54795</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2017-09-01T14:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/175987#M55085</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Today I also experienced this critical system log entries. The firewall is running PAN-OS 8.0.2 and the setting "Stop Traffic when LogDB Full" is NOT enabled. The log entries were flooding the system log with up to 400 logs / second. Unfortunately I was not able to resolve the issue and suddenly the firewall stopped processing connections completely. I then had to shut down ALL ports (dataplane interfaces were not enough to trigger a failover) because ssh, https and panorama context switch wasn't possible anymore ... was really fun today &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Any advice regarding this situation?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2017 19:19:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/175987#M55085</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2017-09-11T19:19:55Z</dc:date>
    </item>
    <item>
      <title>Re: About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/175991#M55086</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/16592"&gt;@Remo&lt;/a&gt;&amp;nbsp;whoa that doesn't sound good&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope you got a techsupport file while it was in this state or were able to reach support&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like something completely different was going on as the stop traffic option leaves your firewall in a rather 'relaxed' management state since its only blocking traffic from that point on (i never really understood this option but I guess there's a business need)&lt;/P&gt;
&lt;P&gt;This sounds like the whole system was affected including several auxiliary daemons&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There's not a lot of advice i can give for such a situation: the best thing is to contact TAC and resist the urge to reboot your firewall while they collect debug data&lt;/P&gt;
&lt;P&gt;Too many times I've had cases linger for a long time because the firewall was rebooted, prior to contacting support, and was in a healthy state with nomore indication of what happened&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2017 19:56:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/175991#M55086</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-09-11T19:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/175998#M55089</link>
      <description>&lt;P&gt;Ok, these problems probably aren't related in any way. It's just bad luck.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After a few hours I decided to enable ONLY the managment port again --&amp;gt; complete cluster was down again ... I am going to contact support now as I did not reboot till now ... the problem is that the generating a tech support from the console also fails ... so there is definately something wrong here &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EDIT: up to 1000 logdb-full system logs / second&lt;/P&gt;</description>
      <pubDate>Mon, 11 Sep 2017 21:21:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/175998#M55089</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2017-09-11T21:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: About traffic-stop-on-logdb-full feature</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/184048#M56478</link>
      <description>&lt;P&gt;I have a customer running PAN-OS 8.0.4&amp;nbsp;on a PA-5050 and their firewall is generating thousands of these very same System Critical Log Messages, "&lt;EM&gt;Traffic and logging are resumed since traffic-stop-on-logdb-full feature has been disabled&lt;/EM&gt;" daily (dozens by the second continually).&amp;nbsp; And the setting within your screenshot is NOT checked (Stop Traffic when LogDB Full).&amp;nbsp; However, I&amp;nbsp;believe this is a known issue and is being addressed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2017 07:43:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/about-traffic-stop-on-logdb-full-feature/m-p/184048#M56478</guid>
      <dc:creator>DGutierrez</dc:creator>
      <dc:date>2017-10-27T07:43:28Z</dc:date>
    </item>
  </channel>
</rss>

