Hi,
This problem that Steve Traylen cured by unsetting GLOBUS_TCP_PORT_RANGE
is a known bug in globus_io
(http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=1851). We have seen
from tcp_dump output that when, for example GLOBUS_TCP_PORT_RANGE is
20000-25000, globus_io always starts using port 20000. On routers using
ACLs this can cause the problems we have seen. Unsetting
GLOBUS_TCP_PORT_RANGE causes globus_io to use any random unprivileged
port which "cures" the problem. I suppose that since this bug was
submitted by the VDT people it will be patched in the future (I hope).
Cheers,
Ron Trompert
<[log in to unmask]>
> -----Original Message-----
> From: LHC Computer Grid - Rollout
> [mailto:[log in to unmask]] On Behalf Of Ron Trompert
> Sent: woensdag 1 september 2004 9:27
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] gridftp problem II
>
>
> Hi Maarten,
>
> Thanks for your prompt reply. I think that it is indeed the
> "globus-url-copy problem". I did 5 globus-url-copies in a row in a
> script and got the same problem. We are going to change the
> settings on
> the router.
>
> Cheers,
>
> Ron
> <[log in to unmask]>
>
> > -----Original Message-----
> > From: LHC Computer Grid - Rollout
> > [mailto:[log in to unmask]] On Behalf Of Maarten
> > Litmaath, CERN
> > Sent: dinsdag 31 augustus 2004 22:33
> > To: [log in to unmask]
> > Subject: Re: [LCG-ROLLOUT] gridftp problem II
> >
> >
> > On Tue, 31 Aug 2004, Ron Trompert wrote:
> >
> > > By the way, globus-url-copies work like a charm. We do have
> > ACL's on the
> > > router connecting the machine to the rest of the world
> > > but from the tcpdump output you can see that the server
> > connects to the
> > > client at port 20000 which is in the
> GLOBUS_TCP_PORT_RANGE which is
> > > opened.
> >
> > Yes, but maybe the router does not allow the same hosts and
> > ports to be
> > immediately reused for a new connection. See this thread on
> > the rollout
> > list: "problem with globus-url-copy".
> > In this case it is strange that it would only affect
> lcg-cp, but maybe
> > Globus is not used exactly the same way as in globus-url-copy.
> > Can you try if unsetting GLOBUS_TCP_PORT_RANGE on the UI helps?
> >
>
|