Node Type: dCacheSiteBDII

t3bdii.psi.ch is currently an alias to t3nfs01.psi.ch

Firewall requirements

local port open to reason
2170/tcp * Site information system (ldap)


Regular Maintenance work

Emergency Measures

Installation

External references:

Add this to the yum configuration:

# This is the official YUM repository string for the glite 3.1 BDII
# Fetched from: http://grid-deployment.web.cern.ch/grid-deployment/yaim/repos/glite-BDII.repo
# Place it to /etc/yum.repos.d/ and run 'yum update'

[glite-BDII]
name=gLite 3.1 BDII service
baseurl=http://linuxsoft.cern.ch/EGEE/gLite/R3.1/glite-BDII/sl4/i386/
enabled=0

Now, install the BDII software

yum install glite-BDII

...

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 glite-BDII              i386       3.1.8-0          glite-BDII        1.7 k
Installing for dependencies:
 bdii                    noarch     3.9.1-5          glite-BDII         19 k
 glite-info-generic      noarch     2.0.2-3          glite-BDII        5.4 k
 glite-info-plugin-fcr   noarch     1.0.0-3          glite-BDII        2.9 k
 glite-info-provider-ldap  noarch     1.1.0-1          glite-BDII        4.3 k
 glite-info-provider-service  noarch     1.0.0-6          glite-BDII         20 k
 glite-info-templates    noarch     1.0.0-8          glite-BDII        8.6 k
 glite-info-update-endpoints  noarch     1.0.0-5          glite-BDII        2.9 k
 glite-version           i386       3.1.0-1.slc4     glite-BDII        1.9 k
 glite-yaim-bdii         noarch     4.0.4-2          glite-BDII        8.9 k
 glite-yaim-core         noarch     4.0.4-2          glite-BDII        106 k
 glue-schema             noarch     1.3.0-3          glite-BDII         30 k
 openldap-clients        x86_64     2.2.13-8.el4_6.5  sl46update        138 k
 openldap-servers        x86_64     2.2.13-8.el4_6.5  sl46update        3.4 M
 perl-Convert-ASN1       noarch     0.18-3           sl46base           33 k
 perl-LDAP               noarch     0.31-5           sl46base          247 k
 perl-XML-NamespaceSupport  noarch     1.08-6           sl46base           13 k
 perl-XML-SAX            noarch     0.12-7           sl46base           75 k
Updating for dependencies:
 openldap                x86_64     2.2.13-8.el4_6.5  sl46update        262 k
 openldap-devel          x86_64     2.2.13-8.el4_6.5  sl46update        1.4 M

Transaction Summary
=============================================================================
Install     18 Package(s)
Update       2 Package(s)
Remove       0 Package(s)
Total download size: 5.8 M
Is this ok [y/N]:                                                                                       

...

Installed: glite-BDII.i386 0:3.1.8-0
Dependency Installed: bdii.noarch 0:3.9.1-5 glite-info-generic.noarch 0:2.0.2-3 glite-info-plugin-fcr.noarch 0:1.0.0-3 glite-info-provider-ldap.noarch 0:1.1.0-1 glite-info-provider-service.noarch 0:1.0.0-6 glite-info-templates.noarch 0:1.0.0-8 glite-info-update-endpoints.noarch 0:1.0.0-5 glite-version.i386 0:3.1.0-1.slc4 glite-yaim-bdii.noarch 0:4.0.4-2 glite-yaim-core.noarch 0:4.0.4-2 glue-schema.noarch 0:1.3.0-3 openldap-clients.x86_64 0:2.2.13-8.el4_6.5 openldap-servers.x86_64 0:2.2.13-8.el4_6.5 perl-Convert-ASN1.noarch 0:0.18-3 perl-LDAP.noarch 0:0.31-5 perl-XML-NamespaceSupport.noarch 0:1.08-6 perl-XML-SAX.noarch 0:0.12-7
Dependency Updated: openldap.x86_64 0:2.2.13-8.el4_6.5 openldap-devel.x86_64 0:2.2.13-8.el4_6.5
Complete!

YAIM configuration and the config file

Make sure that the YAIM configuration file site-info.def contains all the correct BDII settings. We store the YAIM configuration files at /root/YAIM-config/site-info.def.

Check YAIM config (Note that I had to generate a symbolic link glite-BDII_site to glite-bdii_site, because the idiotic script needs the component string in capitals).

/opt/glite/yaim/bin/yaim -v -s site-info.def -n glite-BDII_site
...
   INFO: Executing function: config_gip_site_check
   ERROR: SITE_DESC is not set
   ERROR: SITE_SECURITY_EMAIL is not set
...

I had to add these changes to the site-info.def since the schema had changed as described in the GOC "How_to_publish_my_site_information"

# new site-wide settings that needed to be added (https://savannah.cern.ch/patch/index.php?1786)
SITE_DESC="CMS Tier-3 Paul Scherrer Institut (PSI)"
SITE_SECURITY_EMAIL=tier3@lists.psi.ch
SITE_OTHER_WLCG_TIER=3
# these settings are obsolete and needed to be commented
# SITE_TIER="TIER 3"
# SITE_SUPPORT_SITE="https://twiki.cscs.ch/twiki/bin/view/LCGTier2/WebHome"

/opt/glite/yaim/bin/yaim -c -s site-info.def -n glite-BDII_site

