Right, so we assume this error msg is a red herring. It's a dog trying
to find out about recent changes. eg. we now have these two files,
which appear to hold the same info...
# cat /opt//glite/etc/gip/site-urls.conf
CE ldap://fal-pygrid-18.lancs.ac.uk:2135/mds-vo-name=local,o=grid
DPM ldap://fal-pygrid-30.lancs.ac.uk:2170/mds-vo-name=resource,o=grid
# cat /opt/bdii/etc/bdii-update.conf
CE ldap://fal-pygrid-18.lancs.ac.uk:2135/mds-vo-name=local,o=grid
DPM ldap://fal-pygrid-30.lancs.ac.uk:2170/mds-vo-name=resource,o=grid
GIP file:///opt/glite/libexec/glite-info-wrapper
The above 3 queries return good info, why the bdii isn't publishing
these is the question.
Peter
2008/11/5 Yves Coppens <[log in to unmask]>:
> Hi Stephen, Peter,
>
> I've asked the same question to ROLLOUT. Felix Nikolaus Ehm replied:
>
> <--
> the message you see doesn't harm the service.
>
> The GIP and the bdii itself try to add this entry to the information
> tree. The slapadd then fails to add the second entry but will continue
> to add the rest.
>
> You should be able to do a ldapsearch to this host without problems. Is
> this the case ?
> -->
>
> So Stephen is right, but it seems we will have to live with this error
> message.
>
> Yves
>
>
> On Wed, 5 Nov 2008, Burke, S (Stephen) wrote:
>
>> Testbed Support for GridPP member institutes
>>>
>>> [mailto:[log in to unmask]] On Behalf Of Peter Love said:
>>> Only visible prob is this in /opt/bdii/var/bdii.log
>>> ==> slapadd: could not add entry dn="Mds-Vo-name=resource,o=grid"
>>> (line=4319): txn_aborted! DB_KEYEXIST: Key/data pair already exists
>>> (-30996)
>>
>> It sounds like you may be trying to run two resource bdiis on the same
>> node - how is it configured? Note that all bdiis now have a resource
>> bdii to publish themselves, which might be the root of the problem.
>>
>> Stephen
>>
>
|