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
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.
Regards,
Jan
>
> -----Original Message-----
> From: LHC Computer Grid - Rollout on behalf of Emanouil Atanassov
> Sent: Mon 8/1/2005 12:54 PM
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] BDII problems? -- READ THIS
>
> Hi,
>
> Are those sites still in lcg2-all-sites.conf? Should they be there?
> I am getting segmentation fault now.
> Using a doctored lcg2-all-sites.conf, it works.
>
> Emanouil Atanassov
> [log in to unmask]
> EGEE SEE ROC
>
>
>>This is a multi-part message in MIME format.
>>--------------030801080908040706030307
>>Content-Type: text/plain; charset=us-ascii; format=flowed
>>Content-Transfer-Encoding: 7bit
>>
>>Maarten Litmaath wrote:
>>
>>
>>>Emanouil Atanassov wrote:
>>>
>>>
>>>> [...]
>>>>
>>>>I think Replica Management worked a day ago, so what has happened now?
>>>>Some site polluting the BDIIs?
>>>
>>>
>>>In a sense; see below.
>>>
>>>
>>>>Something with the new glue schema?
>>>
>>>
>>>No. There has been the following bug in GFAL since a long time:
>>>if a record in the information system contains a "GlueServiceType",
>>>but _not_ a "GlueServiceAccessPointURL", or vice versa, the routine
>>>free() is called with an uninitialized variable as argument.
>>>Such can lead to an infinite loop or a segmentation fault.
>>>This bug has been fixed for LCG-2_6_0.
>>>
>>>What we will do now is search for the "bad" entry and either remove
>>>it from the BDII or preferrably have it "fixed". More news later.
>>
>>OK, I found the entries that gave problems and removed their sites
>>from lcg-bdii.cern.ch:
>>
>>#TU-Kosice ldap://ce.grid.tuke.sk:2170/Mds-Vo-name=TU-Kosice,o=grid
>>#AEGIS01-PHY-SCL ldap://ce.phy.bg.ac.yu:2170/mds-vo-name=AEGIS01-PHY-SCL,o=grid
>>
>>Everybody, please ensure your site is not publishing entries that
>>only have either "GlueServiceType" or "GlueServiceAccessPointURL".
>>
>>This probably means hand-editing /opt/lcg/var/gip/lcg-info-static.ldif
>>on Resource Brokers, GridICE nodes, MyProxy servers, ...
>>Just add the missing entry with some dummy value.
>>
>>I have attached a script you can run to test your site BDII as follows:
>>
>> ldapsearch -x -h your_bdii:2170 -b o=grid | perl bad-dn.pl
>>
>>The output should be empty.
>>
>>--------------030801080908040706030307
>>Content-Type: text/plain;
>> name="bad-dn.pl"
>>Content-Transfer-Encoding: 7bit
>>Content-Disposition: inline;
>> filename="bad-dn.pl"
>>
>>#!/usr/bin/env perl
>>
>>use strict;
>>
>>$/ = "";
>>
>>while (<>) {
>> if (/GlueServiceType/) {
>> print unless /GlueServiceAccessPointURL/;
>> next;
>> }
>> if (/GlueServiceAccessPointURL/) {
>> print unless /GlueServiceType/;
>> next;
>> }
>>}
>>
>>--------------030801080908040706030307--
>
>
>
--
Jan Astalos
Institute of Informatics, Slovak Academy of Sciences
|