/opt/glite/yaim/functions/config_gip_bdii_site: line 46: [: =: unary operator expected
   INFO: -   --   ---  ----  o  oo ooo OOO #### OOO ooo oo  o  ----  ---  --  -
         .  __  _____   ______  ___
         .  \ \/ / _ | /  _/  |/  /  Current Working directory is: /root/YAIM-config
         .   \  / __ |_/ // /|_/ /   Site-info file used: Sep 2 21:18 site-info.def
         .   /_/_/ |_/___/_/  /_/    Tue Sep  2 22:13:00 CEST 2008 : /opt/glite/yaim/bin/yaim -c -s site-info.def -n glite-BDII_site
         YAIM versions used: glite-yaim-core-4.0.4-2.noarch ; glite-yaim-bdii-4.0.4-2.noarch ;
   INFO: Output will be written into log file: /opt/glite/yaim/bin/../log/yaimlog
   INFO: Using site configuration file: site-info.def
   INFO: The default location of the grid-env.(c)sh files will be: /opt/glite/etc/profile.d
   INFO: Sourcing the utilities in /opt/glite/yaim/functions/utils
   INFO: Detecting environment
   INFO: Executing function: config_gip_site_check
   INFO: Executing function: config_gip_bdii_site_check
   INFO: Executing function: config_info_service_bdii_site_check
   INFO: Executing function: config_edgusers
   INFO: Executing function: config_bdii_only
Stopping BDII                                              [FAILED]
Starting BDII                                              [  OK  ]
   INFO: Executing function: config_gip_only
   INFO: Executing function: config_gip_site
   INFO: Executing function: config_gip_bdii_site
   INFO: Executing function: config_info_service_bdii_site_setenv
   INFO: Executing function: config_info_service_bdii_site
   INFO: Configuration Complete.                                               [  OK  ]

Testing

To test the local BDII:

ldapsearch -x -h t3bdii.psi.ch -p 2170 -b "mds-vo-name=T3_CH_PSI,o=grid"
ldapsearch -x -h t3bdii.psi.ch -p 2170 -b "o=grid"

To test for our entries in the central BDII

ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b "mds-vo-name=T3_CH_PSI,mds-vo-name=local,o=grid"

Upgrade on 2009-01-13

  1. Stopped bdii and used yum to pull in updates for the BDII:
  2. Updated packages:
    glite-yaim-bdii         noarch     4.0.4-6
    glite-BDII              i386       3.1.12-0         glite-BDII        2.7 k
    Updating for dependencies:
     bdii                    noarch     4.0.1-0          glite-BDII         23 k
     glite-info-provider-ldap  noarch     1.2.2-2          glite-BDII        5.7 k
     glite-info-provider-service  noarch     1.0.1-3          glite-BDII         21 k
     glite-yaim-core         noarch     4.0.5-7          glite-BDII        108 k
     glue-schema             noarch     1.3.0-5          glite-BDII         30 k
    
  3. Ran YAIM again:
    /opt/glite/yaim/bin/yaim -v -s site-info.def -n glite-BDII_site
    
  4. Restarted BDII.

Upgrade to GLITE 3.2 service

Documentation:

Testing

Dump of the complete LDAP information

 
slapcat -f /opt/bdii/etc/bdii-slapd.conf

Searches from external nodes (note that the ldap bdii will not reply on the localhost interface)

ldapsearch -x -h t3vmbdii.psi.ch -p 2170 -b "o=grid"

ldapsearch -x -h t3bdii.psi.ch -p 2170 -b "Mds-Vo-name=t3_ch_psi,o=grid"

ldapsearch -x -h t3bdii.psi.ch -p 2170 -b "Mds-Vo-name=resource,o=grid"

To test for our entries in the central BDII

ldapsearch -x -h lcg-bdii.cern.ch -p 2170 -b "mds-vo-name=T3_CH_PSI,mds-vo-name=local,o=grid"

Troubleshooting

  • If the network is down or in case of some network problem at service start, the whole LDAP will remain empty. A restart will be needed.
  • There is a service configuration file at /opt/bdii/etc/bdii.conf. In there, one can configure the log level and also the log file location
    BDII_LOG_FILE=/var/log/bdii/bdii-update.log
    BDII_LOG_LEVEL=ERROR
    
    Set the level to WARNING for more verbose logging.

Installation of openldap2.4 as countermeasure to frequent bdii crashes

following description at http://glite.cern.ch/glite-BDII_site/known_issues and using the RPMs from the links on this page:
lib64ldap2.4_2-2.4.22-1.el5.x86_64.rpm  openldap2.4-extra-schemas-1.3-10.el5.noarch.rpm
openldap2.4-2.4.22-1.el5.x86_64.rpm     openldap2.4-servers-2.4.22-1.el5.x86_64.rpm
Extra dependency to install: unixODBC-2.2.11-7.1.x86_64.rpm

Install the package, stop the BDII service, set SLAPD=/usr/sbin/slapd2.4 in the /etc/sysconfig/bdii file and start the BDII service again.

Services

Backups

-- DerekFeichtinger - 29 Aug 2008

NodeTypeForm
Hostnames t3bdii02
Services Site BDII
Hardware VM
Install Profile t3bdii
Guarantee/maintenance until VM
Edit | Attach | Watch | Print version | History: r34 | r18 < r17 < r16 < r15 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r16 - 2011-08-11 - DerekFeichtinger
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback