Log forwarding to syslog server stops after upgrade to 10.1.0
6251
Created On 09/17/21 19:44 PM - Last Modified 05/31/25 03:27 AM
Symptom
- Syslog-ng (less mp-log syslog-ng) crashes every 2 minutes after upgrade to 10.1.0 in messages.log
CMS klogd: [ 378.155097] syslog-ng[10969]: segfault at 49 ip 00007fa7984f2880 sp 00007fa79683a4e0 error 4 in libcrypto.so.1.0.1e[7fa798332000+271000]
CMS klogd: [ 503.334900] syslog-ng[12251]: segfault at 49 ip 00007fa7984f2880 sp 00007fa79683a4e0 error 4 in libcrypto.so.1.0.1e[7fa798332000+271000]
CMS klogd: [ 633.716127] syslog-ng[12610]: segfault at 49 ip 00007fa7984f2880 sp 00007fa79683a4e0 error 4 in libcrypto.so.1.0.1e[7fa798332000+271000]
CMS klogd: [ 829.332002] syslog-ng[15179]: segfault at 49 ip 00007fa7984f2880 sp 00007fa79683a4e0 error 4 in libcrypto.so.1.0.1e[7fa798332000+271000]
CMS klogd: [ 959.780610] syslog-ng[15509]: segfault at 49 ip 00007fa7984f2880 sp 00007fa79683a4e0 error 4 in libcrypto.so.1.0.1e[7fa798332000+271000]
- Logd.log (less mp-log logd.log)
Error: _pan_syslog(pan_syslog.c:806): Error calling syslog client
### [User admin logged in via Web from 10.47.223.240 using https], dgid 0, tplid 0
Error: syslog_clnt_send(syslog_clnt.c:348): SYSLOGCLNT(0x7f173b4afa38, 0x7f173b4afaf8, 28856, shut) Pkt dropped. syslog client not ready
Error: _pan_syslog(pan_syslog.c:806): Error calling syslog client
Error: syslog_clnt_send(syslog_clnt.c:348): SYSLOGCLNT(0x7f173b4afa38, 0x7f173b4afaf8, 28856, shut) Pkt dropped. syslog client not ready
Error: _pan_syslog(pan_syslog.c:806): Error calling syslog client
### [Connection to Update server: updates.paloaltonetworks.com completed successfully, initiated by 10.193.92.97], dgid 0, tplid 0
Error: syslog_clnt_send(syslog_clnt.c:348): SYSLOGCLNT(0x7f173b4afa38, 0x7f173b4afaf8, 28856, shut) Pkt dropped. syslog client not ready
Environment
- Palo Alto Firewall or Panorama
- PAN OS: 10.1
Cause
Issue with OCSP check which causes syslog-ng to crash.
Resolution
Set OCSP and CRL to skip with the below commands:
- Verify current setting for OSCP and CRL
> show system state | match cfg.syslogng-params
- Then run the below commands to skip
> set syslogng-ssl-conn-validation explicit CRL skip OCSP skip EKU skip
> set syslogng-ssl-conn-validation explicit OCSP skip CRL skip EKU skip
> configure
# commit force
- Confirm OSCP and CRL is now set to skip
> show system state | match cfg.syslogng-params
- Confirm syslog-ng is no longer crashing and confirm that log is being sent to and received by syslog server