Re: [HTCondor-users] Condor_config_val stopped working after updating to 8.4.7

[Iain Bradford Steers <iain.steers@xxxxxxx>]

Hi Kashif,

Just as a test to rule it out.

Could you run the following from the same node as the condor_config_val.

condor_ping -name <node-name> -type STARTD -table ALL

There should be a line starting with ADMINISTRATOR.

e.g. 

ADMINISTRATOR            GSI       3DES       MD5    ALLOW cm@xxxxxxxxxxxx

If the last column in that is unmapped or FAIL then you have a security/authorization mis-configuration.

You should also see in the StartLog of the startd a message to say that it failed and it may give a reason.

You might need to enable D_SECURITY in STARTD_DEBUG.

Cheers, Iain

________________________________________
From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of mohammad kashif [kashif.alig@xxxxxxxxx]
Sent: 09 August 2016 12:55
To: HTCondor-Users Mail List
Subject: [HTCondor-users] Condor_config_val stopped working after updating      to 8.4.7

Hi

I use condor_config_val to manage compute nodes remotely. I upgraded some of compute nodes to 8.4.7 and 8.4.8 and condor_config_val -set stopped working


condor_config_val -name <node-name> -startd -set "StartJobs = True"  Attempt to set configuration "StartJobs = True" on startd slot1@<node_name><mailto:slot1@xxxxxxxxxxxxxxxxxxxxxxx> A.B.C.D:62166?addrs=A.B.C.D-62166> failed.

I have following config settings which is working for 8.4.4

ENABLE_RUNTIME_CONFIG = TRUE

STARTD.SETTABLE_ATTRS_ADMINISTRATOR = StartJobs

ENABLE_PERSISTENT_CONFIG = TRUE

PERSISTENT_CONFIG_DIR = /etc/condor/persistent

Has any one else seen this issue?

Thanks

Kashif