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

Re: [HTCondor-users] Master Daemon - can't find address



Thank you – that is very helpful.

 

Our IT department recently installed HTCondor on a machine, but they did not follow my instructions on the various settings. So I have therefore had to go through and edit the condor_config file. I have changed it so that it is the same as the other machines that are working correctly, but it still doesn’t seem to be working properly. The machine (PC_92) does not appear when I do a condor_status. We have then run condor_startd on the computer, at which point it appeared on the status list. However, it is unable to submit analyses, and it does not respond to requests from other computers:

 

PS D:\condor\GSA_test> condor_submit test_VBS_GSA_submit_3.txt

Submitting job(s)

ERROR: Failed to connect to local queue manager

CEDAR:6001:Failed to connect to <10.201.25.217:54536>

 

-          This means that it has failed to connect to itself, since this is its own IP address (i.e. 10.201.25.217).

 

PS C:\Users\andrew.mole> condor_config_val -name PC_92 IP_ADDRESS

Can't find address for this master

Perhaps you need to query another pool.

 

 

1.      Any ideas why this is?

2.      Is there anything in the windows setup that would mess with the operation of the computer – ie that cannot be overridden by the settings in the config files?

 

This computer is running 8.0.2 on a win7 x64 PC, while the pool manager is still running 7.8.6 on a win7 x64 PC.

 

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of kschwarz@xxxxxxxxxxxxxx
Sent: Wednesday, October 09, 2013 7:15 PM
To: HTCondor-Users Mail List
Cc: HTCondor-users
Subject: Re: [HTCondor-users] Master Daemon

 

Hi Andrew,

Yes you are doing right!
Master daemon is the daemon that is responsible for keeping all the rest of the HTCondor daemons running on each machine in the pool, so each machine in a HTCondor pool must have this daemon running no matter what functions the machine performs.
The first line you wrote is for an executer and submitter node.
The Central Manager should have at least the MASTER, COLLECTOR and NEGOTIATOR to perform the CM functions: collect all ClassAds (COLLECTOR) and perform the matchmaking (NEGOTIATOR). The line you wrote adds the Scheduler and Executer functions to that machine.
Always you have a machine with STARTD running you should also have a KBDD daemon to monitor the keyboard/mouse activity. On Windows machines you will also see an KBDD running under the user login that monitors that user keyboard/mouse activity.

More informations about MASTER you could find at http://condor-portal/manuals/html/condor-V8_0_2-Manual/3_1Introduction.html#8881
http://condor-portal/manuals/html/condor-V8_0_2-Manual/condor_master.html#68658
http://condor-portal/manuals/html/condor-V8_0_2-Manual/3_3Configuration.html#12245

Cheers,
Klaus





From:        Andrew Mole <Andrew.Mole@xxxxxxxx>
To:        "htcondor-users@xxxxxxxxxxx" <htcondor-users@xxxxxxxxxxx>,
Date:        09/10/2013 05:43
Subject:        Re: [HTCondor-users] Master Daemon
Sent by:        "HTCondor-users" <htcondor-users-bounces@xxxxxxxxxxx>





Please excuse my ignorance, but which computers should be running the master daemon – i.e. if I have a node that can submit and execute (but is not the central manager) should it be running the master daemon? I don’t find the documentation particularly helpful on this, at least, not in the locations I have looked (which is almost certainly not the right ones!).
 
 
DAEMON_LIST=MASTER SCHEDD STARTD KBDD
 
For my central manager I have:
 
DAEMON_LIST=MASTER SCHEDD COLLECTOR NEGOTIATOR STARTD KBDD
 
Am I doing it right?
 
Andrew
 
 

____________________________________________________________
Electronic mail messages entering and leaving Arup  business
systems are scanned for acceptability of content and viruses
_______________________________________________
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/


This message is intended solely for the use of its addressee and may contain privileged or confidential information. All information contained herein shall be treated as confidential and shall not be disclosed to any third party without Embraer’s prior written approval. If you are not the addressee you should not distribute, copy or file this message. In this case, please notify the sender and destroy its contents immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações privilegiadas e confidenciais. Todas as informações aqui contidas devem ser tratadas como confidenciais e não devem ser divulgadas a terceiros sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor, notifique o remetente da mesma e destrua imediatamente a mensagem.