About traffic-stop-on-logdb-full feature

[Ayesha]

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.

Thank you.

[reaper]

you'll want to verify the stop traffic on log full setting as displayed below

what version of PAN-OS are you running?

[Raido_Rattameister]

@reaper other option on this screenshot "Enable Log on High DP load" is one of most badly worded option in Palo GUI.

Can you suggest internally to rename it. For example "Log High DP load".

Currently it seems that logging will be stopped when DP is high but actually System log is written.

[vsys_remo]

@reaper

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 😛

Any advice regarding this situation?

[reaper]

@vsys_remo whoa that doesn't sound good

I hope you got a techsupport file while it was in this state or were able to reach support

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)

This sounds like the whole system was affected including several auxiliary daemons

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

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