Node Type: dCacheSiteBDII

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

Firewall requirements

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

---

Regular Maintenance work

The Site BDII is quite stable, simply have a look to the t3bdii02 page inside t3nagios to check our bdii status.

Emergency Measures

Installation

OLD External references:

• Glite node generic install guide
• YAIM guide
  • How to correctly override YAIM functions
• GOCwiki: How_to_publish_my_site_information
• LCG directory documentation portal
• CCRC08 page with WLCG-GLUE Schema for CCRC08 which is still the valid schema as of 2008-11-27
• usage of WLCG-GLUE Schema v1.3 (Version 1.8.7, dated 2009-02-03)

Procedure for gLite 3.2

Official Admin How To for BDII Site gLite 3.2.

Add this file to the yum.repos.d directory:

[root@t3bdii02 yum.repos.d]# cat glite-BDII_site.repo
# This is the official YUM repository string for the glite 3.2 BDII_site
# Fetched from: http://grid-deployment.web.cern.ch/grid-deployment/yaim/repos/glite-BDII_site.repo
# Place it to /etc/yum.repos.d/ and run 'yum update' 
[glite-BDII_site]
name=gLite 3.2 BDII_site
baseurl=http://glitesoft.cern.ch/EGEE/gLite/R3.2/glite-BDII_site/sl5/x86_64/RPMS.release/
gpgkey=http://glite.web.cern.ch/glite/glite_key_gd.asc
gpgcheck=1
enabled=1

[glite-BDII_site_updates]
name=gLite 3.2 BDII_site updates
baseurl=http://glitesoft.cern.ch/EGEE/gLite/R3.2/glite-BDII_site/sl5/x86_64/RPMS.updates/
gpgkey=http://glite.web.cern.ch/glite/glite_key_gd.asc
gpgcheck=1
enabled=1

[glite-BDII_site_ext]
name=gLite 3.2 BDII_site external
baseurl=http://glitesoft.cern.ch/EGEE/gLite/R3.2/glite-BDII_site/sl5/x86_64/RPMS.externals/
gpgcheck=0
enabled=1

Then install the RPM:

yum install glite-BDII_site

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, then configure.

   INFO: Using site configuration file: ./site-info.def
   INFO: 
         ###################################################################
         
         .             /'.-. ')
         .     yA,-"-,( ,m,:/ )   .oo.     oo    o      ooo  o.     .oo
         .    /      .-Y a  a Y-.     8. .8'    8'8.     8    8b   d'8
         .   /           ~ ~ /         8'    .8oo88.     8    8  8'  8
         . (_/         '===='          8    .8'     8.   8    8  Y   8
         .   Y,-''-,Yy,-.,/           o8o  o8o    o88o  o8o  o8o    o8o
         .    I_))_) I_))_)
         
         
         current working directory: /root/YAIM-config
         site-info.def date: Jul 19 16:18 ./site-info.def
         yaim command: -d 5 -c -s ./site-info.def -n BDII_site
         log file: /opt/glite/yaim/bin/../log/yaimlog
         Tue Jul 19 16:18:15 CEST 2011 : /opt/glite/yaim/bin/yaim
         
         Installed YAIM versions:
         glite-yaim-bdii ame:-ame:
         glite-yaim-core 4.0.14-1
         
         ####################################################################
   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_bdii_5.1_check 
   INFO: Executing function: config_gip_site 
SITE_COUNTRY =  Switzerland
   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: Executing function: config_bdii_5.1 
Stopping BDII update process:                              [  OK  ]
Stopping BDII slapd:                                       [  OK  ]
Starting BDII slapd:                                       [  OK  ]
Starting BDII update process:                              [  OK  ]
   INFO: Configuration Complete.                                               [  OK  ]
   INFO: YAIM terminated succesfully.

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 NGI-DE BDII:

ldapsearch -x -h bdii-fzk.gridka.de -p 2170 -b "mds-vo-name=T3_CH_PSI,mds-vo-name=local,o=grid"

Troubleshooting

Net Down

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.

Debug level

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.

Frequent openldap crashes

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

You can turn on/off or check the the bdii with:

/etc/init.d/bdii {start|stop|restart|status|condrestart}

Backups

-- DerekFeichtinger - 29 Aug 2008