Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

Using Globus Jobmanager accounting

Note: This is not a standard feature of Globus 2.4.3. This feature is only available in the VDT 1.1.13 version of Globus. The efforts to enable this feature have been contributed by our LCG users. If you would like to know more about this feature please refer to patches 13__job_manager_acct and 14__gatekeeper_acct at patches and bugfixes in Globus2.4.3. We are working with the Globus developers to see if this feature becomes a part of the standard Globus distribution.

Who should use Jobmanager accouting?

If you manage lot of resources and have a heavy traffic of jobs being executed at your site then Jobmanager accounting might be helpful to you. You can use this new feature available in the VDT version of Globus that supports accounting of the jobs being executed at your site. This feature is also useful for people to know which Globus user has submitted a job to the local batch system and process this information to cater to their needs.

What is Jobmanager accounting?

For each job that Globus executes, it writes the accounting information to the accounting file (gatekeeper log file by default). For each job, the accounting information is of the following format

JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID <ID> for <DN> on <IP-addr>
JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID <ID> has GRAM_SCRIPT_JOB_ID <JOB_ID> manager type <type>
JMA YYYY/MM/DD HH:MM:SS GATEKEEPER_JM_ID <ID> JM exiting 

Where,
<ID> is string has this format: YYYY-MM-DD.HH:MM:SS.<PID>.<SEQ>
<ID> string is obtained from the "GATEKEEPER_JM_ID" environment variable defined by the gatekeeper.
<PID> is the PID of the gatekeeper left-padded with zeroes to have 10 digits.
<SEQ> is request sequence number (incremented per connection) left-padded with zeroes to have 10 digits.
<DN> is the certificate subject (Distinguished Name) of the user submitting the job
<JOB_ID> is the Job Id as reported by the jobmanager of local batch system
<IP-addr> is the IP address of the machine from which user submitted the job.
The second JMA line allows the job's <DN> and originating host to be linked to the job's accounting information recorded by the batch system.

How do you enable Jobmanager accounting?

To enable accounting information to be logged to a different file is fairly straight forward. It is available as a command line option. When you start the gatekeeper provide an extra option -acctfile <filename>, where filename is a complete path to the accounting log file.

So after enabling accounting to be logged to a different log file the ${VDT_LOCATION}/globus/etc/globus-gatekeeper.conf should look like -

 % cat ${GLOBUS_LOCATION}/etc/globus-gatekeeper.conf

  -x509_cert_dir /scratch.1/vdt/1.1.13/globus/TRUSTED_CA
  -x509_user_cert /etc/grid-security/hostcert.pem
  -x509_user_key /etc/grid-security/hostkey.pem
  -gridmap /etc/grid-security/grid-mapfile
  -home /scratch.1/vdt/1.1.13/globus
  -e libexec
  -logfile var/globus-gatekeeper.log
  -port 2119
  -grid_services etc/grid-services
  -acctfile /scratch.1/vdt/1.1.13/globus/var/accounting.log
  -inetd
    

If you already have a gatekeeper running, restart it for the changes to take effect.