Hi Mat,
Could you do a "pstack" of the child condor_master process?
Unfortunately, from your traceback, it like the master is simply waiting for the child to do something (either exec or error out) -- not too much info there.
Brian
> On Jul 21, 2020, at 12:05 PM, MÃtyÃs Selmeci via HTCondor-devel <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
> <MasterLog.txt><summary.txt>_______________________________________________
> HTCondor-devel mailing list
> HTCondor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-devel
|