[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] condor_config_val no longer working since upgrade 7.2 --> 7.4

This caught us as well when we upgraded to 7.4.x - we worked around it
by changing



On Fri, Jul 2, 2010 at 11:04 AM, David McKechan
<david.mckechan@xxxxxxxxxxxxxx> wrote:
> Hi,
> I am administering a cluster that has a proportion of nodes dedicated
> to PBS. Originally, condor was configured to start running on these
> nodes when the PBS queue is empty, i.e., by having a
> PBSRUNNING=FALSE variable set in the condor_config file and using the
> PBS prologue/epilogue scripts to alter that variable. When a PBS node
> has a new PBS job it sends the condor_vacate command and then:
> ===============
> condor_config_val -rset -startd PBSRUNNING=TRUE
> ===============
> However, that command has not worked since upgrading from 7.2.x to 7.4.2:
> ===============
> [root@node87 mom_priv]# condor_config_val -rset -startd "PBSRUNNING=TRUE"
> Attempt to set configuration "PBSRUNNING=TRUE" on startd node87.local
> <> failed.
> ===============
> In the condor configuration the variable ENABLE_RUNTIME_CONFIG=TRUE is
> set. Can anyone help me find out why this command is no longer
> working? When condor is running on these nodes it provides another
> ~20% of the cluster.
> Many thanks,
> David McKechan
> _______________________________________________
> 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/

Preston M. Smith
Manager, HPC Grid Computing Systems
ITaP, Purdue University