Re: [HTCondor-users] START = FALSE still fails (condor_config_val request refused)

[Aaron Moate <moate@xxxxxxxxxxx>]

Perhaps there is a higher priority config file setting
ENABLE_RUNTIME_CONFIG = TRUE?  What does this command output?

condor_config_val -v ENABLE_RUNTIME_CONFIG

A blurb from the HTCondor Manual:

ENABLE_RUNTIME_CONFIG
The condor_config_val tool has an option -rset for dynamically
setting run time configuration values, and which only affect the
in-memory configuration variables. Because of the potential
security implications of this feature, by default, HTCondor
daemons will not honor these requests. To use this
functionality, HTCondor administrators must specifically enable
it by setting ENABLE_RUNTIME_CONFIG to True, and specify what
configuration variables can be changed using the
SETTABLE_ATTRS... family of configuration options. Defaults to
False.

SETTABLE_ATTRS_<PERMISSION-LEVEL>
All macros that begin with SETTABLE_ATTRS or
<SUBSYS>.SETTABLE_ATTRS are settings used to restrict the
configuration values that can be changed using the
condor_config_val command. Section 3.6.9 on Setting up
IP/Host-Based Security in HTCondor for details on these macros
and how to configure them. In particular, section 3.6.9 on page
[*] contains details specific to these macros.

Possibly add the following to your config if it isn't there
already:

SETTABLE_ATTRS_CONFIG = START

I haven't tried it, just throwing it out there as a possibility.

-Moate

On Fri, Jul 31, 2015 at 04:08:26PM +0200, Iain Steers wrote:
> Hello,
> 
> Did you ever figure out the issue behind this issue.
> 
> I've just run into what appears to be the same problem and I'm a bit
> stumped.
> 
> Thanks,
> 
> Iain
> 
> On Fri, May 22, 2015 at 12:14:42PM -0500, Dimitri Maziuk wrote:
> > So with
> > 
> > ALLOW_CONFIG = *.bmrb.wisc.edu
> > ENABLE_RUNTIME_CONFIG = TRUE
> > 
> > I get
> > 
> > > set_persistent_config(): ENABLE_PERSISTENT_CONFIG is false. Not setting persistent config file param: Name = start, Value = START=FALSE
> > 
> > Did anyone actually think of usability before they made these all
> > security improvements?
> > 
> > And here's the kicker: setting ENABLE_PERSISTENT_CONFIG = TRUE doesn't
> > change the error.
> > 
> > -- 
> > Dimitri Maziuk
> > Programmer/sysadmin
> > BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
> > 
> > 
> > 
> 
> 
> 
> > _______________________________________________
> > HTCondor-users mailing list
> > To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> > 
> > The archives can be found at:
> > https://lists.cs.wisc.edu/archive/htcondor-users/
> 
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/