Logging stopped in Pan OS GUI

Announcements

ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

Reply
Highlighted
L7 Applicator

Could you please check CLI command o/p of > show ntp

It should show the NTP server, it's connected.

Related DOC:

Error in NTP Sync Status Display

:

Let me know the result.

Thanks

Highlighted
Not applicable

Think I need to contact support for this. Thanks for the help

Highlighted
L7 Applicator

The mentioned error messages are related to NTP. Hence, could you please check the status of the NTP server on your FW.

Server error: An error occurred. See dagger.log for information


Thanks

Highlighted
Not applicable

Low and behold the log information is coming through now. I'm still getting the Server error: An error occurred. See dagger.log for information running debug log-receiver statistics from CLI though.

Highlighted
Not applicable

Interesting I am showing connected false for NTP

admin@PA-500(active)> show ntp

NTP state:

    NTP synched to LOCAL

    NTP server 0.north-america.pool.ntp.org connected: False

    NTP server 1.north-america.pool.ntp.org connected: False

Highlighted
L7 Applicator

Yes, NTP is the issue behind the error message "Server error: An error occurred. See dagger.log for information". Please check above mentioned KB DOC for the same.

Hope this helps.

Thanks

Highlighted
Not applicable

Hulk thanks so much for the help. The NTP server re-synched and now its showing true so it looks good now.

Highlighted
Not applicable

I think I spoke too soon. We are getting system log info etc. I tried checking just now and I notice the traffic log is not updating or displaying in the monitor. NTP seems to be fine.

I ran debug log-receiver statistics and the error "An error occured. See dagger.log for information." still appears.

I ran tail output after running debug log-receiver statistics and I see the following

KeyError: 'sw.logrcvr.runtime.opcmd'

admin@PA-500(active)> tail mp-log dagger.log

2014-07-08 20:44:23.567 -0700 OPCMD: handler "logrcvr_handler.debug_stats"

Traceback (most recent call last):

  File "/usr/share/dagger/logrcvr.py", line 60, in debug_stats

    resp_node = self.sdb.modify(name=op_node_name, object=op_node, timeout=60)

KeyError: 'sw.logrcvr.runtime.opcmd'

2014-07-08 20:45:11.212 -0700 OPCMD: handler "logrcvr_handler.debug_stats"

Traceback (most recent call last):

  File "/usr/share/dagger/logrcvr.py", line 60, in debug_stats

    resp_node = self.sdb.modify(name=op_node_name, object=op_node, timeout=60)

KeyError: 'sw.logrcvr.runtime.opcmd'

Is it possible I need to let the devices re-sync. Is there a command to manually force the devices to resync?

Highlighted
L7 Applicator

You can force the sync from the secondary cli using this command.

request high-availability sync-to-remote running-config

I doubt this is the issue but it can confirm what you want to confirm.

I would try to schedule a reboot of both nodes in turn after a sync confirmed.  If the issue is still present I would open a case.

Steve Puluka BSEET - IP Architect - DQE Communications (Metro Ethernet/ISP)
ACE PanOS 6; ACE PanOS 7; ASE 3.0; PSE 7.0 Foundations & Associate in Platform; Cyber Security; Data Center
Highlighted
Not applicable

Thank you Steven. (and Hulk). You have been very helpful. We intend to reboot the devices. As you mentioned the sync did not resolve the issue. Very odd indeed. All other logs system logs etc are working fine except traffic and some of the threat logs.

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!