Re: [Condor-users] Condor not vacating quad core machines

[Dan Bradley <dan@xxxxxxxxxxxx>]

Let's debug this off the list and then post back the results if they are 
of general interest.

Please send the following information to condor-admin@xxxxxxxxxxx:

On an execute node where you are having the problem, get the output from 
'condor_config_val -dump'

On an execute node that is at that moment having the problem, get the 
output from 'condor_status -long <hostname>' and also get a copy of the 
condor StartLog.

--Dan

Simon Hammond wrote:

> Hi All,
>
> Thanks for your help with everything so far, a new question for you.
>
> We are currently running RHEL 5 installations mixed with a few RHEL 4
> boxes. We recently upgraded to Condor 7.0.0 after having run 6.9.x
> series for a 14 months without problems.
>
> Since upgrading we have noticed that jobs are not vacated from the
> system when the interactive user logs in. The jobs just continue to
> run. Occasionally one of the slots (boxes are quad core, so there are
> four) will become Owner but the rest remain Claimed and Busy.
>
> I was wondering whether you had any advice on how to investigate this
> further, as I say, our previous installation worked pretty much
> flawlessly so it seems odd to have a new problem like this.
>
> Any advice you have would be much appreciated.
>
>
> Si Hammond
> High Performance Systems Group
> University of Warwick
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/
>