Hi
I have solved this, I had some old globus-mds process
running.
its ok now
thanks , and sorry for the trouble
cheers
Mario
Quoting [log in to unmask]:
> On Thu, 4 Aug 2005, Mario David wrote:
>
> > Hi
> > this one is similar to Hernath's LFC globus-mds problem
> > in the CE who is suposed to be running the slapd at 2135??
> >
> > in my CE..
> >
> > [root@ce01 init.d]# /etc/init.d/globus-mds status
> > globus-mds is stopped
> > [root@ce01 init.d]# /etc/init.d/globus-mds start
> > Starting Globus MDS (gcc32dbgpthr) [ OK ]
> > [root@ce01 init.d]# /etc/init.d/globus-mds status
> > globus-mds is stopped
>
> It reports the right thing as I write this: did you change anything?
>
> > here is a problem on starting the globus-mds although it says OK
> >
> > but a ldapsearch gives (please read below this)
> >
> > [david@ui01 lcgtest]$ ldapsearch -LLL -x -H ldap://ce01.lip.pt:2135 -b
> > "mds-vo-name=local,o=grid"
> > dn: GlueSiteUniqueID=LIP-LCG2,mds-vo-name=local,o=grid
> > objectClass: GlueTop
> > objectClass: GlueSite
> > objectClass: GlueKey
> > objectClass: GlueSchemaVersion
> > GlueForeignKey: GlueSiteUniqueID=LIP-LCG2
> > GlueForeignKey: GlueClusterUniqueID=ce01.lip.pt
> > GlueForeignKey: GlueSEUniqueID=se01.lip.pt
> > GlueForeignKey: GlueSiteUniqueID=LIP-LCG2
> > GlueForeignKey: GlueClusterUniqueID=ce01.lip.pt
> > GlueForeignKey: GlueSEUniqueID=se01.lip.pt
> > GlueSchemaVersionMajor: 1
> > GlueSchemaVersionMinor: 2
> >
> > dn: GlueCEUniqueID=ce01.lip.pt:2119/jobmanager-lcgpbs-atlas,
> mds-vo-name=local
> > ,o=grid
> > o
> >
> > and a lot more, and now even a more interesting thing, since my
> > dn: GlueSiteUniqueID=LIP-LCG has missing info like siteName and other
> stuff
> > I have checked the gip, and that info is there, so
> > any hints where this piece of info is lost??
>
> Interesting... Again, the problem is gone as I write this.
> Check /var/log/messages?
>
|