After a quick skim of the log, I think it is hung trying to read from the pipe between the master and the procd which is used to try to propagate errors during exec(). Can you run the procd by hand? (And at least get the usage info?)
Cheers,
-zach
ïOn 7/21/20, 12:06 PM, "HTCondor-devel on behalf of MÃtyÃs Selmeci via HTCondor-devel" <htcondor-devel-bounces@xxxxxxxxxxx on behalf of htcondor-devel@xxxxxxxxxxx> wrote:
Hey folks,
I've got a problem running 8.9.8 on my Fedora 32 laptop (I'm using an
RPM Tim gave me from an NMI build): when I start condor, the master
forks and the child master gets into an infinite loop, eating an entire
CPU and not responding to SIGTERM. The last line in the MasterLog is:
07/21/20 11:46:56 (fd:1) (pid:233863) (D_DAEMONCORE) About to exec "/usr/sbin/condor_procd"
SELinux is off. I attached my MasterLog with D_ALL:2 and
condor_config_val -summary (that feature's great). The traceback
at the end of MasterLog is me killing sending SIGABRT to both
condor_master processes.
Any ideas?
Thanks,
-Mat
|