1GLOBUS-JOB-MANAGER(8) GRAM5 Commands 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]
11 [-globus-host-cputype CPUTYPE]
12 [-globus-host-osname OSNAME]
13 [-globus-host-osversion OSVERSION]
14 [-globus-gatekeeper-host HOST]
15 [-globus-gatekeeper-port PORT]
16 [-globus-gatekeeper-subject SUBJECT]
17 [-home GLOBUS_LOCATION]
18 [-target-globus-location TARGET_GLOBUS_LOCATION]
19 [-condor-arch ARCH] [-condor-os OS]
20 [-history HISTORY_DIRECTORY]
21 [-scratch-dir-base SCRATCH_DIRECTORY]
22 [-enable-syslog] [-stdio-log LOG_DIRECTORY]
23 [-log-pattern PATTERN] [-log-levels LEVELS]
24 [-state-file-dir STATE_DIRECTORY]
25 [-globus-tcp-port-range PORT_RANGE]
26 [-x509-cert-dir TRUSTED_CERTIFICATE_DIRECTORY]
27 [-cache-location GASS_CACHE_DIRECTORY] [-k]
28 [-extra-envvars VAR=VAL,...]
29 [-seg-module SEG_MODULE]
30 [-audit-directory AUDIT_DIRECTORY]
31 [-globus-toolkit-version TOOLKIT_VERSION]
32 [-disable-streaming] [-disable-usagestats]
33 [-usagestats-targets TARGET]
34 [-service-tag SERVICE_TAG]
35
37 The globus-job-manager program is a servivce which starts and controls
38 GRAM jobs which are executed by a local resource management system,
39 such as LSF or Condor. The globus-job-manager program is typically
40 started by the globus-gatekeeper program and not directly by a user. It
41 runs until all jobs it is managing have terminated or its delegated
42 credentials have expired.
43 Typically, users interact with the globus-job-manager program via
45 client applications such as globusrun, globus-job-submit, or tools such
46 as CoG jglobus or Condor-G.
47 The full set of command-line options to globus-job-manager consists of:
49 -help
51 Display a help message to standard error and exit
52 -type LRM
54 Execute jobs using the local resource manager named LRM.
55 -conf CONFIG_PATH
57 Read additional command-line arguments from the file CONFIG_PATH.
58 If present, this must be the first command-line argument to the
59 globus-job-manager program.
60 -globus-host-manufacturer MANUFACTURER
62 Indicate the manufacturer of the system which the jobs will execute
63 on. This parameter sets the value of the
64 $(GLOBUS_HOST_MANUFACTURER) RSL substitution to MANUFACTURER
65 -globus-host-cputype CPUTYPE
67 Indicate the CPU type of the system which the jobs will execute on.
68 This parameter sets the value of the $(GLOBUS_HOST_CPUTYPE) RSL
69 substitution to CPUTYPE
70 -globus-host-osname OSNAME
72 Indicate the operating system type of the system which the jobs
73 will execute on. This parameter sets the value of the
74 $(GLOBUS_HOST_OSNAME) RSL substitution to OSNAME
75 -globus-host-osversion OSVERSION
77 Indicate the operating system version of the system which the jobs
78 will execute on. This parameter sets the value of the
79 $(GLOBUS_HOST_OSVERSION) RSL substitution to OSVERSION
80 -globus-gatekeeper-host HOST
82 Indicate the host name of the machine which the job was submitted
83 to. This parameter sets the value of the $(GLOBUS_GATEKEEPER_HOST)
84 RSL substitution to HOST
85 -globus-gatekeeper-port PORT
87 Indicate the TCP port number of gatekeeper to which jobs are
88 submitted to. This parameter sets the value of the
89 $(GLOBUS_GATEKEEPER_PORT) RSL substitution to PORT
90 -globus-gatekeeper-subject SUBJECT
92 Indicate the X.509 identity of the gatekeeper to which jobs are
93 submitted to. This parameter sets the value of the
94 $(GLOBUS_GATEKEEPER_SUBJECT) RSL substitution to SUBJECT
95 -home GLOBUS_LOCATION
97 Indicate the path where the Globus Toolkit(r) is installed on the
98 service node. This is used by the job manager to locate its support
99 and configuration files.
100 -target-globus-location TARGET_GLOBUS_LOCATION
102 Indicate the path where the Globus Toolkit(r) is installed on the
103 execution host. If this is omitted, the value specified as a
104 parameter to -home is used. This parameter sets the value of the
105 $(GLOBUS_LOCATION) RSL substitution to TARGET_GLOBUS_LOCATION
106 -history HISTORY_DIRECTORY
108 Configure the job manager to write job history files to
109 HISTORY_DIRECTORY. These files are described in the FILES section
110 below.
111 -scratch-dir-base SCRATCH_DIRECTORY
113 Configure the job manager to use SCRATCH_DIRECTORY as the default
114 scratch directory root if a relative path is specified in the job
115 RSL´s scratch_dir attribute.
116 -enable-syslog
118 Configure the job manager to write log messages via syslog. Logging
119 is further controlled by the argument to the -log-levels parameter
120 described below.
121 -log-pattern PATTERN
123 Configure the job manager to write log messages to files named by
124 the string PATTERN. The PATTERN string may contain job-independent
125 RSL substitutions such as $(HOME), $(LOGNAME), etc, as well as the
126 special RSL substition $(DATE) which will be resolved at log time
127 to the date in YYYYMMDD form.
128 -stdio-log LOG_DIRECTORY
130 Configure the job manager to write log messages to files in the
131 LOG_DIRECTORY directory. This is a backward-compatible parameter,
132 equivalent to -log-pattern LOG_DIRECTORY/gram_$(DATE).log.
133 -log-levels LEVELS
135 Configure the job manager to write log messages of certain levels
136 to syslog and/or log files. The available log levels are FATAL,
137 ERROR, WARN, INFO, DEBUG, and TRACE. Multiple values can be
138 combined with the | character. The default value of logging when
139 enabled is FATAL|ERROR.
140 -state-file-dir STATE_DIRECTORY
142 Configure the job manager to write state files to STATE_DIRECTORY.
143 If not specified, the job manager uses the default of
144 $GLOBUS_LOCATION/tmp/gram_job_state/. This directory must be
145 writable by all users and be on a file system which supports POSIX
146 advisory file locks.
147 -globus-tcp-port-range PORT_RANGE
149 Configure the job manager to restrict its TCP/IP communication to
150 use ports in the range described by PORT_RANGE. This value is also
151 made available in the job environment via the GLOBUS_TCP_PORT_RANGE
152 environment variable.
153 -x509-cert-dir TRUSTED_CERTIFICATE_DIRECTORY
155 Configure the job manager to search TRUSTED_CERTIFICATE_DIRECTORY
156 for its list of trusted CA certificates and their signing policies.
157 This value is also made available in the job environment via the
158 X509_CERT_DIR environment variable.
159 -cache-location GASS_CACHE_DIRECTORY
161 Configure the job manager to use the path GASS_CACHE_DIRECTORY for
162 its temporary GASS-cache files. This value is also made available
163 in the job environment via the GLOBUS_GASS_CACHE_DEFAULT
164 environment variable.
165 -k
167 Configure the job manager to assume it is using Kerberos for
168 authentication instead of X.509 certificates. This disables some
169 certificate-specific processing in the job manager.
170 -extra-envvars VAR=VAL,...
172 Configure the job manager to define a set of environment variables
173 in the job environment beyond those defined in the base job
174 environment. The format of the parameter to this argument is a
175 comma-separated sequence of VAR=VAL pairs, where VAR is the
176 variable name and VAL is the variables value.
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 -disable-usagestats
207 Disable sending of any usage stats data, even if
208 -usagestats-targets is present in the configuration.
209 -usagestats-targets TARGET
211 Send usage packets to a data collection service for analysis. The
212 TARGET string consists of a comma-separated list of HOST:PORT
213 combinations, each contaiing an optional list of data to send. See
214 Usage Stats Packets[1] for more information about the tags. Special
215 tag strings of all (which enables all tags) and default may be
216 used, or a sequence of characters for the various tags. If this
217 option is not present in the configuration, then the default of
218 usage-stats.globus.org:4810 is used.
219 -condor-arch ARCH
221 Set the architecture specification for condor jobs to be ARCH in
222 job classified ads generated by the GRAM5 codnor LRM script. This
223 is required for the condor LRM but ignored for all others.
224 -condor-os OS
226 Set the operating system specification for condor jobs to be OS in
227 job classified ads generated by the GRAM5 codnor LRM script. This
228 is required for the condor LRM but ignored for all others.
229
231 If the following variables affect the execution of globus-job-manager
232 HOME
234 User´s home directory.
235 LOGNAME
237 User´s name.
238 JOBMANAGER_SYSLOG_ID
240 String to prepend to syslog audit messages.
241 JOBMANAGER_SYSLOG_FAC
243 Facility to log syslog audit messages as.
244 JOBMANAGER_SYSLOG_LVL
246 Priority level to use for syslog audit messages.
247 GATEKEEPER_JM_ID
249 Job manager ID to be used in syslog audit records.
250 GATEKEEPER_PEER
252 Peer information to be used in syslog audit records
253 GLOBUS_ID
255 Credential information to be used in syslog audit records
256 GLOBUS_JOB_MANAGER_SLEEP
258 Time (in seconds) to sleep when the job manager is started. [For
259 debugging purposes only]
260 GRID_SECURITY_HTTP_BODY_FD
262 File descriptor of an open file which contains the initial job
263 request and to which the initial job reply should be sent. This
264 file descriptor is inherited from the globus-gatekeeper.
265 X509_USER_PROXY
267 Path to the X.509 user proxy which was delegated by the client to
268 the globus-gatekeeper program to be used by the job manager.
269 GRID_SECURITY_CONTEXT_FD
271 File descriptor containing an exported security context that the
272 job manager should use to reply to the client which submitted the
273 job.
274 GLOBUS_USAGE_TARGETS
276 Default list of usagestats services to send usage packets to.
277
279 $HOME/.globus/job/HOSTNAME/LRM.TAG.red
280 Job manager delegated user credential.
281 $HOME/.globus/job/HOSTNAME/LRM.TAG.lock
283 Job manager state lock file.
284 $HOME/.globus/job/HOSTNAME/LRM.TAG.pid
286 Job manager pid file.
287 $HOME/.globus/job/HOSTNAME/LRM.TAG.sock
289 Job manager socket for inter-job manager communications.
290 $HOME/.globus/job/HOSTNAME/JOB_ID/
292 Job-specific state directory.
293 $HOME/.globus/job/HOSTNAME/JOB_ID/stdin
295 Standard input which has been staged from a remote URL.
296 $HOME/.globus/job/HOSTNAME/JOB_ID/stdout
298 Standard output which will be staged from a remote URL.
299 $HOME/.globus/job/HOSTNAME/JOB_ID/stderr
301 Standard error which will be staged from a remote URL.
302 $HOME/.globus/job/HOSTNAME/JOB_ID/x509_user_proxy
304 Job-specific delegated credential.
305 $GLOBUS_LOCATION/tmp/gram_job_state/job.HOSTNAME.JOB_ID
307 Job state file.
308 $GLOBUS_LOCATION/tmp/gram_job_state/job.HOSTNAME.JOB_ID.lock
310 Job state lock file. In most cases this will be a symlink to the
311 job manager lock file.
312 $GLOBUS_LOCATION/etc/globus-job-manager.conf
314 Default location of the global job manager configuration file.
315 $GLOBUS_LOCATION/etc/grid-services/jobmanager-LRM
317 Default location of the LRM-specific gatekeeper configuration file.
318
320 globusrun(1), globus-gatekeeper(8), globus-personal-gatekeeper(1),
321 globus-gram-audit(8)
322
324 1. Usage Stats Packets
325 http://confluence.globus.org/display/~bester/GRAM5+Usage+Stats+Packets
326University of Chicago 03/08/2011 GLOBUS-JOB-MANAGER(8)