Opened 5 months ago

Closed 3 months ago

#3430 closed help (fixed)

PPTransfer Failed

Reported by: dgalea Owned by: um_support
Component: SSH Keywords:
Cc: Platform: ARCHER
UM Version: 11.0



I am running a climate run of suite u-bz203 but the PPTransfer task to transfer data to JASMIN is failing.

The job.err file shows the following:

[WARN] skip missing optional source: namelist:moose_arch
[WARN] skip missing optional source: namelist:moose_arch
[WARN]  [SUBPROCESS]: Command: rsync -av --stats --rsync-path=mkdir -p /group_workspaces/jasmin4/hiresgw/dg/archer_transfers/u-bz203/19970501T0000Z && rsync /work/n02/n02/dgalea/archive/u-bz203/19970501T0000Z/
[SUBPROCESS]: Error = 255:

            Access to this system is monitored and restricted to
            authorised users.   If you do not have authorisation
            to use  this system,  you should not  proceed beyond
            this point and should disconnect immediately.

            Unauthorised use could lead to prosecution.

    (See also -

Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(641) [sender=3.0.4]

[WARN]  Transfer command failed: rsync -av --stats --rsync-path="mkdir -p /group_workspaces/jasmin4/hiresgw/dg/archer_transfers/u-bz203/19970501T0000Z && rsync" /work/n02/n02/dgalea/archive/u-bz203/19970501T0000Z/
[ERROR] Unknown Error - Return Code=255
[FAIL]  Command Terminated
[FAIL] Terminating PostProc...
[FAIL] # return-code=1
Received signal ERR
cylc (scheduler - 2020-11-25T09:26:52Z): CRITICAL Task job script received signal ERR at 2020-11-25T09:26:52Z
cylc (scheduler - 2020-11-25T09:26:52Z): CRITICAL failed at 2020-11-25T09:26:52Z

It seems that ARCHER is having trouble connecting to JASMIN to perform the data transfer but I have managed to do so manually without a problem. Could you help me figure this out please?


Change History (6)

comment:1 Changed 5 months ago by dgalea


just checking if you've had some time to have a look at this.


comment:2 Changed 5 months ago by grenville


Please allow us read access to your PUMA space


comment:3 Changed 5 months ago by dgalea

Sorry, I thought I had already given you read rights. Should be fixed now.

comment:4 Changed 5 months ago by grenville


Did you check that you can ssh to xfer1 from espp1 and espp2?


comment:5 Changed 5 months ago by dgalea


it turns out the ssh-agent was turned off on espp1 and espp2. I've restarted them and everything seems to be ok now. Thanks for your help.


comment:6 Changed 3 months ago by ros

  • Component changed from UM Model to SSH
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.