Hi Dominic,
I looked at it with Matt last week and there is no apparent reason why
the current configuration shouldn't work. The SE BDII is visible from
the site BDII machine and a plain ldapsearch works.
The only suspicious thing that came out is that 'SE1: no such object'
found in your bdii.log which could be due to some weird character in
your site-info.def which you don't seem to have.
I couldn't find anything meaningful on google apart from the fact that
clearly you are trying to publish something that is not foreseen in the
schema.
If it was me in your place I'd try to
1) look if an SE1 appears anywhere in the bdii files of both site BDII
and DPM.
2) rename the URL BDII_SE_URL and put simply SE in your BDII_REGIONS
and reconfigure the bdii and see if SE1 is replaced by SE or if that
line disappears.
3) I'd run the configuration with additional printout from me to see if
I can pinpoint where it all goes wrong.
Other than that I suggested Matt to open a ticket for the BDII people in
GGUS. You should send them the log files as well. Tell them what version
of yaim, glue and bdii rpms you have on all your machines and the
site-info.def.
cheers
alessandra
Dominic G. Wilson wrote:
> Hi all
>
> Ok I'm getting sick of not having a clue what is going wrong here and
> banging my head against the desk. So far all I can understand is that
> all the processes are running properly {I guessing not}. We are passing
> CE information but not SE information.
>
> This would seam to me there is a config problem somewhere between the
> SE, the site BDii and the rest of the world. I will have attached our
> site-info.def and will list all the yaim options used on the nodes. in
> the hope that someone can see something blindingly wrong.
>
>
> On the SE
> SE_dpm_mysql
>
> On the CE
> CE
>
> On site BDii
> BDII_site
>
> Any help would be greatly received.
>
> Dominic
>
> --
> Corporate Information & Computing Services, University of Sheffield
> 285 Glossop Road, Sheffield, United Kingdom S10 2HB
> Voice: +44 114 22 23049 E-Mail: [log in to unmask]
>
>
>
>
