Dear Adeel,
however, i didnt see RB ldif fetch in bdii var/tmp, and the RB defined
in bdii update config seems referring to port 2135?
> unalias ls ; globus-job-run pcncp04.ncp.edu.pk `which ls` /opt/bdii/var/tmp/
CE.ldif
MON.ldif
PX.ldif
SE.ldif
lcg2-all-sites.conf
> globus-job-run pcncp04.ncp.edu.pk `which cat` /opt/bdii/etc/bdii-update.conf
CE ldap://pcncp04.ncp.edu.pk:2135/mds-vo-name=local,o=grid
SE ldap://pcncp22.ncp.edu.pk:2135/mds-vo-name=local,o=grid
RB ldap://pcncp24.ncp.edu.pk:2135/mds-vo-name=local,o=grid
SE2 ldap://pcncp23.ncp.edu.pk:2135/mds-vo-name=local,o=grid
PX ldap://myproxy.cern.ch:2135/mds-vo-name=local,o=grid
MON ldap://pcncp21.ncp.edu.pk:2135/mds-vo-name=local,o=grid
Br,
J
On Tue, 6 May 2008, Adeel-ur-Rehman wrote:
>
> Hi Jason,
>
> Thanks for your prompt reply. But even after correcting the issue as you
> suggested, the GSTAT behaviour is same as before. Even the ldapsearch query
> has no difference since before.
>
> Any ideas now,
>
> -- Best Regards --
> Adeel-ur-Rehman
>
> -----Original Message-----
> From: LHC Computer Grid - Rollout [mailto:[log in to unmask]] On
> Behalf Of Jason Shih
> Sent: Tuesday, May 06, 2008 11:28 AM
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] No Information published for WMS/BDII host on
> GSTAT (fwd)
>
> Hi Adeel,
>
> from bdii update config, the RB replaced by WMS should have bdii running
> on pcncp24, while you have configure site bdii to read from mds port
> instead. could you help updating the config and restart bdii. let us know
> if this help.
>
> --
> CE ldap://pcncp04.ncp.edu.pk:2135/mds-vo-name=local,o=grid
> SE ldap://pcncp22.ncp.edu.pk:2135/mds-vo-name=local,o=grid
> RB ldap://pcncp24.ncp.edu.pk:2135/mds-vo-name=local,o=grid
> SE2 ldap://pcncp23.ncp.edu.pk:2135/mds-vo-name=local,o=grid
> PX ldap://myproxy.cern.ch:2135/mds-vo-name=local,o=grid
> MON ldap://pcncp21.ncp.edu.pk:2135/mds-vo-name=local,o=grid
>
> > ldapsearch -x -H ldap://pcncp04.ncp.edu.pk:2170 -b
> mds-vo-name=NCP-Lcg2,o=grid |grep GlueServiceUniqueID
> dn: GlueServiceUniqueID=pcncp21.ncp.edu.pk:2136,mds-vo-name=NCP-LCG2,o=grid
> GlueServiceUniqueID: pcncp21.ncp.edu.pk:2136
>
>
> Br,
> J
>
> On Tue, 6 May 2008, Adeel-ur-Rehman wrote:
>
> > Hi,
> >
> > We have upgraded our lcg-RB+glite-BDII node (glite-3.0.2, SL3.0.9) to
> > glite-WMS+glite-BDII node (glite-3.1.0, SLC 4.6). Set "WMS_host" variable
> in
> > "site-info.def" of site-BDII (CE). Also enabled the monitoring for
> glite-WMS
> > and glite-BDII in the GOCDB but GSTAT is not showing any WMS/BDII node
> being
> > monitored in our site.
> >
> > The installed rpms for WMS on our host are:
> >
> > glite-wms-ism-3.1.15-2.slc4
> > glite-wms-helper-3.1.17-7.slc4
> > glite-wms-jobsubmission-3.1.9-2.slc4
> > glite-wms-common-3.1.19-3.slc4
> > glite-wms-checkpointing-3.1.2-3.slc4
> > glite-wms-thirdparty-bypass-3.1.3-3.slc4
> > glite-wms-manager-3.1.30-1.slc4
> > glite-wms-classad_plugin-3.1.8-2.slc4
> > glite-wms-partitioner-3.1.2-2.slc4
> > glite-wms-purger-3.1.8-3.slc4
> > glite-wms-brokerinfo-3.1.10-1.slc4
> > glite-wms-interactive-3.1.5-1.slc4
> > glite-wms-utils-jobid-3.1.3-1.slc4
> > glite-wms-configuration-3.1.10-1.slc4
> > glite-wms-matchmaking-3.1.5-1.slc4
> > glite-yaim-wms-4.0.1-7
> > glite-wms-utils-tls-3.1.3-1.slc4
> > glite-wms-utils-classad-3.1.6-1.slc4
> > glite-wms-wmproxy-3.1.30-4.slc4
> > glite-wms-utils-exception-3.1.3-1.slc4
> > glite-wms-broker-3.1.5-3.slc4
> >
> >
> > We have used the following command for installing the related
> meta-package:
> >
> > yum install glite-WMS glite-BDII as well as yum install cert-glite-WMS
> > glite-BDII
> >
> > The following command has been executed for configuring the node-type:
> >
> > /opt/glite/yaim/bin/yaim -c -s
> > /opt/glite/yaim/examples/siteinfo/site-info.def -n glite-WMS -n BDII_top
> as
> > well as /opt/glite/yaim/bin/yaim -c -s
> > /opt/glite/yaim/examples/siteinfo/site-info.def -n glite-WMS -n glite-BDII
> >
> > Any ideas regarding the issue??
> >
> >
> > Thanks in advance,
> >
> >
> >
> >
> >
> > -- Best Regards --
> >
> > Adeel-ur-Rehman
> >
> > NCP-LCG2
> >
> > Site-Administration Team
> >
> >
> >
> >
>
|