Pptransfer fails: error in file IO (code 11)

Dear NCAS Helpdesk,

For one of my suites, pptransfer frequently fails (about 1/12 months) with the error code below. When I retrigger pptransfer it works fine, so this isn’t a big issue, but do you have any idea why this might be happening as it would be convenient to not have to retrigger pptransfer tasks often?

rsync: write failed on “/gws/nopw/j04/bas_palaeoclim/rachel/ARCHER2_archive/u-cl809/18720601T0000Z/cl809a.p718720611.pp”: Input/output error (5)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]

[WARN] Transfer command failed: rsync -av --stats --rsync-path=“mkdir -p /gws/nopw/j04/bas_palaeoclim/rachel/ARCHER2_archive/u-cl809/18720601T0000Z && rsync” /work/n02/n02/radiam24/archive/u-cl809/18720601T0000Z/ hpxfer1.jasmin.ac.uk:/gws/nopw/j04/bas_palaeoclim/rachel/ARCHER2_archive/u-cl809/18720601T0000Z
[ERROR] transfer.py: Unknown Error - Return Code=11
[FAIL] Command Terminated
[FAIL] Terminating PostProc…
[FAIL] transfer.py <<'STDIN
**[FAIL] **
[FAIL] ‘STDIN’ # return-code=1
2022-03-07T19:15:02Z CRITICAL - failed/EXIT

Best wishes,


Hi Rachel,

It’s difficult to say without seeing the error logs and even that might not help, it could be for any number of reasons; GWS disk full, intermittent general connection or JASMIN issue, etc.

You could try adding the following to the [[PPTRANSFER]] section so that it automatically tries again a couple of times on failure to save having to do it manually.

        execution retry delays = 2*PT10M



Thanks, I’ll try that.