ADMINISTRATION » History » Version 8

« Previous - Version 8/22 (diff) - Next » - Current version
Arthur Kreymer, 04/01/2013 11:39 AM



Working directories and files are under /grid/data/${GROUP}/LOCK

On the grid, the username does not reflect the identity of the
person who submitted the job.
So the lock script gets the identity from the grid proxy.

/LOCKS - active lock files
The lock files are empty, with names contining
date, time queued, host, pid, user, identity

/QUEUE - locks pending, empty files containing
date, host, pid, user, identity

/LOG - empty files with names reflecting completed locks
date, time queued, time locked, host, pid, user, identity

/LOGS - monthly text summaries built from LOG file names.

/STALE - record of locks that have timed out

glimit - global activity limit, including all user groups
set this near the actual Bluearc capacity
this is not implemented as of 2012-11-06

limit - local activity limit, for the users' own group
set this well under Bluearc capacity

perf - performance MB/sec required in PERF before locking

PERF - actual MB/sec performance, measured by external agent
( No agents implemented as of 2010-08-02 )

rate - net retry rate target, in retries per second

small - MBytes: files smaller than this are not locked by cpn.

wait - mininum time to wait before retrying, regardless of the load.
the time delay before retrying a lock is the minimum of
  • wait
  • (number of queued locks)/rate


lock files should be owned by some appropriate group account, like mindata.

That account should occasionally remove expired locks and queue entries,
and concatenate LOG entries into monthly summary files.

You can run the lockclean script manually, which will do this hourly :
But be careful, interactive logins on gpsn01 are in group gpcf.
Use 'sg' to set the proper group first

    sg -g <mygroup> /bin/bash
    set nohup ; /grid/fermiapp/common/tools/lockclean &

There should be a crontab entry for each account like
@reboot sg <mygroup> -c /grid/fermiapp/common/tools/lockclean

Group Account@Host crontab
des desdata@gpsn01
e875 mindata@minos27
e938 minervadat@if02
gm2 gm2dat@gpsn01
gpcf ifmon@gpsn01 @reboot sg gpcf -c /grid/fermiapp/common/tools/lockclean
lbne lbnedata@lbnegpvm01
marsmu2e marsmu2e@detsim
mu2e mu2e@mu2egpvm01
mu2epro mu2epro@mu2egpvm01
t-962 argoneut@argoneutgpvm01 @reboot /grid/fermiapp/common/tools/lockclean
uboone uboone@uboonegpvm01
nova novadata@gpcf028


Get an idea of activity by counting lines in log files.

For example, for Minos,

$ wc -l /grid/data/e875/LOCK/LOGS/*.log
9124 /grid/data/e875/LOCK/LOGS/200908.log
140794 /grid/data/e875/LOCK/LOGS/200909.log
181895 /grid/data/e875/LOCK/LOGS/200910.log
196327 /grid/data/e875/LOCK/LOGS/200911.log
125084 /grid/data/e875/LOCK/LOGS/200912.log
272598 /grid/data/e875/LOCK/LOGS/201001.log
284000 /grid/data/e875/LOCK/LOGS/201002.log
275479 /grid/data/e875/LOCK/LOGS/201003.log
354725 /grid/data/e875/LOCK/LOGS/201004.log
1840026 total
$ wc -l /grid/data/e875/LOCK/STALE/LOCKS/*.log
$ wc -l /grid/data/e875/LOCK/STALE/QUEUE/*.log


To start up a new group's LOCKs,
the group should give REX DH people access to the account,
and issue a ServiceNow ticket to have the files set up.
The .k5login should include


REX will verify that the group id name is the same
on Fermigrid nodes and in the Lab GID registry, at

REX will then log in to the account
and use 'ups tailor cpn' to create the default files.
( Available from cpn v1.3 onward )

ups tailor cpn          - will echo the commands proposed 
ups tailor cpn -O write - will execute the commands