When to run this procedure

You should run this procedure when there is an intervention that requires the LFC daemons to be stopped. Usually you will:

  1. stop the service
  2. inform the person doing the intervention
  3. restart the service
  4. verify service is back

Step description

Stopping the service

To stop all LFC daemons on all nodes of GRIDLFC cluster you may (please read-on for information on how to stop for a single VO):

note: if all boxes are SMS state maintenance you don't need to disable the LFC lemon exceptions.

wassh -l root -c gridlfc "lemon-host-check -d 30051,30052,30059,30075,30082,30083,30084; service lfcdaemon stop; service lfc-dli stop;"

To stop LFC daemons for a single VO you may

note: if all boxes are SMS state maintenance you don't need to disable the LFC lemon exceptions.

wassh -l root -c gridlfc/'lfc-instance-name' "lemon-host-check -d 30051,30052,30059,30075,30082,30083,30084; service lfcdaemon stop; service lfc-dli stop;"

Starting the service

After a DB Intervention

To check after a DB intervention that the DB is available, log onto the node and run:

sqlplus `cat /opt/lcg/etc/NSCONFIG`
This should log you into Oracle. To check things are ok, do select * from schema_version; You should get back one line of output, as in example below:
[root@lfc201 root]# sqlplus `cat /opt/lcg/etc/NSCONFIG`

SQL*Plus: Release 10.2.0.1.0 - Production on Thu Feb 22 09:21:37 2007

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options

SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
[root@lfc201 root]# sqlplus `cat /opt/lcg/etc/NSCONFIG`

SQL*Plus: Release 10.2.0.1.0 - Production on Thu Feb 22 09:22:28 2007

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options

SQL> select * from schema_version;

     MAJOR      MINOR      PATCH
---------- ---------- ----------
         3          0          0

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options

To start all LFC daemons on all nodes you may (please read on for information on how to start for a single VO):

wassh -l root -c gridlfc "service lfcdaemon start; service lfc-dli start; lemon-host-check -e 30051,30052,30059,30075,30082,30083,30084; lemon-host-check;"

To start LFC daemons for a single VO you may

wassh -l root -c gridlfc/'lfc-instance-name' "service lfcdaemon start; service lfc-dli start; lemon-host-check -e 30051,30052,30059,30075,30082,30083,30084; lemon-host-check;"

Verifying minimal functionalities

wassh -l root -c gridlfc "service lfcdaemon status; service lfc-dli status; bash; export PATH=/opt/lcg/bin:$PATH; export LFC_HOST=\`hostname\`;lfc-ls /;"

and

  1. Logon lxplus
  2. source /afs/cern.ch/project/gd/LCG-share/sl3/etc/profile.d/grid_env.csh
  3. grid-proxy-init
  4. setenv LFC_HOST lfcxxx
  5. lfc-ls /grid/dteam
  6. lfc-mkdir /grid/dteam/essaix

or

export LFC_HOST=lfc101;lfc-ls /grid/dteam; lfc-mkdir /grid/dteam/`uuidgen`;

-- MiguelSantos - 21 Feb 2007

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2007-02-22 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG 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