97 | | == Troubleshooting common errors == |
98 | | |
99 | | === rose host-select archer error === |
100 | | |
101 | | If your PUMA and ARCHER usernames are different you may see the following when submitting a suite: |
102 | | |
103 | | {{{ |
104 | | RosePopenError?: bash -ec H=$(rose\host-select\archer);\echo\$H # return-code=1, stderr= |
105 | | [WARN] login5.archer.ac.uk: (ssh failed) |
106 | | [WARN] login7.archer.ac.uk: (ssh failed) |
107 | | ….. |
108 | | [FAIL] No hosts selected |
109 | | }}} |
110 | | |
111 | | This is because rose is running a command called `rose host-select` to chose a machine to submit the suite to. The Met Office use this to choose the least loaded machine; and we use it for ARCHER to mitigate against situations where some of the ARCHER login nodes are down. |
112 | | |
113 | | To get this to work you will need to follow 2 steps: |
114 | | |
115 | | i) Configure your SSH settings so that it knows your ARCHER username. Open the file `~/.ssh/config` and add the following lines to the top of the file, replacing `<archer-username>` with your username: |
| 97 | === Setting up rose host-select archer === |
| 98 | |
| 99 | Some suites use the command `rose host-select` to choose a machine to submit the suite to. This can be used to select the least-loaded server, but for ARCHER we use this to mitigate against times when some of the ARCHER login nodes are down. |
| 100 | |
| 101 | To get `rose host-select archer` to work there is some setup required. (Note: You can just replace the `rose host-select` line in your `suite.rc` or `site/archer.rc` file with the name of the host, but you won't get the benefits.) |
| 102 | |
| 103 | i) If your PUMA and ARCHER usernames are the same skip to step ii). Otherwise you will need to configure your SSH settings so that it knows your ARCHER username. Open the file `~/.ssh/config` and add the following lines, replacing `<archer-username>` with your username: |