Re: [Condor-users] condor_config_val -set problem

[Armen Babikyan <armenb@xxxxxxxxxx>]

Hi Greg,

I got a little further, but I'm still having the problem.  After I set 
my HOSTALLOW_CONFIG to something other than *, I am getting this problem:

grid-8:~> condor_config_val -v MY_RESOURCE_1
TRUE
 Defined in '/software/condor/condor/local.grid-8/condor_config.local', 
line 107.

grid-8:~> condor_config_val -rset "MY_RESOURCE_1 = False"
Successfully set configuration "MY_RESOURCE_1 = False" on master 
grid-8.static.net <192.168.66.117:33807>.
grid-8:~> condor_config_val MY_RESOURCE_1
TRUE
grid-8:~> condor_config_val -set "MY_RESOURCE_1 = False"
Successfully set configuration "MY_RESOURCE_1 = False" on master 
grid-8.static.net <192.168.66.117:33807>.
grid-8:~> condor_config_val MY_RESOURCE_1
TRUE
grid-8:~> condor_config_val -set "MY_RESOURCE_1 = True"
Successfully set configuration "MY_RESOURCE_1 = True" on master 
grid-8.static.net <192.168.66.117:33807>.
grid-8:~> condor_config_val MY_RESOURCE_1
TRUE
grid-8:~> condor_config_val -rset "MY_RESOURCE_1 = True"
Successfully set configuration "MY_RESOURCE_1 = True" on master 
grid-8.static.net <192.168.66.117:33807>.
grid-8:~> condor_config_val MY_RESOURCE_1
TRUE
grid-8:~>

In other words, my configuration change look like its not happening in 
either RUNTIME or PERSISTENT modes, despite the success message.  Here's 
the snippet from the MasterLog after I turned on D_FULLDEBUG and D_COMMAND:

11/22 16:08:35 ProcAPI::buildFamily() Found daddypid on the system: 20267
11/22 16:08:37 ProcAPI::buildFamily() Found daddypid on the system: 20268
11/22 16:09:31 DaemonCore: Command received via TCP from host 
<192.168.66.117:33948>
11/22 16:09:31 DaemonCore: received command 60003 (DC_CONFIG_RUNTIME), 
calling handler (handle_config())
11/22 16:09:35 ProcAPI::buildFamily() Found daddypid on the system: 20267
11/22 16:09:37 ProcAPI::buildFamily() Found daddypid on the system: 20268
11/22 16:09:42 DaemonCore: Command received via TCP from host 
<192.168.66.117:33949>
11/22 16:09:42 DaemonCore: received command 60002 (DC_CONFIG_PERSIST), 
calling handler (handle_config())
11/22 16:09:53 Getting monitoring info for pid 20264
11/22 16:09:56 DaemonCore: Command received via TCP from host 
<192.168.66.117:33950>
11/22 16:09:56 DaemonCore: received command 60002 (DC_CONFIG_PERSIST), 
calling handler (handle_config())
11/22 16:10:02 DaemonCore: Command received via TCP from host 
<192.168.66.117:33951>
11/22 16:10:02 DaemonCore: received command 60003 (DC_CONFIG_RUNTIME), 
calling handler (handle_config())
11/22 16:10:35 ProcAPI::buildFamily() Found daddypid on the system: 20267
11/22 16:10:37 ProcAPI::buildFamily() Found daddypid on the system: 20268

Any ideas?  Thanks, and Happy Thanksgiving!

 - Armen

Greg Quinn wrote:
> Armen Babikyan wrote:
>   
> > I have:
> >
> > HOSTALLOW_CONFIG = *
> > ENABLE_RUNTIME_CONFIG = True
> > SETTABLE_ATTRS_CONFIG = *
> >     
>
> Armen,
>
> I've looked into this and there appears to be a problem with Condor's 
> handling of the "HOSTALLOW_CONFIG = *" line. This bug will be fixed in 
> future versions of Condor.
>
> In the meantime, you can work around this problem by using a slightly 
> more specific setting. For example, you could use the setting:
>
> HOSTALLOW_CONFIG = *.edu
>
> Regards,
>
> Greg Quinn
>   
--
Armen Babikyan
MIT Lincoln Laboratory
armenb@xxxxxxxxxx . 781-981-1796