1GLOBUS-JOB-MANAGER(8) Grid Community Toolkit Manual GLOBUS-JOB-MANAGER(8)
2
6 globus-job-manager - Execute and monitor jobs
7
9 globus-job-manager -type LRM [-conf CONFIG_PATH] [-help]
10 [-globus-host-manufacturer MANUFACTURER] [-globus-host-cputype CPUTYPE]
11 [-globus-host-osname OSNAME] [-globus-host-osversion OSVERSION]
12 [-globus-gatekeeper-host HOST] [-globus-gatekeeper-port PORT]
13 [-globus-gatekeeper-subject SUBJECT] [-home GLOBUS_LOCATION]
14 [-target-globus-location TARGET_GLOBUS_LOCATION] [-condor-arch ARCH]
15 [-condor-os OS] [-history HISTORY_DIRECTORY] [-scratch-dir-base
16 SCRATCH_DIRECTORY] [-enable-syslog] [-stdio-log LOG_DIRECTORY]
17 [-log-pattern PATTERN] [-log-levels LEVELS] [-state-file-dir
18 STATE_DIRECTORY] [-globus-tcp-port-range PORT_RANGE]
19 [-globus-tcp-source-range SOURCE_RANGE] [-x509-cert-dir
20 TRUSTED_CERTIFICATE_DIRECTORY] [-cache-location GASS_CACHE_DIRECTORY]
21 [-k] [-extra-envvars VAR=VAL,...] [-seg-module SEG_MODULE]
22 [-audit-directory AUDIT_DIRECTORY] [-globus-toolkit-version
23 TOOLKIT_VERSION] [-disable-streaming] [-service-tag SERVICE_TAG]
24
26 The globus-job-manager program is a servivce which starts and controls
27 GRAM jobs which are executed by a local resource management system,
28 such as LSF or Condor. The globus-job-manager program is typically
29 started by the globus-gatekeeper program and not directly by a user. It
30 runs until all jobs it is managing have terminated or its delegated
31 credentials have expired.
32 Typically, users interact with the globus-job-manager program via
34 client applications such as globusrun, globus-job-submit, or tools such
35 as CoG jglobus or Condor-G.
36 The full set of command-line options to globus-job-manager consists of:
38 -help
40 Display a help message to standard error and exit
41 -type LRM
43 Execute jobs using the local resource manager named LRM.
44 -conf CONFIG_PATH
46 Read additional command-line arguments from the file CONFIG_PATH.
47 If present, this must be the first command-line argument to the
48 globus-job-manager program.
49 -globus-host-manufacturer MANUFACTURER
51 Indicate the manufacturer of the system which the jobs will execute
52 on. This parameter sets the value of the
53 $(GLOBUS_HOST_MANUFACTURER) RSL substitution to MANUFACTURER
54 -globus-host-cputype CPUTYPE
56 Indicate the CPU type of the system which the jobs will execute on.
57 This parameter sets the value of the $(GLOBUS_HOST_CPUTYPE) RSL
58 substitution to CPUTYPE
59 -globus-host-osname OSNAME
61 Indicate the operating system type of the system which the jobs
62 will execute on. This parameter sets the value of the
63 $(GLOBUS_HOST_OSNAME) RSL substitution to OSNAME
64 -globus-host-osversion OSVERSION
66 Indicate the operating system version of the system which the jobs
67 will execute on. This parameter sets the value of the
68 $(GLOBUS_HOST_OSVERSION) RSL substitution to OSVERSION
69 -globus-gatekeeper-host HOST
71 Indicate the host name of the machine which the job was submitted
72 to. This parameter sets the value of the $(GLOBUS_GATEKEEPER_HOST)
73 RSL substitution to HOST
74 -globus-gatekeeper-port PORT
76 Indicate the TCP port number of gatekeeper to which jobs are
77 submitted to. This parameter sets the value of the
78 $(GLOBUS_GATEKEEPER_PORT) RSL substitution to PORT
79 -globus-gatekeeper-subject SUBJECT
81 Indicate the X.509 identity of the gatekeeper to which jobs are
82 submitted to. This parameter sets the value of the
83 $(GLOBUS_GATEKEEPER_SUBJECT) RSL substitution to SUBJECT
84 -home GLOBUS_LOCATION
86 Indicate the path where the Grid Community Toolkit(r) is installed
87 on the service node. This is used by the job manager to locate its
88 support and configuration files.
89 -target-globus-location TARGET_GLOBUS_LOCATION
91 Indicate the path where the Grid Community Toolkit(r) is installed
92 on the execution host. If this is omitted, the value specified as a
93 parameter to -home is used. This parameter sets the value of the
94 $(GLOBUS_LOCATION) RSL substitution to TARGET_GLOBUS_LOCATION
95 -history HISTORY_DIRECTORY
97 Configure the job manager to write job history files to
98 HISTORY_DIRECTORY. These files are described in the FILES section
99 below.
100 -scratch-dir-base SCRATCH_DIRECTORY
102 Configure the job manager to use SCRATCH_DIRECTORY as the default
103 scratch directory root if a relative path is specified in the job
104 RSL’s scratch_dir attribute.
105 -enable-syslog
107 Configure the job manager to write log messages via syslog. Logging
108 is further controlled by the argument to the -log-levels parameter
109 described below.
110 -log-pattern PATTERN
112 Configure the job manager to write log messages to files named by
113 the string PATTERN. The PATTERN string may contain job-independent
114 RSL substitutions such as $(HOME), $(LOGNAME), etc, as well as the
115 special RSL substition $(DATE) which will be resolved at log time
116 to the date in YYYYMMDD form.
117 -stdio-log LOG_DIRECTORY
119 Configure the job manager to write log messages to files in the
120 LOG_DIRECTORY directory. This is a backward-compatible parameter,
121 equivalent to '-log-pattern '.
122 -log-levels LEVELS
124 Configure the job manager to write log messages of certain levels
125 to syslog and/or log files. The available log levels are FATAL,
126 ERROR, WARN, INFO, DEBUG, and TRACE. Multiple values can be
127 combined with the | character. The default value of logging when
128 enabled is FATAL|ERROR.
129 -state-file-dir STATE_DIRECTORY
131 Configure the job manager to write state files to STATE_DIRECTORY.
132 If not specified, the job manager uses the default of
133 $GLOBUS_LOCATION/tmp/gram_job_state/. This directory must be
134 writable by all users and be on a file system which supports POSIX
135 advisory file locks. . This directory must be writable by all users
136 and be on a file system which supports POSIX advisory file locks.
137 -globus-tcp-port-range PORT_RANGE
139 Configure the job manager to restrict its TCP/IP communication to
140 use ports in the range described by PORT_RANGE. This value is also
141 made available in the job environment via the GLOBUS_TCP_PORT_RANGE
142 environment variable.
143 -globus-tcp-source-range SOURCE_RANGE
145 Configure the job manager to restrict its TCP/IP communication to
146 use source ports in the range described by SOURCE_RANGE. This value
147 is also made available in the job environment via the
148 GLOBUS_TCP_SOURCE_RANGE environment variable.
149 -x509-cert-dir TRUSTED_CERTIFICATE_DIRECTORY
151 Configure the job manager to search TRUSTED_CERTIFICATE_DIRECTORY
152 for its list of trusted CA certificates and their signing policies.
153 This value is also made available in the job environment via the
154 X509_CERT_DIR environment variable.
155 -cache-location GASS_CACHE_DIRECTORY
157 Configure the job manager to use the path GASS_CACHE_DIRECTORY for
158 its temporary GASS-cache files. This value is also made available
159 in the job environment via the GLOBUS_GASS_CACHE_DEFAULT
160 environment variable.
161 -k
163 Configure the job manager to assume it is using Kerberos for
164 authentication instead of X.509 certificates. This disables some
165 certificate-specific processing in the job manager.
166 -extra-envvars VAR=VAL,...
168 Configure the job manager to define a set of environment variables
169 in the job environment beyond those defined in the base job
170 environment. The format of the parameter to this argument is a
171 comma-separated sequence of VAR=VAL pairs, where VAR is the
172 variable name and VAL is the variable’s value. If the value is not
173 specified, then the value of the variable in the job manager’s
174 environment is used. This option may be present multiple times on
175 the command-line or the job manager configuration file to append
176 multiple environment settings.
177 -seg-module SEG_MODULE
179 Configure the job manager to use the schedule event generator
180 module named by SEG_MODULE to detect job state changes events from
181 the local resource manager, in place of the less efficient polling
182 operations used in GT2. To use this, one instance of the
183 globus-job-manager-event-generator must be running to process
184 events for the LRM into a generic format that the job manager can
185 parse.
186 -audit-directory AUDIT_DIRECTORY
188 Configure the job manager to write audit records to the directory
189 named by AUDIT_DIRECTORY. This records can be loaded into a
190 database using the globus-gram-audit program.
191 -globus-toolkit-version TOOLKIT_VERSION
193 Configure the job manager to use TOOLKIT_VERSION as the version for
194 audit and usage stats records.
195 -service-tag SERVICE_TAG
197 Configure the job manager to use SERVICE_TAG as a unique identifier
198 to allow multiple GRAM instances to use the same job state
199 directories without interfering with each other’s jobs. If not set,
200 the value untagged will be used.
201 -disable-streaming
203 Configure the job manager to disable file streaming. This is
204 propagated to the LRM script interface but has no effect in GRAM5.
205 -condor-arch ARCH
207 Set the architecture specification for condor jobs to be ARCH in
208 job classified ads generated by the GRAM5 codnor LRM script. This
209 is required for the condor LRM but ignored for all others.
210 -condor-os OS
212 Set the operating system specification for condor jobs to be OS in
213 job classified ads generated by the GRAM5 codnor LRM script. This
214 is required for the condor LRM but ignored for all others.
215
217 If the following variables affect the execution of globus-job-manager
218 HOME
220 User’s home directory.
221 LOGNAME
223 User’s name.
224 JOBMANAGER_SYSLOG_ID
226 String to prepend to syslog audit messages.
227 JOBMANAGER_SYSLOG_FAC
229 Facility to log syslog audit messages as.
230 JOBMANAGER_SYSLOG_LVL
232 Priority level to use for syslog audit messages.
233 GATEKEEPER_JM_ID
235 Job manager ID to be used in syslog audit records.
236 GATEKEEPER_PEER
238 Peer information to be used in syslog audit records
239 GLOBUS_ID
241 Credential information to be used in syslog audit records
242 GLOBUS_JOB_MANAGER_SLEEP
244 Time (in seconds) to sleep when the job manager is started. [For
245 debugging purposes only]
246 GRID_SECURITY_HTTP_BODY_FD
248 File descriptor of an open file which contains the initial job
249 request and to which the initial job reply should be sent. This
250 file descriptor is inherited from the globus-gatekeeper.
251 X509_USER_PROXY
253 Path to the X.509 user proxy which was delegated by the client to
254 the globus-gatekeeper program to be used by the job manager.
255 GRID_SECURITY_CONTEXT_FD
257 File descriptor containing an exported security context that the
258 job manager should use to reply to the client which submitted the
259 job.
260 GLOBUS_TCP_PORT_RANGE
262 Default range of allowed TCP ports to listen on. The
263 -globus-tcp-port-range command-line option overrides this.
264 GLOBUS_TCP_SOURCE_RANGE
266 Default range of allowed TCP ports to bind to. The
267 -globus-tcp-source-range command-line option overrides this.
268
270 $HOME/.globus/job/HOSTNAME/LRM.TAG.red
271 Job manager delegated user credential.
272 $HOME/.globus/job/HOSTNAME/LRM.TAG.lock
274 Job manager state lock file.
275 $HOME/.globus/job/HOSTNAME/LRM.TAG.pid
277 Job manager pid file.
278 $HOME/.globus/job/HOSTNAME/LRM.TAG.sock
280 Job manager socket for inter-job manager communications.
281 $HOME/.globus/job/HOSTNAME/JOB_ID/
283 Job-specific state directory.
284 $HOME/.globus/job/HOSTNAME/JOB_ID/stdin
286 Standard input which has been staged from a remote URL.
287 $HOME/.globus/job/HOSTNAME/JOB_ID/stdout
289 Standard output which will be staged from a remote URL.
290 $HOME/.globus/job/HOSTNAME/JOB_ID/stderr
292 Standard error which will be staged from a remote URL.
293 $HOME/.globus/job/HOSTNAME/JOB_ID/x509_user_proxy
295 Job-specific delegated credential.
296 $GLOBUS_LOCATION/tmp/gram_job_state/job.HOSTNAME.JOB_ID
298 Job state file.
299 $GLOBUS_LOCATION/tmp/gram_job_state/job.HOSTNAME.JOB_ID.lock
301 Job state lock file. In most cases this will be a symlink to the
302 job manager lock file.
303 $GLOBUS_LOCATION/etc/globus-job-manager.conf
305 Default location of the global job manager configuration file.
306 $GLOBUS_LOCATION/etc/grid-services/jobmanager-LRM
308 Default location of the LRM-specific gatekeeper configuration file.
309 $GLOBUS_LOCATION/etc/globus/gram/job—manager.rvf
311 Default location of the site-specific job manager RSL validation
312 file.
313 $GLOBUS_LOCATION/etc/globus/gram/lrm.rvf
315 Default location of the site-specific job manager RSL validation
316 file for the named lrm.
317
319 globusrun(1), globus-gatekeeper(8), globus-personal-gatekeeper(1),
320 globus-gram-audit(8)
321
323 Copyright © 1999-2016 University of Chicago
324Grid Community Toolkit 6 12/06/2018 GLOBUS-JOB-MANAGER(8)