Hi, We just upgraded Condor from 7.4.1 to 7.6.6 on one of our CE. When we do a condor_q, the following error pops out: # condor_q Error: Extra Info: You probably saw this error because the condor_schedd is not running on the machine you are trying to query. If the condor_schedd is not running, the Condor system will not be able to find an address and port toconnect to and satisfy this request. Please make sure the Condor daemons are
running and try again.Extra Info: If the condor_schedd is running on the machine you are trying to
query and you still see the error, the most likely cause is that you have setup a personal Condor, you have not defined SCHEDD_NAME in your condor_config file, and something is wrong with your SCHEDD_ADDRESS_FILE setting. You must define either or both of those settings in your config file, or you must use the -name option to condor_q. Please see the Condor manual for details on SCHEDD_NAME and SCHEDD_ADDRESS_FILE. We did see that both schedd and startd are running: condor 6518 6490 0 17:42 ? 00:00:00 condor_startd -f condor 6520 6490 0 17:42 ? 00:00:00 condor_schedd -f The local configuration file for this CE: # cat condor_config.local CONDOR_HOST=condormanager-13-3.local NETWORK_INTERFACE=10.3.255.253 START=False START_LOCAL_UNIVERSE = TotalLocalJobsRunning < 20 || GridMonitorJob =?= TRUE DAEMON_LIST = MASTER, STARTD, SCHEDD # Temporarily allow WRITE access from all worker nodes. This is supposed # to be done implicitly by Condor, but a bug in 7.0.4 prevents this if # the condor_shadow process runs > 8 hours. #ALLOW_WRITE = $(NETWORK_INTERFACE) ALLOW_WRITE = 10.3.0.0/16 PER_JOB_HISTORY_DIR=/osg/1.2.8/gratia/var/data MAX_SHADOW_LOG = 1000000000 SHADOW_DEBUG = D_SECURITYDo we need to set SCHEDD_NAME as suggested? Again, all configuration is based on 7.4.1.
Thanks advance for your help. Steven.....
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature