[Condor-users] A problem about local queue manager

[Zheng Chen <zc05r@xxxxxxxxxxxxxxx>]

Hi All,
    My condor can start up when my system is boosting. However, I have the
following problems.

(1) When submitting jobs,
[zchen@zc05rvm experiments]$ condor_submit jobs.submit
Submitting job(s)
ERROR: Failed to connect to local queue manager
CEDAR:6001:Failed to connect to <152.78.64.187:32816>

(2) When using condor_q, it shows that
Failed to fetch ads from: <152.78.64.187:32987> : zc05rvm.ecs.soton.ac.uk
CEDAR:6001:Failed to connect to <152.78.64.187:32987>

(3) Then I look at all the condor related processes:
[zchen@zc05rvm ~]$ ps -aux|egrep condor
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.5/FAQ
daemon    2096  0.2  0.5   6856  3084 ?        Ss   19:21   0:01
/home/zchen/software/vdt/condor/sbin/condor_master
daemon    2102  0.0  0.5   6960  2924 ?        Ss   19:21   0:00
condor_collector -f

>From (1),(2) and (3), It seems that the queue manager at 152.78.64.187:32987
does not start and no process condor_schedd exists.

I check the local configuration file, which has specified the following

##  condor_master
##  Daemons you want the master to keep running for you:

DAEMON_LIST = SCHEDD, STARTD, COLLECTOR, MASTER, NEGOTIATOR

So it is quite weired. All the five processes should be started when my system
is boosting. How can I fix this problem, e.g.,manully start the local queue
manager?

Many thanks,

Zheng