Today
SAGrid Core Services resolved a problem with NWU SiteBDII not reporting
correctly to the TopBDII. The problem was related to an upgrade
procedure, not very well documented, between IG release versions. As of
ig_15 gLite 3.2, a site is no longer permitted to install a SiteBDII and
Computing Element (CE) on the same machine. The main issue relates to
the versions of the BDII software. The Computing Element and the
Resource Information System no longer utilize the same version of BDII.
Therefore, it is extremely important to read the ig_release notes on
version upgrades prior to upgrading your enivironment. See the following
URL for these announcements: http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:updates:ig3_2_64:start
We started off by investigating log files. The log files for LDAP
information on the NWU SiteBDII exists at /var/log/bdii/bdii-update.log Herewith an extract from the log file:
mkdir /opt/glite/var/cache/gip/site-urls.conf: Permission denied at /opt/glite/libexec/glite-info-provider-ldap line 191
mkdir /opt/glite/var/cache/gip/site-urls.conf-glue2: Permission denied at /opt/glite/libexec/glite-info-provider-ldap line 191
The
user identifier in which slapd processes are executed was set
to "root" and not "ldap". You might find however in certain instances that
ownership permissions are not set on the respective directories and
cause services to fail, which was the case in NWU Site BDII. The user
identifier used to be edgusr prior to ig_15 release.
Once we assigned the correct permissions we updated the SiteBDII with yaim and almost immediately is appeared in our TopBDII. Additional information regarding the support call can be found at : https://ops.sagrid.ac.za/trac/ticket/407