How to troubleshoot firewall or Panorama log queue issues
26781
Created On 09/10/24 16:54 PM - Last Modified 07/31/25 17:41 PM
Objective
To find the root cause and fix the log queue issue.
Environment
- NGFW
- Panorama
- External log server
- Log forwarding
Procedure
- Ensure that the log forwarding from firewall or Panorama to the external logging service is correctly configured. Refer to Configure Log Forwarding.
- Verify there are no connectivity issues between the firewall or Panorama and the external logging service.
- For syslog server, refer to How To Troubleshoot Connection Failures To Syslog Servers.
- For SNMP manager, refer to Forward Traps to an SNMP Manager.
- For email server, use the Test Connection button within the email server profile to verify that the firewall can successfully authenticate with the email server. Refer to How to Send a Test Email to Verify Email Profile Settings.
- If the external logging server is configured but is not used or unreachable from the firewall or Panorama, it is recommended to delete its configuration from the firewall or Panorama.
- For the firewall, check the output of the command
> debug log-receiver statistics- Check the external forwarding stats, look for the Drop Count, and see if that is incrementing:
External Forwarding stats: Type Enqueue Count Send Count Drop Count Queue Depth Send Rate(last 1min) syslog 9187198 9166138 3565042 16366 6701 snmp 0 0 0 0 0 email 0 0 0 0 0 raw 0 12747547 0 0 12451 http 0 0 0 0 0 autotag 0 0 0 0 0 quarantine 0 0 0 0 0 - For more details about which logs are dropping check the external forwarding stats per log type for the affected external log server:
External Forwarding stats per log type for syslog: Type Enqueue Count Send Count Drop Count traffic 9037714 9017508 3438854 config 4 4 4 system 21170 21155 3318 threat 128310 127471 122866 hipmatch 0 0 0 userid 0 0 0 iptag 0 0 0 extpcap 0 0 0 gtp 0 0 0 auth 0 0 0 sctp 0 0 0 globalprotect 0 0 0 decryption 0 0 0
- Check the external forwarding stats, look for the Drop Count, and see if that is incrementing:
- For Panorama or Log-collector, check the output of this command:
> debug log-collector log-collection-stats show log-forwarding-stats- Check the counters related to the affected log server, and look for the dropped count. See if that is incrementing. Example:
syslog enqueued count: 150612012 syslog sent count: 150349867 syslog dropped count: 189121069 syslog Queue depth: 262144
- Check the counters related to the affected log server, and look for the dropped count. See if that is incrementing. Example:
- If suspecting that the log-receiver daemon is not working as expected, restart the log-receiver to see if it resolves the issue:
> debug software process restart log-receiver
- Check the firewall or Panorama resources to verify whether some resource constraints are affecting the logging.
- For a Panorama-managed firewall, navigate to Panorama > Managed Devices > Health in the Panorama UI. This will allow you to check the firewall resources and its logging rate. Click on the affected firewall's name then on the Logging Tab for the detailed Logging Rate graph and the Resources Tab for the detailed Memory, CPU, Packet Buffers, and Packet Descriptors graphs.
- Check the logrcvr log for errors, particularly the message "Error: pan_logforward_enqueue_new".
- For Syslog Server:
-
Check if Panorama is hitting any SW issues, like: PAN-257615 which fixed an issue on Panorama where logs did not display or displayed intermittently on the web interface.
-
Check if the firewall or Panorama is hitting SW issue: PAN-234929 that fixed an issue where Fixed an issue where tabs in the ACC like Network Activity and Threat Activity may not display data correctly within certain time filters.
-
- SNMP Manager:
- Ensure the SNMP manager is correctly ingesting logs. If log ingestion is slow, it may create additional overhead for logrcvr (due to queuing and hint mechanisms), which can impact the log forwarding performance of the firewall or Panorama. Logs intended for forwarding to the SNMP manager are typically dropped if the connection to the SNMP server is broken or unstable, or if the SNMP server is unable to acknowledge the logs promptly.
- Email Server and HTTP server:
- Email server and HTTP log forwarding are designed for occasional notifications, not high-volume logs like Syslog. Ensure these services are not configured for heavy log traffic.
- For Syslog Server: