Dear HTCondor Experts,
It's Prasun from Kolkata, India.
[root@kolkata-condor-ce ~]# condor_ce_status -schedd -pool kolkata-condor-ce.tier2-kol.res.in:9619
Error: communication error
CEDAR:6001:Failed to connect to <188.8.131.52:9619
Error: Couldn't contact the condor_collector onkolkata-condor-ce.tier2-kol.res.in
Extra Info: the condor_collector is a process that runs on the central
manager of your Condor pool and collects the status of all the machines and
jobs in the Condor pool. The condor_collector might not be running, it might
be refusing to communicate with you, there might be a network problem, or
there may be some other problem. Check with your system administrator to fix
If you are the system administrator, check that the condor_collector is
running on kolkata-condor-ce.tier2-kol.res.in
the ALLOW/DENY configuration in your condor_config, and check the MasterLog
and CollectorLog files in your log directory for possible clues as to why the
condor_collector is not responding. Also see the Troubleshooting section of
Also, when I restart the condor-ce daemon, it takes too much time. However, condor daemon are restart within a fraction.
There are followingÂ condor daemon running on kolkata-condor-ce:-
[root@kolkata-condor-ce ~]# condor_config_val DAEMON_LIST
[root@kolkata-condor-ce ~]# condor_ce_config_val DAEMON_LIST
MASTER COLLECTOR SCHEDD JOB_ROUTER, CEVIEW, GANGLIAD, SCHEDD
Another case is that when we reconfig condor-ce, it say "Can't connect to local master".
We had also check MasterLog, SchedLog of condor-ce, but there are no any specific type of error.
So, please help how to resolve this issue.
Prasun Singh Roy
(Technician / F)