Configuring TLS Syslog @ PTX running 23.4R2-S2.3-EVO completely breaks both local and remote syslog, TLS session never starts and core dumps are generated

Once TLS Syslog config is committed (in particular the trigger looks to be the last section of the required TLS config in << system syslog host …>> after loading certificates and configuring the security config stanza – same behavior if leveraging groups or not), this happens.

Below alarm is reported.

2024-10-29 17:01:38 CET Major Application master-eventd fail on node Re0

Core dumps are generated (master-eventd core)

A check is missing for a local-certificate value when server auth is enabled. This certificate is only used for mutual auth, when server auth is enabled, this value is NULL, hence when tried to access, a core is generated.

This issue is fixed via PR1813100.

Way to recover:

deactivate TLS syslog config ( “system syslog host”)