Hi
answer is yes, snipet from a central bdii
dn: GlueServiceUniqueID=http://lfc01.lip.pt:8085/,mds-vo-name=LIP-LCG2,mds-vo-
name=local,o=grid
objectClass: GlueTop
objectClass: GlueService
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueServiceUniqueID: http://lfc01.lip.pt:8085/
GlueServiceName: LIP-LCG2-lfc-dli
GlueServiceType: data-location-interface
GlueServiceVersion: 1
GlueServiceEndpoint: http://lfc01.lip.pt:8085/
GlueServiceURI: http://lfc01.lip.pt:8085/
GlueServiceAccessPointURL: http://lfc01.lip.pt:8085/
GlueServiceStatus: running
GlueServiceOwner: swetest
GlueServiceAccessControlRule: swetest
GlueForeignKey: GlueSiteUniqueID=LIP-LCG2
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 2
dn: GlueServiceUniqueID=lfc01.lip.pt,mds-vo-name=LIP-LCG2,mds-vo-name=local,o=
grid
objectClass: GlueTop
objectClass: GlueService
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueServiceUniqueID: lfc01.lip.pt
GlueServiceName: LIP-LCG2-lfc
GlueServiceType: lcg-file-catalog
GlueServiceVersion: 1
GlueServiceEndpoint: lfc01.lip.pt
GlueServiceURI: lfc01.lip.pt
GlueServiceAccessPointURL: lfc01.lip.pt
GlueServiceStatus: running
GlueServiceOwner: atlas
GlueServiceOwner: cms
GlueServiceOwner: dteam
Glu...... etc
did you check if you have the ca rpm installed
because at least the lcg-LFC_mysql does not depend and does not
install the lcg-CA
Quoting Hernath Szabolcs <[log in to unmask]>:
> Hi Mario,
>
> On Thu, 4 Aug 2005, Mario David wrote:
>
> > Hi
> >
> > for LFC gip publishing I had the same problem, since I am
> > running the central catalog for a local VO, so
> > I have configured a LFC "central for all vo'sI support
> > and after I take out manually from the
> > lcg-info-generic.conf
> > lcg-info-static.ldif
> >
> > the ones I do not support centrally
> I did the same. That's why I said it isn't a serious problem, just minor
> nuisance...the real problem is that globus-mds does not publish anything,
> it just dies upon startup. All I get from ldapsearch is:
>
> ldap_bind: Can't contact LDAP server
>
> There is no slapd process running on that node. I have no idea about the
> cause of the problem. Could you check please whether your LFC actually
> publishes that info? Thanks,
> Cheers
>
> Szabolcs
>
>
>
>
>
> > finally do you have installed in the LFC
> > rpm -qa|grep ca_ ???
>
>
>
>
>
>
> >
> > cheers
> >
> > Mario
> >
> >
> > Quoting Hernath Szabolcs <[log in to unmask]>:
> >
> >> Hi Fellow Upgraders,
> >>
> >> I found two problems while upgrading our central LFC server for a local
> >> VO:
> >>
> >> 1. If you specify your service type as 'central', yaim will configure
> the
> >> lfc-dli to act as a central catalogue for *all* VOs that you specify in
> >> site-info.def. This is clearly wrong, it should definitely be only a
> small
> >> subset of your supported VOs, usually just one of them. This is only a
> >> minor nuisance.
> >>
> >> 2. globus-mds does not work. On startup it will say [ OK ], but then
> >> just dies right after that. I have no clue what could be wrong.
> >> Any ideas?
> >>
> >> Szabolcs
> >>
> >
>
|