Hi
I am not sure where the problem is either. My guess is in YAIM, because YAIM is the thing that adds the extra slash:
On Feb 15, 2012, at 16:33 , Arnau Bria wrote:
> If I enable the VO (in group_enable) as
>
> phys.vo.ibergrid.eu
>
> /opt/glite/etc/lcg-info-dynamic-scheduler.conf generates its entry as:
>
> ibphys:/phys.vo.ibergrid.eu
>
You did not put a slash, but YAIM did.
This is one of the areas we addressed in the Operations and Tools TEG, where we talked about problems generated by coupling between pieces of middleware. This piece of YAIM code is coupling user & group creation on the machine, generation of the static LDIF file which determines what the BDII and GIP will be publishing, ACLs on queues in torque, and configuration of the dynamic scheduler program, so it's not easy to get right.
The documentation on how it is supposed to work is provided as part of the RPM so it is installed on all glite and lcg CEs. I don't know whether the explanation in the doc is unclear, or people do not read the (entire) doc (it is quite short), so they misunderstand what the conf file is doing and get it wrong. It happens quite often, unfortunately. The error of mapping the same unix group to two different external identifiers I've seen several times before.
JT
|