 |
 |
On Mon, 1 Aug 2005, Jan Astalos wrote: > Maarten Litmaath wrote: > > Indeed, you need to switch off the auto-update in bdii.conf > > and edit the problem sites out of bdii-update.conf. > > GlueServiceAccessPointURL is missing for gridice service in YAIM > (/opt/lcg/yaim/functions/config_gip). After fixing the script and > reconfiguring, BDII is publishing: > > # ce.grid.tuke.sk:2136, TU-Kosice, grid > dn: GlueServiceUniqueID=ce.grid.tuke.sk:2136,mds-vo-name=TU-Kosice,o=grid > objectClass: GlueTop > objectClass: GlueService > objectClass: GlueKey > objectClass: GlueSchemaVersion > GlueServiceUniqueID: ce.grid.tuke.sk:2136 > GlueServiceName: TU-Kosice-gridice > GlueServiceType: gridice > GlueServiceVersion: 1.1 > GlueServiceEndpoint: ldap://ce.grid.tuke.sk:2136/mds-vo-name=local,o=grid > GlueServiceAccessPointURL: > ldap://ce.grid.tuke.sk:2136/mds-vo-name=local,o=gri > d > GlueServiceStatus: OK > GlueServiceStatusInfo: No Problems > ... > > Is it OK or GlueServiceType must be immediately after > GlueServiceAccessPointURL ? It is so in lcg-info-generic.conf but in The order does not matter. The new lcg-info-templates rpm sets the value to the string "not_used" (it just has to be a non-empty string). > lcg-info-static.ldif it got shuffled. Or do I have to remove gridice > service completely ? > > 2170 port is firewalled at TU-Kosice until the issue will be resolved. That was a good idea! Since your data is fine now, you can unblock the port; I already put you in lcg-bdii.cern.ch again.