no that isnât intentional. Is there a configuration variable that could be causing this?
Other than that - why canât condor kill the job? Shouldnât it be possible to do so anyways?
On 6. Dec 2021, at 17:43, Greg Thain <gthain@xxxxxxxxxxx> wrote:
On 12/6/21 8:32 AM, Schock, Justus wrote:
When running jobs with the docker universe, I always get the following error message:
12/06/21 15:26:24 (pid:3819363) Create_Process succeeded, pid=3819365
12/06/21 15:26:24 (pid:3819363) Suspending all jobs.
12/06/21 15:26:24 (pid:3819363) DockerProc::Suspend() container 'HTCJob50126_0_slot1_1_PID3819363'
It looks like condor is trying to suspect the docker job immediately after starting it. Is this intentional in your pool -- suspend means that the job is still using the slot, but has effectively been sent SIGSTOP, so that it isn't using
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: