 |
 |
Hi, I found the cause of my problems, and I think there is a 'bug' in the documentation that led to this. In short: globus-mds did not start, because I was missing some packages. The relevant metapackage has been renamed from lcg-LFC-mysql (2_4_0) to lcg-LFC_mysql (2_6_0). As I already had an LFC service installed, a simple 'apt-get upgrade' did not pull the new packages. This sort of problem is indicated in the upgrade notes for the classic SE and the BDII, but not for LFC. So, if you are *upgrading* an LFC node, you have to issue rpm -e --nodeps lcg-LFC-mysql apt-get install lcg-LFC_mysql before 'apt-get upgrade', and then follow with yaim config as usual. There is, however, a remaining problem with the configuration of gip. As said earlier, yaim will happily configure a central LFC service for all the VOs you declared in site-info.def, which is not what you want. Just like Mario, I had to change lcg-info-generic.conf to exclude the unnecessary VOs from the 'central service' entry. But which one is it? You have two entries: 1. 'dn:GlueServiceUniqueID=http://grid155.kfki.hu:8085/\ ,mds-vo-name=BUDAPEST,o=grid' with 'GlueServiceType: data-location-interface' 2. 'dn: GlueServiceUniqueID=grid155.kfki.hu,mds-vo-name=BUDAPEST,o=grid' with 'GlueServiceType: lcg-file-catalog' Throughout the LFC-Administrator-Guide-1.3.5.pdf document (linked from the GocWIKI Administration FAQ) it is emphasized that 'dli' is the thing for the central service, so you might guess that you have to change entry #1. On the other hand, the same document offers a sample lcg-info-generic.conf with 'GlueServiceType: lcg-file-catalog' for the central service and 'GlueServiceType: local-lcg-file-catalog' for the local catalogue. This would make you want to change entry #2. For the time being, I just copied Mario's solution, which is probably right, but the documentation should definitely be updated :-). And a final question: is it necessary to open port 8085 for the central service to work? The documentation only mentions port 5010. Happy Upgrading, Szabolcs On Thu, 4 Aug 2005, Mario David wrote: > 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 >>>> >>> >> >