WE are deploying/configuring a new Grid site named PK-CIIT consists of the following
Gllite version = Glite3.2
CREAMCE (cern-56-24-244.comsats.edu.pk)
VOBOX for ALICE (cern-56-24-242.comsats.edu.pk) site BDII (cern-56-24-243.comsats.edu.pk) Worker Nodes (logical CPUS = 80)
We are facing problems on our site bdii and CREAME CE.
Following rpm are installed in site BDII:
glite-yaim-bdii-4.1.12-1.noarch
bdii-config-site-0.9.1-1.noarch
fix-bdii-conf-1.1.0-1.noarch
bdii-5.2.5-1.el5.noarch
glite-info-provider-ldap-1.3.4-1.noarch
glite-info-provider-service-1.4.4-1.noarch
glite-info-provider-release-1.0.2-1.noarch
The following command only gives the following information:
ldapsearch -x -H ldap://cern-56-24-243.comsats.edu.pk:2170 -b "mds-vo-name=resource,o=grid"
# extended LDIF
#
# LDAPv3
# base <mds-vo-name=resource,o=grid> with scope subtree # filter: (objectclass=*) # requesting: ALL #
# resource, grid
dn: Mds-Vo-name=resource,o=grid
Mds-Vo-name: resource
objectClass: Mds
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
From above results of the ldapserach command, it seems that Site BDII even does not publishing its own information
Moreover CREAMCE gives the same response and does not publish its information to Site BDII.
ldapsearch -x -H ldap://cern-56-24-244.comsats.edu.pk:2170 -b "mds-vo-name=resource,o=grid"
# extended LDIF
#
# LDAPv3
# base <mds-vo-name=resource,o=grid> with scope subtree # filter: (objectclass=*) # requesting: ALL #
# resource, grid
dn: Mds-Vo-name=resource,o=grid
Mds-Vo-name: resource
objectClass: Mds
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
Whereas vobox is publishing its information through ldapsearch command. But it is not publishing its information to siteBDII.
In site bdii, glite-bdii_site file, the following lines are already added
# List of hosts where there are services that want to publish into the BDII BDII_REGIONS="SBDII CREAMCE VOBOX"
# The following example is valid for hosts using BDII.
# If your host is using MDS instead (all 3.0 nodes) # change the port to 2135 and mds-vo-name=local BDII_SBDII_URL="ldap://cern-56-24-243.comsats.edu.pk:2170/mds-vo-name=resource,o=grid"
BDII_CREAMCE_URL="ldap://cern-56-24-244.comsats.edu.pk:2170/mds-vo-name=resource,o=grid"
BDII_VOBOX_URL="ldap://cern-56-24-242.comsats.edu.pk:2170/mds-vo-name=resource,o=grid"
On our site BDII, the ldif files are given below:
[root@cern-56-24-243 ~]# locate *.ldif
/etc/openldap/schema/core.ldif
/etc/openldap/schema/openldap.ldif
/opt/glite/etc/glue1.test.ldif
/opt/glite/etc/glue2.test.ldif
/opt/glite/var/cache/gip/site-urls.conf/SBDII.ldif
/var/lib/bdii/old.ldif
/var/lib/bdii/gip/ldif/default.ldif
There are no CREAMCE.ldif and VOBOX.ldif files in /opt/glite/var/cache/gip/site-urls.conf directory.
The permissions of the directories are
[root@cern-56-24-243 ~]# ll /opt/glite/var/cache/gip/
total 4
drwxr-xr-x 2 ldap ldap 4096 Feb 4 19:33 site-urls.conf
[root@cern-56-24-243 ~]# ll /opt/glite/var/tmp
total 16
drwxr-xr-x 4 ldap ldap 4096 Feb 5 17:50 gip
drwxr-xr-x 2 ldap ldap 4096 Feb 25 2011 log
Please suggest any solution.
Regards
Muhammad Umair Naru
|