From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Chesal Sent: Wednesday, July 06, 2011 1:22 PM To: Condor-Users Mail List Subject: Re: [Condor-users] Newbie Question On Wednesday, July 6, 2011 at 2:17 PM, Smith, Herb wrote:
Hello Condor Users,
I have a, hopefully simple, newbie question. I believe I have set up successfully a Condor queue on a master machine and also added one additional machine to the pool. This is all on Windows XP. The problem that I seem to have is that when I do condor_status on the master node, it does not seem to see the other machine in the pool. It does see the dual core processor of its own. If I go to the other machine in the pool and do condor_status, it reports the cores available on the master node, but again does not report any resources for itself.
It appears that the second machine is connected to the pool, however, does not seem to have indicated that it is available to run any jobs. Is there a simple way to determine this and to fix it? Make sure your second machine is running a condor_startd process. This process is what makes a machine an execute node. To have Condor start a condor_startd process when the service starts, edit your condor_config.local file and make sure that: DAEMON_LIST = MASTER, PROCD, STARTD For the machine. You can check this setting from the command line with: condor_config_val DAEMON_LIST Ian,
The second machine shows MASTER, STARTD, and KBDD in response to the condor_config_val DAEMON_LIST command. The master node shows: MASTER SCHEDD COLLECTOR NEGOTIATOR STARTD and KBDD. I’m checking into the allow status that Mike mentioned. Herb |