Access to the machine

  • cms-http-group

Web areas

The following web areas (from CERN web services) are used to expose the produced data:

You must know the cmsfomon account password in order to change them in


Login to, or as yourself@yourdevvm if deploying on your vm for testing, and use the following instructions.

# Cleanup (set "mydevvmname" to "" or to your devvm name)
([ "$(hostname)" = "mydevvmname" ] || exit; echo "Cleanning..."
 crontab -r;  acrontab -e;  killall python python2.6 wget; ps axuwwwwf|grep cmsweb)
# kill whatever (a)cron processes that would still be running

# Backup
rm -rf /data/srv2 /data/cfg2
rsync -cavu /data/srv /data/srv2
mv /data/cfg /data/cfg2

# Get the latest HG tag from and set on the commands below
(VER=HG1506a; cd /data; git clone git:// cfg && cd cfg && git reset --hard $VER)

# edit /data/cfg/admin/InstallDev, comment line that runs ProxySeed and the one before

# Deploy
(VER=HG1506a REPO="-r comp=comp.pre" A=/data/cfg/admin
 PKGS="admin cmssls downtimecal sreadiness ssb";
 cd /data;
 # if testing on devvm, drop "-a $AUTH" or set AUTH to path where the secrets are
 $A/InstallDev -R comp@$VER -s image -v $VER -a $AUTH $REPO -p "$PKGS" -S -u $ADMIN)

# Run the Proxy Renewal
sudo su - yourself
mkdir -p /tmp/foo
cd /tmp/foo
git clone git:// x
x/admin/ProxySeed -t dev -d cmsweb@$(hostname -f):/data/srv/current/auth/proxy
rm -rf /tmp/foo

Login again there as cmsweb and run all cronjobs, one by one, to make sure they are all fine. Finally, do a kinit and run all acronjobs for that machine too.

When installing on a devvm, you don't get the acronjobs installed, so the output of the scripts won't be synced to the AFS areas. Either check the output of the scripts under /data/srv/state or copy it somewhere to be exposed by a web server.


There is no service to start/stop. All scripts run as (a)cronjobs. If you want to stop something, comment out its correspondent (a)cronjob line.

Proxy renewal

Upon receipt of a message telling the proxy is about to expire or has expired, you need to upload a new long term proxy credentions to myproxy. Login as yourself to vocms0128 and run:

mkdir -p /tmp/foo
cd /tmp/foo
git clone git:// x
x/admin/ProxySeed -t dev -d cmsweb@$(hostname -f):/data/srv/current/auth/proxy
rm -rf /tmp/foo

In case the deployment target is not /data/srv, you need to change this path too in the command above. If for some reason you cannot connect as yourself directly, login as cmsweb there, get a kerberos token for yourself@CERNNOSPAMPLEASE.CH, and then sudo su - yourself.


The logs can be found in /data/srv/logs/.

The lemon start page for this machine is:

The acronjobs exposes many of the produced files by copying them to /afs/ This is an AFS volume shared with other LCG tools, so be aware in case the quota reaches the limit:

$ fs lq /afs/
Volume Name                    Quota       Used %Used   Partition
p.cms.lcg                    3000000    1752015   58%          8%

There are (a)cronjobs in place to delete old logs and the historical data, so it should make sane usage of the space this AFS volume.

-- DiegoGomes - 03-Aug-2012

Edit | Attach | Watch | Print version | History: r19 < r18 < r17 < r16 < r15 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r19 - 2015-08-25 - DiegoGomes
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback