This KB explains the cause, impact, and available mitigation.
SRX devices running Junos OS releases prior to 24.4R2 may log repeated jlaunchd messages indicating that commit-batch or ipsec-key-management processes are thrashing and not being restarted.
jlaunchd
commit-batch
ipsec-key-management
The following system log messages are observed repeatedly:
jlaunchd 25626 - - ipsec-key-management (PID 95708) exited with status=127jlaunchd 25626 - - ipsec-key-management is thrashing, not restartedjlaunchd 25626 - - commit-batch (PID 95711) exited with status=1jlaunchd 25626 - - commit-batch is thrashing, not restarted
In certain Junos OS releases prior to 24.4R2, jlaunchd may attempt to start legacy IKE/IPsec components even when the device is operating with iKED or does not actively use IPsec. Because the relevant process is not required in this mode, it may fail to start and repeatedly exit, causing jlaunchd to report a thrashing condition.
This behavior is a known cosmetic issue and has been fixed in Junos OS 24.4R2 and 25.1DCB .
** Monitor the system logs after performing the above steps
Resolution Guides and Troubleshooting Checklists:
JTAC Certified step-by-step troubleshooting flowcharts and articles
Technical Bulletins: SRX Series (log in to see more)