Opened 3 years ago

Closed 3 years ago

#2358 closed help (fixed)

Cannot run UM Nesting suite on Archer

Reported by: tstein Owned by: um_support
Component: UM Model Keywords:
Cc: Platform:
UM Version: <select version>



When I try to run my suite u-ao745 using "rose suite-run" on PUMA, I get a "fail" message (copied below).
I do not have to use my password to login to Archer, so am not sure what else could be wrong.
I have enough HPC resources on my account as well, I believe.
I have not made major changes to my suite.

Could you please let me know what else I could try?


[FAIL] ssh -oBatchMode=yes thmstein@… bash —login -c \'ROSE_VERSION=2016.11.1\ rose\ suite-run\ -v\ -v\ —name=u-ao745\ —run=run\ —remote=uuid=5630d0a4-6d16-4b44-9a77-0d444e19b8f1,root-dir=$DATADIR\' # return-code=2, stderr=
[FAIL] ————————————————————————————————————————
[FAIL] This is a private computing facility. Access to this service is limited to those
[FAIL] who have been granted access by the operating service provider on behalf of the
[FAIL] contracting authority and use is restricted to the purposes for which access was
[FAIL] granted. All access and usage are governed by the terms and conditions of access
[FAIL] agreed to by all registered users and are thus subject to the provisions of the
[FAIL] Computer Misuse Act, 1990 under which unauthorised use is a criminal offence.
[FAIL] If you are not authorised to use this service you must disconnect immediately.
[FAIL] ————————————————————————————————————————
[FAIL] [FAIL] 2018-01-10T15:25:06+0000 tar -czf log.20171214T143855Z.tar.gz log.20171214T143855Z # return-code=2, stderr=
[FAIL] [FAIL] 2018-01-10T15:25:06+0000 tar: log.20171214T143855Z.tar.gz: Cannot write: Broken pipe
[FAIL] [FAIL] 2018-01-10T15:25:06+0000 tar: Error is not recoverable: exiting now

Change History (2)

comment:1 Changed 3 years ago by grenville


Can you delete or move log.20171214T143855Z and try again?


comment:2 Changed 3 years ago by willie

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