Every now and then, we see pipelines failing due to the "process apparently never started..."-error. See also the snippet below. We have listened to the proposed solution, namely making use of the LAUNCH_DIAGNOSTICS flag, but that does not give any other leads. It actually printed nothing additional compared to what was already printed: "process apparently never started...".

Next to that, we see this problem occuring multiple times a day. In the morning when load is generally relatively low, in the afternoon when there the load is skyhigh and everything in between. Therefore, this does not seem to be a usage-related issue.

I have seen that there have been some changes in the past with the durable-task plugin, such as the renaming of several parameters (FORCE_BINARY_WRAPPER -> USE_BINARY_WRAPPER). Maybe we could make use of that? Could this problem be related to the configuration of Jenkins and plugins we are having? Or is it a purely technical issue?

Thanks a lot!

 
[2021-10-19T11:12:11.179Z] process apparently never started in /home/jenkins/agent/workspace/<some-branch-name>@tmp/durable-fbd89733
https://jenkins2.verz.local/blue/organizations/jenkins/SDPJ%2Fsdp-jenkins2-image/detail/feature%2FSDP-4517_iac_health_plugin/3/pipeline/#step-55-log-2[2021-10-19T11:12:11.181Z] (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
https://jenkins2.verz.local/blue/organizations/jenkins/SDPJ%2Fsdp-jenkins2-image/detail/feature%2FSDP-4517_iac_health_plugin/3/pipeline/#step-55-log-3script returned exit code -2