On Fri, 2005-12-09 at 10:52, Graeme Stewart wrote:
> > ok, with chmod 775 and files owned by dpmmgr on the pool node, lcg-cp of
> > atlas data from the pool node works again (it fails with 770).
>
> OK, so better ;-)
could one get around this e.g. by adding user dpmmgr to the groups of
each VO? What do other DPM sites have? It's strange that the head node
works fine with 770, only the pool node needs 775
> > Besides this I have established that:
> > - from our UI, srmcp of atlas data from the pool node fails in both the
> > 770 and 775 cases
>
> srmcp using what SURL? The dpns nameserver entry created by the migration
> script, I presume? The olf sfn:// SURLs I would not expect to be accessible
> via the SRM.
>
> > - from lxplus, it works instead, in both 770 and 775 cases
>
> That's weird. Could you do it with -debug in both cases and look for any
> differences in the SURL->TURL mappings. And what the error message is on the
> UI.
I use this command:
srmcp -debug=true \
srm://pc55.hep.ucl.ac.uk:8443/dpm/hep.ucl.ac.uk/home/atlas/TESTDIR/TestFile file:////tmp/MyLocalFile.txt
the SURL->TURL mapping is correct in both cases. But from our UI, it
fails with the following error:
GridftpClient: gridFtpWrite: starting the transfer in emode from
pc55:/storage/lcgatlas/2005-12-06/TestFile.932.0
org.globus.ftp.exception.ServerException: Server refused performing the
request. Custom message: (error code 1) [Nested exception message:
Custom message: Unexpected reply: 425 Can't open data connection.
data_connect_failed() failed: a system call failed (No route to
host).]. Nested exception is
org.globus.ftp.exception.UnexpectedReplyCodeException: Custom message:
Unexpected reply: 425 Can't open data connection. data_connect_failed()
failed: a system call failed (No route to host).
I suppose it's a firewall issue. Then again, srmcp worked at one point
from our UI!
> > Is there a recommendation for the ports needed on
> > the DPM pool node?
> >
> Internally between the DPM nodes open everything. Externally, open 8443, 2811
> and GLOBUS_PORT_RANGE (20000-25000) for gridftp/srm data transfers. Open 5010
> and 5015 to enable DPNS and DPM queries and commands, respectively (I'd
> recommend this). I would not open 5001 - that's for rfio, and I would
> restrict that to the DPM nodes themselves. And to get it fully working you
> need the dynamic rfio ports open too (everything > 1024 I think).
thanks, implementing these changes on the pool node, we pass again the
SFT!
> Did you do anything about remounting the /storage/atlas partition yet?
I'll do this next week, I wanted to make sure that the DPM is fully
functional before doing that. I'll keep you posted.
cheers,
gianfranco
|