Changes between Initial Version and Version 1 of Ticket #2467, comment 1


Ignore:
Timestamp:
15/05/18 12:16:34 (18 months ago)
Author:
ros
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2467, comment 1

    initial v1  
    33When the `nemo_cice.20100101T0000Z` was submitted on Friday it was submitted to `login2.archer.ac.uk`. 
    44 
    5 Whilst it was running `login2.archer.ac.uk` developed problems.  If you look in the `log/suite/log` file you will see that it is failing to login to that particular login node to check on the task's status.  Cylc then will continue to check on the tasks status through `login2.archer.ac.uk` even when you stopped and restarted the suite. Since it can't update the status it leaves it in the last known state which is "submitted". 
     5Whilst it was running `login2.archer.ac.uk` developed problems.  If you look in the `log/suite/log` file you will see that it is failing to login to that particular login node to check on the task's status.  Cylc then will continue to check on the task's status through `login2.archer.ac.uk` even when you stopped and restarted the suite. Since it can't update the status it leaves it in the last known state which is "submitted". 
    66 
    77In order to get the suite going again, you will need to manually check that the `nemo_cice.20100101T0000Z` task succeeeded by looking at the log files on ARCHER and assuming it has then manually change the status of the task in the Cylc GUI to `succeeded` to allow the suite to continue.