Threat and URL filtering logs are not displayed via WebGUI and CLI.
256
Created On 03/09/26 01:52 AM - Last Modified 09/02/26 22:17 PM
Symptom
- Threat and URL Filtering are not displayed from both WebGUI and CLI.
- Forwarding the logs to Syslog server is working fine.
logrcvr.logcontinuously records an error.Error: pan_logdb_writer_open_logfile(pan_logdb_writer.c:4551): File(/opt/pancfg/mgmt/logdb/threat/1/20260226/pan.log) positioned at a different value (write_pos:27037696) than where we are supposed to write (last_recoffset:27099276) Error: _taskq_worker_impl(pan_taskq.c:645): Error executing tasks process fn Error: pan_logdb_writer_open_logfile(pan_logdb_writer.c:4551): File(/opt/pancfg/mgmt/logdb/threat/1/20260226/pan.log) positioned at a different value (write_pos:27037696) than where we are supposed to write (last_recoffset:27099276) Error: _taskq_worker_impl(pan_taskq.c:645): Error executing tasks process fn Error: pan_logdb_writer_open_logfile(pan_logdb_writer.c:4551): File(/opt/pancfg/mgmt/logdb/threat/1/20260226/pan.log) positioned at a different value (write_pos:27037696) than where we are supposed to write (last_recoffset:27099276) Error: _taskq_worker_impl(pan_taskq.c:645): Error executing tasks process fnindexgen.logshows errors indicating that specific log files are corrupted.Error: main(pan_logdb_indexer.c:660): Logfile /opt/pancfg/mgmt/logdb/threat/1/20260226/pan.000000000000.log is corrupted, skip Error: main(pan_logdb_indexer.c:660): Logfile /opt/pancfg/mgmt/logdb/threat/1/20260226/pan.000000000000.log is corrupted, skip Error: main(pan_logdb_indexer.c:660): Logfile /opt/pancfg/mgmt/logdb/threat/1/20260226/pan.000000000000.log is corrupted, skip Error: main(pan_logdb_indexer.c:660): Logfile /opt/pancfg/mgmt/logdb/threat/1/20260226/pan.000000000000.log is corrupted, skip- The issue started after an unexpected power cycle or shutdown.
Environment
- Platform : Any PAN-OS firewall.
- PAN-OS : Any PAN-OS releases.
- Following an unexpected power cycle or shutdown.
Cause
- If the firewall is powered down unexpectedly while log files are actively being written to the disk, the log file header can become corrupted.
- This log database corruption prevents the management processes from properly writing or indexing the affected logs, resulting in the failure to display them from Web GUI or CLI.
Resolution
The affected logs must be cleared from the device.
- Log in to the CLI and execute the following command to clear all threat logs:
clear log threat
Additional Information
- A similar issue may occur with Traffic logs or other log types. In such cases, please clear the corresponding corrupted logs. For example, if the error is observed under /opt/pancfg/mgmt/logdb/traffic/, please clear traffic log.
clear log traffic