# Re: Postproc submit-failed

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/re-postproc-submit-failed/2079>\
**Category:** Uncategorized\
**Tags:** ARCHER2\
**Created:** [7 May 2026 20:17 UTC](https://cms-helpdesk.ncas.ac.uk/t/re-postproc-submit-failed/2079 "2026-05-07T20:17:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [7 May 2026 20:17 UTC](https://cms-helpdesk.ncas.ac.uk/t/re-postproc-submit-failed/2079/1 "2026-05-07T20:17:59Z")

</div>

Hi Leif,

Looking at the logs I can see that atmos\_main has been hit by the same problem on numerous occasions as well. e.g.  
You may not be aware of it because atmos\_main task has automatic retries on submit-failure.

20030801T0000Z/atmos\_main:  
01/ 02/ 03/ 04/ 05/ NN@

When you run

rose host-select archer2

on the puma2 command line does it select an archer2 node ok. Try multiple times.

At the moment ln01 is down for maintenance so if it picks that node it should try another. e..g

ros@puma2$ rose host-select archer2  
[WARN] ln01: (ssh failed)  
ln04

ln02, ln03 and ln04 should all work. Make sure you can ssh into these 3 nodes ok.

Is this something that has only started happening since PUMA2 was rebooted last week?

Regards,  
Ros

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/1fd2411499ffcbc299fe756cd5cdf26e44956558.png) [@system](https://cms-helpdesk.ncas.ac.uk/u/system)\
**Post date:** [6 June 2026 20:18 UTC](https://cms-helpdesk.ncas.ac.uk/t/re-postproc-submit-failed/2079/2 "2026-06-06T20:18:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
