#2356 closed help (answered)

MASS archiving error

Reported by: ajd Owned by: um_support
Component: Archiving Keywords: MASS
Cc: Platform: Monsoon2
UM Version: 10.7


Good morning,

I am getting an archiving error in my N96-ORCA1 run on MonSooN (suite-id u-at491). The archiving has worked without problems so far, I have just restarted my run after it crashed for a different reason.

[WARN] moo.py: Moose Error: user-error (see Moose docs). (ReturnCode?=2) File: /home/d02/andit/cylc-run/u-at491/share/data/History_Data/NEMOhist/archive_ready/nemo_at491o_1m_18691101-18691201_grid-W.nc
[WARN] Failed to archive file: /home/d02/andit/cylc-run/u-at491/share/data/History_Data/NEMOhist/archive_ready/nemo_at491o_1m_18691101-18691201_grid-W.nc. Will try again later.
[WARN] [SUBPROCESS]: Command: moo put -f -vv /home/d02/andit/cylc-run/u-at491/share/data/History_Data/NEMOhist/archive_ready/nemo_at491o_1m_18691101-18691201_scalar.nc moose:crum/u-at491/onm.nc.file
[SUBPROCESS]: Error = 2:

put command-id=480967332 failed: (SSC_TASK_REJECTION) one or more tasks are rejected.

/home/d02/andit/cylc-run/u-at491/share/data/History_Data/NEMOhist/archive_ready/nemo_at491o_1m_18691101-18691201_scalar.nc → moose:/crum/u-at491/onm.nc.file/nemo_at491o_1m_18691101-18691201_scalar.nc: (TSSC_CONFLICT_WITH_EARLIER_COMMAND) command conflicts with another command.
Conflicting command-ids: 480933053, 480933331,

put: failed (2)

Do you know what could be causing this and how to solve it?

Many thanks,

Change History (3)

comment:1 Changed 22 months ago by ros

  • Status changed from new to pending

Hi Andrea,

I've forwarded your query on to the Met Office. You may hear from them direct otherwise I will update here when I get a reply.


comment:2 Changed 22 months ago by ros

P.S It might be worth trying again in case it was just an intermittent problem.

comment:3 Changed 22 months ago by ros

  • Keywords MASS added
  • Resolution set to answered
  • Status changed from pending to closed

Summary of response received:

A bug has been identified in the latest release that is causing commands to become stuck and they are working on a fix. Stuck commands are being periodically killed, but if required, you can also kill a command yourself by using the moo kill command (See manual for details).

Alternatively ctrl-c can also be used to kill a running MOOSE command.

Note: See TracTickets for help on using tickets.