[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Notifying Condor Master of shuting down compute nodes
- Date: Wed, 9 Mar 2005 14:42:08 +0100
- From: Mário Costa <atritoman@xxxxxxxxx>
- Subject: Re: [Condor-users] Notifying Condor Master of shuting down compute nodes
Sorry, I mean I'm shutting down the condor on the node in the condor
administrator acount, and I send the condor_off in the node with out
arguments, the problem is that the classds are still in the
negotiator, or in the collector, and the negotiator is using those
classads to match jobs.
I'm shure that the condor is not running in the node, so when I run
the condor_off, the collector is notified that the node is no longer
available ?? if not how can I do this ?
On Wed, 9 Mar 2005 7:18:00 -0600, Todd Tannenbaum <tannenba@xxxxxxxxxxx> wrote:
> Mário Costa <atritoman@xxxxxxxxx> wrote:
> >Is there any way of notifying condor master that a node is going down
> >? Wen I use condor_off -master in a node, because when I check the
> >status of the pool with condor_status, after suting down a node, the
> >node is still in the pool, and being used for maches with jobs, that
> >then fail to claim the resources ...
> >Can any one helpe me on this ?
> Perhaps it is just permissions.
> Shutting down a node requires administrator permissions. Thus, the hostname or ip address of the machine were you issue the condor_off must be listed in HOSTALLOW_ADMINISTRATOR.
> By default just the central manager is there, so _from your central manager_ try
> condor_off -master -fast node5.foo.edu
> to shut down condor on node5.
> >Condor-users mailing list
> Condor-users mailing list