Yes: this is a nasty little bug which we still have to find a way to
solve once and for all.
The infoproviders object is not automatically started when some of its
parameters are modified. You have to do this by hand on the CE node:
/etc/obj/infoproviders start
and then restart the globus-mds server with
/etc/rc.d/init.d/globus-mds restart
Emanuele
Jiri Kosina wrote:
> On Tue, 7 Oct 2003, Jiri Kosina wrote:
>
>
>>>Oops, one more thing: you are currently publishing the LCG1-1_0_0
>>>version tag instead of the one you installed, i.e. LCG1-1_0_1. Can you
>>>please change it in site-cfg.h under the SITE_EDG_VERSION tag?
>>
>>Oops, sorry, I changed it to the proper version, and regenerated new
>>profile for CE.
>>Does everything seem OK now?
>
>
> I will reply to myself: no, it doesn't. In my site-cfg.h I have changed
> SITE_EDG_VERSION to
>
> #define SITE_EDG_VERSION LCG1-1_0_1
>
> But after generating new profile with do_mkxprofd and running
> /etc/obj/updaterpms run on CE, i still get LCG1-1_0_0 using this query:
>
> ldapsearch -LLL -x -H ldap://golias25.farm.particle.cz:2135 -b
> "mds-vo-name=local,o=grid" | grep -i datagridversion
>
> Even after restarting globus-gatekeeper and globus-mds ... is there
> anything else that should be restarted to publish changes?
>
> --
> Jiri Kosina
> Institute of physics, Academy of Sciences of the Czech republic
--
/------------------- Emanuele Leonardi -------------------\
| eMail: [log in to unmask] - Tel.: +41-22-7674066 |
| IT division - Bat.31 2-012 - CERN - CH-1211 Geneva 23 |
\---------------------------------------------------------/
|