User Tools

Site Tools



Support System

nextnano GmbH



Option A: HTCondor

You can use HTCondor to run the nextnano software on your local computer infrastructure (“on-premise”). Essentially, the nextnanomat software submits the job either locally or on the “HTCondor” cluster.

This feature is only supported with our new license system.

Download recommended HTCondor installer from HTCondor. Click on Download and download Current Stable Release (e.g. HTCondor 8.6.12) from UW Madison. We recommend the Native Package for Windows.

  • Latest tested version: 8.6.13: condor-8.6.13-453497-Windows-x64.msi
  • Latest tested version: 8.6.12: condor-8.6.12-446077-Windows-x64.msi
  • Latest tested version: 8.6.11: condor-8.6.11-440910-Windows-x64.msi

File. (Click to download). When you download you have to enter your name, email address and institution.

  1. Start installer
  2. Click Next and accept License Agreement
  3. Then there are two options. There will be one special computer that manages all condor jobs (Central Manager), and normal computers. If there is no Central Manager yet, we have to create a New Pool.
    1. If you are on the Central Manager, choose Create a new HTCondor Pool and fill in the name of the Pool, e.g. nextnanoCondorPool. This is a unique name for your pool of machines.
    2. If you are not the Central Manager, choose Join an existing HTCondor Pool and fill in the hostname of the central manager, e.g. computername where nextnanoCondorPool has been created.
  4. Tic Submit jobs to HTCondorPool and choose Always run jobs and never suspend them. (Alternative: If you do not want other people to run jobs on your machine at all, select Do not run jobs on this machine or if you do not want other people to run jobs on your machine while you are working, select When keyboard has been idle for 15 minutes.. You can of course modify these settings later.)
  5. Fill in your domain name (Example: Your Windows domain, e.g. (without www).) All PCs of your network should get the same domain name, this does not necessarily be your Windows domain.
  6. Hostname of SMTP Server and email address of administrator (not needed currently, leave it blank)
  7. Path to Java Virtual Machine (not needed currently, leave it blank)
  8. Host with Read access: *
  9. Host with Write access: $(CONDOR_HOST), $(IP_ADDRESS), *, 192.168.178.*, (Replace * with your domain name and add your local IP subnet e.g. 192.168.178.*)

On Windows you can obtain your IP subnet using cmd.exe with the ipconfig command.

  1. Host with Administrator access * (or $(IP_ADDRESS))
  2. Enable VM Universe No
  3. Choose an installation directory and press next (e.g. C:\condor\)

Program files seem to be problematic, so we do not recommend to use that directory

  1. Press Install (You need Administrator rights.)
  2. Once installed, you have to restart the computer. Then your new pool or pool member should be up and running.
  3. To be able to submit jobs from nextnanomat to HTCondor, you have to store your credentials once. Open a command shell and type the following command: condor_store_cred add
    • Enter your password and you are ready to submit your first HTCondor job.
    • If this does not work, try to enter condor_store_cred add -debug for more output information on the error.
  4. In order to submit jobs from nextnanomat to HTCondor, you have to activate within nextnanomat: Tools → Options → Expert settings → Show nonworking and experimental features

Summary of settings (Example)

Hostname (for HTCondor pool):
Policy: "Always run jobs"
Accounting domain:
Read access: *
Write access: $(CONDOR_HOST), $(IP_ADDRESS), *
Administrator: $(IP_ADDRESS)
Config file

You can find your condor config settings in the file C:\condor\condor_config. Let's look at an example.

  • Your company is called Simpson.
  • Your Windows domain is called
  • Your condor pool shall have the name TheSimpsonsCondorPool.
  • The condor host that manages the condor jobs has the computer name
  • Your computer is called
  • The computers in your network have the IP range 192.168.188.*. (or 2001:db8:2042::* in IPv6)
RELEASE_DIR = C:\condor
LOCAL_CONFIG_FILE = $(LOCAL_DIR)\condor_config.local
#CONDOR_HOST: $(FULL_HOSTNAME)          # on computer called homer
CONDOR_HOST: homer                      # on computer called lisa
COLLECTOR_NAME = TheSimpsonsCondorPool  # only on computer called homer
#UID_DOMAIN =                           # empty if you do not have a domain
SOFT_UID_DOMAIN=TRUE             # entry is missing if you do not have a domain
FILESYSTEM_DOMAIN =  # entry is missing if you do not have a domain
ALLOW_WRITE = $(CONDOR_HOST), $(IP_ADDRESS), *, 192.168.188.*, 2001:db8:2042::*
DAEMON_LIST = MASTER SCHEDD STARTD                       # on computer called lisa

Useful HTCondor commands for the Command Prompt

  • condor_submit <filename>.sub Submit a job to the pool.
  • condor_q Shows current state of own jobs in the queue.
    • condor_q -nobatch -global -allusers Shows state of all jobs in the cluster. Of all users.
    • condor_q -goodput -global -allusers Shows state and occupied CPU of all jobs in the cluster.
    • condor_q -allusers -global -analyze Detailed information for every job in the cluster.
    • condor_q -global -allusers -hold Shows why jobs are in hold state.
  • condor_status Shows state of all available resources.
  • condor_rm Remove jobs from a queue:
    • condor_rm -all Removes all jobs from a queue.
    • condor_rm <cluster>.<id> Removes jobs on cluster <cluster> with id <id> (It seems <cluster>. can be omitted, and id is the JOB_IDS number.)
  • condor_release -all If any jobs are in state hold, use this command to restart them.
  • condor_restart Restart all condor daemons/services after changes in config file.
  • condor_version Returns the version number of HTCondor
  • condor_store_cred query Returns info about the credentials stored for HTCondor jobs


Q: I submitted a job to HTCondor, but the Batch line of nextnanomat is stuck with preparing. What is wrong?

A1: Did you store your credentials after the installation of HTCondor? If not, enter condor_store_cred add into the command prompt to add your password, see above (Recommended Installation Process).

A2: Did you change your password recently? If yes you have to reenter your credentials for HTCondor. Enter condor_store_cred add into the command prompt to add your password, see above (Recommended Installation Process). If this does not work, try to enter condor_store_cred add -debug for more output information on the error.

Q: I specified target machines in Tools - Options. Afterwards every submitted job to HTCondor is stuck with transmitting. What is wrong?

A: The value for UID_DOMAIN within the condor_config file needs to be the same for every computer of your cluster. (You can easily test it in a command prompt with condor_status -af uiddomain) If it's not the same value, no matching computer will be found and the job won't be transmitted successfully.

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

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

Option B: Amazon EC2 (aws)

(We are working on it.)

nnm/cloud_computing.txt · Last modified: 2019/05/19 15:39 by stefan.birner