glidecondor_addDN
The glidecondor_addDN script (found in the ./install directory of the glideinWMS tree) can help manage Condor mapfiles. The management of DNs and authorization to specific users can be confusing and this utility can help.
Usage:
glidecondor_addDN [-daemon] /OU=YOUR/OU=DN/CN=HERE Mapped_to_User
This script will use the condor_config in your path (from "condor_config_val BIN") so make sure your path and config is pointing to the correct condor if you have multiple services installed on the same machine.
This script will modify the certs/condor_mapfile of your condor_mapfile in order to correctly add the DN to Condor's authorization scheme.
If -daemon is specified, then, in addition, this will modify the condor_config.local to include this DN as a daemon.
glidecondor_createSecSched
The glidecondor_createSecSched script (found in the ./install directory of the glideinWMS tree) can help manage the HTCondor's secondary schedds. It can be used when HTCondor's configuration is stored in LOCAL_CONFIG_DIR.
Usage:
glidecondor_createSecSched [-commonlog] [-nocreatedirs] scheddlist
This script will re-create the 11_gwms_secondary_schedds.config file at each invocation. The node admin can thus easily change the number of secondary schedds as needed.
By default, each secondary schedd will have its own log file.
If a shared log is desired, use -commonlog.
Please note that the tool does not try to guess what the existing config, if any, is using.
By default, the tool will create any needed directories. If you are sure the directories are already in place, e.g. beacuse you are just reducing the number of secondary schedds, you can use -nocreatedirs to speed it up.
Example:
glidecondor_createSecSched schedd_glideins1,schedd_glideins2
glidecondor_createSecCol
The glidecondor_createSecCol script (found in the ./install directory of the glideinWMS tree) can help manage the HTCondor's secondary collectors. It can be used when HTCondor's configuration is stored in LOCAL_CONFIG_DIR.
Usage:
glidecondor_createSecCol [-useportasname] [-commonlog] portrange
This script will re-create the 11_gwms_secondary_collectors.config file file at each invocation. The node admin can thus easily change the number of secondary collectors as needed.
Since each Condor Daemon needs a unique name, each collector will be called COLLECTORxxx.
By default, the numbering starts with 0 for the first collector in the port range, and is incremented by one for each additional one.
If -useportasname is used, xxx is instread defined as the port number used by the collector.
Please note that the tool does not try to guess what the existing config, if any, is using.
By default, each secondary collector will have its own log file.
If a shared log is desired, use -commonlog.
Please note that the tool does not try to guess what the existing config, if any, is using.
Example:
glidecondor_createSecCol 9620-9639
Other monitoring tools
The tools analyze_entries,analyze_queues, and analyze_frontends exist in the factory/tools directory. They can be used to monitor recent status of the factory, entries, and connected frontends. See Factory monitoring for more details.