On Fri, 24 Jun 2005, Massimo Biasotto wrote:
> [log in to unmask] wrote:
>
> > What do you have in /etc/shift.localhosts (sic)?
> > On our testbeds we have this in it:
> >
> > ----------------------------------------
> > 137.138.
> > 128.142.
> > ----------------------------------------
> >
> > This makes both networks local as far as RFIO is concerned.
>
> With LCG-2.5.0?
>
> We have the same:
> -------------
> 192.168.
> 192.135.
> -------------
>
> and it worked before upgrading to 2.5.0. Now the WNs are unable
> to reach the SEs.
>
> I've noticed that on the WNs there are now 2 different version
> of rfio client. The old one, provided by CASTOR-client-1.7.1.5-1.longname,
> and a new one provided by DPM-client-1.3.4-1sec_sl3.
> Using the old one I can still access the rfio servers not involved
> in the 2.5.0 upgrade, but they fail with the upgraded SE.
> Using the new client commands I can't access any of my rfio servers
> outside the private network.
Somehow we did not catch that. For now I suggest you remove
DPM-client-1.3.4-1sec_sl3 from your WNs, assuming your WNs
will not yet be doing anything involving a DPM SE.
|