Re: [HTCondor-users] cached result for advertise_startd

[Zach Miller <zmiller@xxxxxxxxxxx>]

Hello,

I think you want to add an '@' sign after the '*' in the first line of your ALLOW_DAEMON:  *@$(UID_DOMAIN)/*.mydomain

Also, you need to run condor_reconfig (or possibly condor_restart) to clear the cache and load the new config.  Then try again and see if things are working as expected.


Cheers,
-zach



ïOn 7/8/20, 2:19 PM, "HTCondor-users on behalf of nagaraj.tifr@xxxxxxxxx" <htcondor-users-bounces@xxxxxxxxxxx on behalf of nagaraj.tifr@xxxxxxxxx> wrote:

    Hi,

    I checked for ALLOW_DAEMON setting. Indeed, the newly added STARTD is not there in the ALLOW_DAEMON list. Beats me, because I did add it in the config file against ALLOW_DAEMON.. and I have restarted condor.

    Why is the setting in cache not getting updated to reflect the config file settings? Clippings from config file is here:


    ALLOW_DAEMON = *$(UID_DOMAIN)/*.mydomain, \
                   *@$(UID_DOMAIN)/$(IP_ADDRESS), \
                   condor_pool@xxxxxxxxxxxxxxxxxxxx, \
                   condor_pool@xxxxxxxxxxxxxxxxxxxx, \
                   *@sim01.mydomain

    and val-ump is here:

    ALLOW_DAEMON = *$(UID_DOMAIN)/*.mydomain, *@$(UID_DOMAIN)/$(IP_ADDRESS) condor_pool@xxxxxxxxxxxxxxxxxxxx, *@sim01.mydomain, condor_pool@xxxxxxxxxxxxx, condor_pool@xxxxxxxxxxxxxx, *@192.168.55.70 <http://192.168.55.70>, *@192.168.55.71 <http://192.168.55.71>..


    As can be seen, wn01 does appear in val dump, and wn02 is missing even though it is in the config file. Its not an issue of syntax, either, I think.


    Nagaraj





    On Wed, Jul 8, 2020 at 6:58 PM Zach Miller <zmiller@xxxxxxxxxxx> wrote:


    Warning: This message originated from outside TIFR domain. Please check the authenticity of the sender.

    Hello,

    Quick note: The config on a machine running a Collector is often different than the config on an execute node.  For a couple examples, the DAEMON_LIST will include the COLLECTER and NEGOTIATOR, and there may be additional ALLOW_*settings, which might be the issue here in this case.  If you have the condor_config from before the upgrade that you were using on your collector machine, you might want to just put that back into place.  We put quite a bit of effort to making sure (when it is possible and reasonable) that config files will still work from one version of HTCondor to the next for an upgrade.


    Now to your issue:

    On your collector machine, run this command:
            condor_config_val -dump ALLOW

    This will show the various authorization lists. Startds advertise to the collector, and the collector authorizes them if they are in the ALLOW_ADVERTISE_STARTD" setting.  Look at this on your collector and see if it looks like the StartD machine should be authorized.

    If ALLOW_ADVERTISE_STARTD is not set, then look at ALLOW_DAEMON instead.

    If you want to just copy and paste the output here I would be happy to take a look.

    Also, if I understand what happened correctly, is possible that next time HTCondor restarts, you will not be running a collector or negotiator due to the DAEMON_LIST issue I mentioned above.  You can check that setting also with "condor_config_val DAEMON_LIST".

    Please let me know what you find and if you have more questions.  Thank you.


    Cheers,
    -zach


    On 7/8/20, 5:31 AM, "HTCondor-users on behalf of Nagaraj Panyam" <htcondor-users-bounces@xxxxxxxxxxx on behalf of pn@xxxxxxxxxxx> wrote:

        Hi,

        What is the procedure to overcome issue as in the line below (from 
        CollectorLog on MC). I believe this is coming up because I had the node 
        execute wn02 to begin with, then reinstalled everything from scratch and 
        tried to join pool and I replicated entire /etc/condor  from a working 
        exec node.

        PERMISSION DENIED to condor_pool@xxxxxxxxxxxxxxxxxxxx from host 
        192.168.55.82 for command 0 (UPDATE_STARTD_AD), access level 
        ADVERTISE_STARTD: reason: cached result for ADVERTISE_STARTD; see first 
        case for the full reason

        Thanks for help!

        Nagaraj

        _______________________________________________
        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/