- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
06-10-2024 09:17 AM
Hello community,
I have encountered the SUBJECT error while t-shooting a SNMP connectivity issue on a PA-220. searching the internet I have not found a similar message anywhere therefor I thought I'd reach out to see if anyone can help with figuring out why this is showing only that line/error in a span of almost 3 months),
2024-03-22 07:49:31.667 -0700 Init-ing sysd
2024-03-22 07:49:31.689 -0700 sysd worker[0]: ffead501e0: starting up...
2024-03-22 07:49:33.714 -0700 Sysd Event: SUCCESS
2024-03-22 07:49:36.711 -0700 connected to sysd with handle:0xfff74a5420
2024-03-22 07:49:36.714 -0700 Setting Refresh timer to 30 seconds.
2024-03-22 07:49:36.714 -0700 Setting Refresh timer to 30 seconds.
2024-03-22 07:49:36.715 -0700 pan_snmp_get_sysd_timeout: Setting sysd timeout to 30 seconds.
2024-03-22 07:49:36 module:panChassis init'd
2024-03-22 07:49:36.717 -0700 Initializing module:panSys
2024-03-22 07:49:36 module:panSys init'd
2024-03-22 07:49:36.734 -0700 Initializing module:entityMIB
2024-03-22 07:49:36.773 -0700 Error: init_entity_fantrays(pan_snmpentity.c:1454): No fantrays retrieved from sysd during initialization (en
v.*.*.fantray.*), ignoring error:NO_MATCHES
2024-03-22 07:49:36.774 -0700 Error: init_entity_fans(pan_snmpentity.c:1122): No fans retrieved from sysd during initilization, ignoring er
ror(NO_MATCHES)
2024-03-22 07:49:36.789 -0700 entity_sysd_handle_chassis_summary: new_ins:0x1 new_cfgdone:0x1
2024-03-22 07:49:36 module:entityMIB init'd
2024-03-22 07:49:36.798 -0700 Initializing module:entitySensorMIB
2024-03-22 07:49:36 module:entitySensorMIB init'd
2024-03-22 07:49:36.804 -0700 Initializing module:hostResource
2024-03-22 07:49:36.814 -0700 module:hostResource init'd
2024-03-22 07:49:36.814 -0700 Initializing module:interfaces
2024-03-22 07:49:36 module:interfaces init'd
2024-03-22 07:49:36.835 -0700 Initializing module:panSessions
2024-03-22 07:49:36.910 -0700 module:panSessions init'd
2024-03-22 07:49:36.910 -0700 Initializing module:panMgmt
2024-03-22 07:49:36 module:panMgmt init'd
2024-03-22 07:49:36.912 -0700 Initializing module:panGlobalProtect
2024-03-22 07:49:36.912 -0700 module:panGlobalProtect init'd
2024-03-22 07:49:36.912 -0700 Initializing module:panVsysTable
2024-03-22 07:49:36 module:panVsysTable init'd
2024-03-22 07:49:36.913 -0700 Initializing module:panDeviceLogging
2024-03-22 07:49:36 module:panDeviceLogging init'd
2024-03-22 07:49:36.914 -0700 Initializing module:lagMIB
2024-03-22 07:49:36 module:lagMIB init'd
2024-03-22 07:49:36.919 -0700 Initializing module:lldpV2MIB
2024-03-22 07:49:36 module:lldpV2MIB init'd
2024-03-22 07:49:36.924 -0700 Initializing module:panHACluster
2024-03-22 07:49:36.929 -0700 hacluster: there is zero session stats entry
2024-03-22 07:49:36 module:panHACluster init'd
2024-03-22 07:49:36.997 -0700 env.s1.mp.power-supply.0 updated
2024-03-22 07:49:36.999 -0700 env.s1.mp.power-supply.1 updated
2024-03-22 07:49:37 NET-SNMP version 5.8
2024-03-22 09:21:18.011 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
[...]
2024-06-10 01:22:41.273 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 01:25:48.244 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 01:57:40.435 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 01:58:45.973 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 02:00:49.191 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 02:01:50.887 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 02:02:44.078 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 02:03:44.286 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 03:09:42.270 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
2024-06-10 03:11:49.309 -0700 Error: update_rlog_mgmtsrvr_fwd_stats(panDeviceLogging_access.c:710): panDeviceLoggingMIB update_rlog_mgmtsrvr_fwd_stats(): No sysd node found
I should mention that SYSD log is looking normal with device attach-detach messages TZ is SA local):
and I attached the output of the 'show system resources' screen-grab
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!