Description

This article talks about an issue seen in vSRX3.0 devices where they keep crashing randomly with a PFE core-dump

Symptoms

  • The vSRX experiences sudden crash and srxpfe core-dump is generated
  • The 'messages' log file shows errors as below:
Mar 4 14:45:47.068 SRX ipfd[11703]: IPID-IPC-ERROR: usp_ipc_server_dispatch: failed to read messages from socket
Mar 4 14:45:47.068 SRX kernel: pid 21138 (srxpfe), jid 0, uid 0: exited on signal 10 (core dumped)
Mar 4 14:45:47.069 SRX ipfd[11703]: IPID-IPC-ERROR: usp_ipc_server_dispatch: failed to read messages from socket
Mar 4 14:45:47.069 SRX aamwd[11652]: IPID-IPC-ERROR: usp_ipc_server_dispatch: failed to read messages from socket
Mar 4 14:45:47.097 SRX useridd[11681]: IPID-IPC-ERROR: usp_ipc_server_dispatch: failed to read messages from socket
Mar 4 14:45:47.097 SRX kernel: peer_input_pending_internal: 6193: peer class: 0, type: 10, index: 0, vksid: 0, state: 1 reported a sb_state 32 = SBS_CANTRCVMORE
Mar 4 14:45:47.097 SRX kernel: peer_input_pending_internal: 6193: peer class: 0, type: 10, index: 0, vksid: 0, state: 1 reported a sb_state 32 = SBS_CANTRCVMORE
Mar 4 14:45:47.097 SRX kernel: peer_inputs: 6451: VKS0 closing connection peer class: 0, type: 10, index: 0, vksid: 0, state: 1, err 5
Mar 4 14:45:47.181 SRX chassisd[11459]: CHASSISD_FRU_OFFLINE_NOTICE: Taking FPC 0 offline: Error
Mar 4 14:45:47.187 SRX jsrpd[11486]: JSRPD_RG_STATE_CHANGE: Redundancy-group 1 transitioned from 'primary' to 'secondary-hold' state due to Flowd down
Mar 4 14:45:47.213 SRX jsrpd[11486]: JSRPD_SET_CS_MON_FAILURE: Cold-sync Monitor failed for redundancy-group 1
Mar 4 14:45:47.224 SRX jsrpd[11486]: JSRPD_HA_HEALTH_WEIGHT_LOW: Detected cluster8-Node0-RG1's health weight(0) low, send out SNMP trap

Solution

The issue has been identified with the pfe compilation process and is fixed in junos:22.4R3-S7, junos:23.2R2-S4, junos:23.4R2-S5, junos:24.2R2-S1, junos:24.3R1, junos:24.4R1.

Modification History

2025-04-02 : Article Created