 |
 |
Dear Stephen, Currently I use the following: # Hostname of the top level BDII BDII_HOST=bdii.grid.am # Hostname of the site BDII SITE_BDII_HOST=bdii.$MY_DOMAIN bdii.grid.am is the top bdii of Armenian NGI. So what do you suggest to change and the re-configure? YAIM for CE: /opt/glite/yaim/bin/yaim -c -s /opt/site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils YAIM for BDII and APEL (same server): /opt/glite/yaim/bin/yaim -c -s /opt/site-info.def -n APEL -n BDII_site Regards, Hrach On 7/22/11 3:01 PM, Stephen Burke wrote: > LHC Computer Grid - Rollout [mailto:[log in to unmask]] said: >> MY_DOMAIN=yerphi-cluster.grid.am >> CE_HOST=ce.$MY_DOMAIN >> DPM_HOST="se.$MY_DOMAIN" >> MON_HOST=apel.$MY_DOMAIN > Your CE information is now there, but you seem to still have a site bdii config on it: > > ldapsearch -x -h ce.yerphi-cluster.grid.am -p 2170 -b mds-vo-name=resource,o=grid objectclass=gluesite | grep UniqueID: > GlueSiteUniqueID: MySite > > ldapsearch -x -h ce.yerphi-cluster.grid.am -p 2170 -b mds-vo-name=resource,o=grid objectclass=glueservice | grep Type: > GlueServiceType: bdii_site > > You need to get rid of the old site bdii configuration on the CE, it should only publish CE-related information. > > Also I don't understand the apel node above; it also seems to be running a site bdii, but you said your site bdii is on a node called bdii which resolves to a different address. Probably you need to change to something like BDII_HOST=bdii.$MY_DOMAIN - the configuration should include the site bdii itself. And again, remove the site bdii config from the apel node if it's no longer needed. > > Stephen