Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[HTCondor-users] Condor 8.9.* and USE_PID_NAMESPACES
- Date: Thu, 13 Aug 2020 13:37:45 +0000
- From: Bert DeKnuydt <Bert.DeKnuydt@xxxxxxxxxxxxxxxx>
- Subject: [HTCondor-users] Condor 8.9.* and USE_PID_NAMESPACES
Dear Condorese,
Has anyone been able running jobs with
USE_PID_NAMESPACES = True
under the current development series?
We've been using PID_NAMESPACES since many many years
without any trouble at all, but from 8.9.* it seems
broken for me.
In 8.9.4, it seemed like that condor_pid_ns_init didn't output
its ".condor_pid_ns_status" to the expected place.
In current 8.9.8, I get something along this:
08/11/20 14:17:22 (pid:72741) Running job as user xyzzy
08/11/20 14:17:22 (pid:72741) About to exec
/usr/libexec/condor/condor_pid_ns_init
/users/visics/xyzzy/condor/testscript.sh
08/11/20 14:17:22 (pid:72741) Warning: Create_Process: failed to read
child process failure code
08/11/20 14:17:22 (pid:72741)
Create_Process(/usr/libexec/condor/condor_pid_ns_init): child failed
with errno 1 (Operation not permitted) before exec()
08/11/20 14:17:22 (pid:72741)
Create_Process(/usr/libexec/condor/condor_pid_ns_init,/users/visics/xyzzy/condor/testscript.sh,
...) failed: (errno=1: 'Operation not permitted')
08/11/20 14:17:22 (pid:72741) Failed to start job, exiting
Higher debug levels available on demand.
The exec /usr/libexec/condor/condor_pid_ns_init is correct and can be
run manually
(with the environment variable trick).
With USE_PID_NAMESPACES = False, all works okay.
Greetings, Bert.