I am still having the same problem.
here is a part listing of the
CONDOR_HOST = thebeast
## Where have you installed the bin,
sbin and lib condor directories?
RELEASE_DIR = /home/condor/release
## Where is the local condor directory for each
LOCAL_DIR = /home/condor/hosts/$(HOSTNAME)
## Where is the machine-specific local config file for each
so in respect of $(HOSTNAME).local I have edited the following file for my
DAEMON_LIST = MASTER, COLLECTOR, NEGOTIATOR, STARTD,
Now the hostname environmental variable looks up fine.
thebeast:/home/condor # hostname
So I could assume i could run the condor daemons on the central manager
thebeast:/home/condor # condor_master
thebeast:/home/condor # ps -fe |
condor 5272 1 0
16:34 ? 00:00:00
condor 5273 5272 0 16:34
? 00:00:00 condor_schedd -f -n root@xxxxxxxxxxxxxxxxxxx
This is all im getting.. And running the collector and negotiator
manually doesnt make any difference.
They are running in memory but no node can connect. condor_status
on any node returns error that
the collector on thebeast can not be contacted even after I ran
Each node can ping thebeast fine and the host read and write are
----- Original Message -----
Sent: Tuesday, September 20, 2005 12:19
Subject: [Condor-users] Problem
installing condor on cluster.
I have a cluster with 24 nodes and a manager
names of each are
mgmnt.cluster.int has an alias thebeast.cluster.int (it was setup this
way by the company that installed the cluster).
so when i log into the manager i get the prompt [thebeast] but if i ping
thebeast it starts pinging mgmnt.cluster.int (192.168.1.1).
on the cluster /home/condor is shared between all nodes.
I ran condor_install and setup the various options, selecting that
/home/condor was shared and the relevant options with config files etc.
During condor_install i set the condor central manager to
The cluster manager machine is also my condor central
I then ran condor_init and then condor_master but the collector and a few
other processes associated with the central manager
is not running so I can only presume than when im executing condor_master
on this machine its only recognising itself as a normal
node and not the central manager which I want it to be.
Is there something simple I am missing or overseeing?
Many thanks in advance
University Of Paisley, Scotland