Description

This article explains an issue where the device messages are flooded with "ipsec-key-management is thrashing, not restarted" logs.

Symptoms

You will see the process thrashing logs in messages as shown below:

<38>1 2026-02-17T05:14:21.275+11:00 SRX jlaunchd 25626 - - ipsec-key-management (PID 95708) started

<38>1 2026-02-17T05:14:21.275+11:00 SRX jlaunchd 25626 - - Registered PID 95708(ipsec-key-management): new process

<38>1 2026-02-17T05:14:22.965+11:00 SRX jlaunchd 25626 - - commit-batch (PID 95702) exited with status=1

<38>1 2026-02-17T05:14:22.965+11:00 SRX jlaunchd 25626 - - Registered PID 95711(commit-batch): exec_command

<38>1 2026-02-17T05:14:22.965+11:00 SRX jlaunchd 25626 - - commit-batch (PID 95711) started

<38>1 2026-02-17T05:14:22.965+11:00 SRX jlaunchd 25626 - - Registered PID 95711(commit-batch): new process

<38>1 2026-02-17T05:14:26.285+11:00 SRX jlaunchd 25626 - - ipsec-key-management (PID 95708) exited with status=127

<33>1 2026-02-17T05:14:26.286+11:00 SRX jlaunchd 25626 - - ipsec-key-management is thrashing, not restarted

<38>1 2026-02-17T05:14:28.019+11:00 SRX jlaunchd 25626 - - commit-batch (PID 95711) exited with status=1

<33>1 2026-02-17T05:14:28.019+11:00 SRX jlaunchd 25626 - - commit-batch is thrashing, not restarted

Solution

This is a cosmetic issue and has been fixed in junos:24.4R2 and newer versions.

Modification History

2026-06-11 : Article Created