No Traffic Logs in CLI and Gui

Reply
L4 Transporter

No Traffic Logs in CLI and Gui

 

 

No traffic logs in cli and gui

last log i see is midnight 2AM MST

 

debug log-receiver stats all logs incremented

 

tail mp-log logrcvr.log shows

 

2019-02-01 02:58:42.332 -0700 Error: _write_task_disk_flush_process(pan_logdb_writer.c:1501): Error executing the disk flush routine from write_task_disk_flush_process
2019-02-01 02:58:42.332 -0700 Error: _taskq_worker(pan_taskq.c:622): Error executing tasks process fn
2019-02-01 02:58:42.352 -0700 Error: _pan_syslog(pan_syslog.c:822): Error 111(Connection refused) writing syslog msg to sock:98 port=514 family=2 addrlen=16
2019-02-01 02:58:43.644 -0700 Error: _pan_syslog(pan_syslog.c:822): Error 111(Connection refused) writing syslog msg to sock:98 port=514 family=2 addrlen=16
2019-02-01 02:58:44.179 -0700 Error: _pan_syslog(pan_syslog.c:822): Error 111(Connection refused) writing syslog msg to sock:19 port=514 family=2 addrlen=16
2019-02-01 02:58:45.644 -0700 Error: _pan_syslog(pan_syslog.c:822): Error 111(Connection refused) writing syslog msg to sock:98 port=514 family=2 addrlen=16
2019-02-01 02:58:46.236 -0700 Error: _pan_syslog(pan_syslog.c:822): Error 111(Connection refused) writing syslog msg to sock:98 port=514 family=2 addrlen=16
2019-02-01 02:58:47.333 -0700 Error: _disk_flush_write_buffer(pan_logdb_writer.c:436): File(/opt/pancfg/mgmt/logdb/traffic/1/20190201/pan.log) positioned at a different value (cur_pos:4226593) than where we are supposed to write (write_
pos:4224796)
2019-02-01 02:58:47.333 -0700 Error: _write_task_disk_flush_process(pan_logdb_writer.c:1501): Error executing the disk flush routine from write_task_disk_flush_process

 

debug log-receiver statistics

 

 

debug log-receiver statistics
[?1h=
Logging statistics
------------------------------ -----------
Log incoming rate: 8/sec
Log written rate: 8/sec
Corrupted packets: 0
Corrupted URL packets: 0
Corrupted HTTP HDR packets: 0
Corrupted EMAIL HDR packets: 0
Logs discarded (queue full): 0
Traffic logs written: 27164399
GTP logs written: 0
Tunnel logs written: 0
Auth logs written: 0
Userid logs written: 0
URL logs written: 0
Wildfire logs written: 85
Anti-virus logs written: 0
Widfire Anti-virus logs written: 0
Spyware logs written: 5
Spyware-DNS logs written: 0
Attack logs written: 0
Vulnerability logs written: 16039
Fileext logs written: 0
Fileext logs URL not written: 0
Fileext logs URL not written (timedout): 0
URL cache age out count: 0
URL cache full count: 0
URL cache key exist count: 0
URL cache wrt incomplete http hdrs count: 0
URL cache rcv http hdr before url count: 0
URL cache full drop count(url log not received): 0
URL cache age out drop count(url log not received): 0
Email hdr cache count: 0
Email hdr cache hit count: 0
Traffic alarms dropped due to sysd write failures: 0
Traffic alarms dropped due to global rate limiting: 0
Traffic alarms dropped due to each source rate limiting: 0
Traffic alarms generated count: 0
Netflow incoming count: 0
Log Forward count: 0
Log Forward discarded (queue full) count: 0
Log Forward discarded (send error) count: 0
Total logs not written due to disk unavailability: 0
Logs not written since disk became unavailable: 0

Summary Statistics:
Num current drop entries in trsum:0
Num cumulative drop entries in trsum:0
Num current drop entries in thsum:0
Num cumulative drop entries in thsum:0
Num current drop entries in gtpsum:0
Num cumulative drop entries in gtpsum:0

External Forwarding stats:
Type Enqueue Count Send Count Drop Count Queue Depth Send Rate(last 1min)
syslog 56078508 56078508 0 0 849
snmp 0 0 0 0 0
email 0 0 0 0 0
raw 27179768 27179768 0 0 424
http 0 0 0 0 0
autotag 0 0 0 0 0

L7 Applicator

Re: No Traffic Logs in CLI and Gui

@MP18,

I would honestly give this thing a good old reboot with the number of different errors you are seeing. 

L4 Transporter

Re: No Traffic Logs in CLI and Gui

Seems giving a reboot fixed the issue.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!