Re: [HTCondor-users] condor_starter hanging with 100% CPU

[Samik Raychaudhuri <samikr@xxxxxxxxx>]

Hi Greg,

Yes - that fixes the starter problem. Before setting it to blank, the value was:

root@condor-01:/etc/condor# condor_config_val BASE_CGROUP
htcondor

I tried reading up a bit and followed a few trails for this variable, but things weren't too clear. Where did that previous value come from during installation?

Regards,
-Samik

On 11-Apr-17 1:55 AM, Greg Thain wrote:

On 04/10/2017 01:43 PM, Samik Raychaudhuri wrote:

Hello,

I am trying to run a single-node v8.6.1 of HTCondor on a debian VM. The condor system seems to start up, and the condor_status does show the node as available. However, once I submit a job, condor_starter goes to 100% CPU and stays there till I manually shut down the condor system. Upon further investigations, I noticed that the job is actually getting done, and the output is written in the temporary folder (see logs below), but for some reason condor_starter is not getting notification of this, or is getting busy in something else.

Here are some relevant logs - please let me know if someone wants to see something else. Where should I start checking?

If you set

BASE_CGROUP =

(that is, blank), does this fix the starter problem?

-greg

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/