User Tools

Site Tools


nnm:cloud_computing

This is an old revision of the document!


nextnano.cloud

Problems with HTCondor

Error: communication error

If you receive the following error when you type in condor_status

C:\Users\"<your user name>">condor_status
Error: communication error
CEDAR:6001:Failed to connect to <123.456.789.123>

you can check whether the computer associated with this IP address is your HTCondor computer using the following command.

nslookup 123.456.789.123

It is also a good idea to type in

nslookup

This will return the name of the Default Server that resolves DNS names. If it is not the expected computer, you can open a Command Prompt as Administrator and type in ipconfig /flushdns to flush the DNS Resolver Cache.

C:\Users\"<your user name>">ipconfig /flushdns

If the DNS address cannot be resolved correctly it could be related to a VPN connection that has configured a different default server for Domain Name to IP address mapping. E.g. if your Windows Domain is called contoso.com (which is only visible within your own network and your own HTCondor pool) but your DNS is resolved to www.contoso.com (which might be outside your local HTCondor pool).

Error: ''condor_store_cred add'' failed with ''Operation failed. Make sure your ALLOW_WRITE setting include this host.''

Solution: Edit condor_config file and add host, i.e. local computer name (here: nn-delta).

    ALLOW_WRITE = $(CONDOR_HOST), $(IP_ADDRESS)
==> ALLOW_WRITE = $(CONDOR_HOST), $(IP_ADDRESS), nn-delta

Error? Check the Log files

If you encounter any strange errors, you can find some hints in the history or Log files generated by HTCondor. You can find them here:

C:\condor\spool

  • history

C:\condor\log

  • CollectorLog
  • MasterLog
  • MatchLog
  • NegotiatorLog
  • ProcLog
  • SchedLog
  • ShadowLog
  • SharedPortLog
  • StarterLog
  • StartLog

More details can be found here: Logging in HTCondor

nnm/cloud_computing.1704295058.txt.gz ยท Last modified: 2024/01/03 16:17 by stefan.birner