Tools/Manuals/TS28

From EGIWiki
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators

Contents



Back to Troubleshooting Guide


Transport endpoint is not connected

Full message

$ lcg-cp --vo atlas srm://some-SE.some-domain/dpm/some-domain/home/atlas/... file:/tmp/...
lcg_cp: Transport endpoint is not connected

The error can also occur for lcg-cr, lcg-rep, lcg-del, ...

Diagnosis

The error message implies that the (SRM or gridftp) server closed the connection without further details getting propagated to the user. Like in many cases, one can learn more by trying a globus-url-copy directly:

$ globus-url-copy file:/etc/group gsiftp://some-SE.some-domain/tmp/test.$$
error: the server sent an error response: 530 530 No local mapping for Globus ID

When the user does appear in the grid-mapfile, it is likely that all the pool accounts for the VO are taken. In that case the solution is to so add more pool accounts and create corresponding empty files in /etc/grid-security/gridmapdir. Otherwise see 530 530 No local mapping for Globus ID for other explanations.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export