...
| Column |
|---|
|
| Note |
|---|
| title | Always close the remote session |
|---|
| Always follow the exit process described above. If you don't and simply close your VS Code window, then some server-side components of VS Code will continue to run remotely. |
|
Kill the leftover orphan processes in the login nodes
...
If users are performing a regular check for orphan processes, unfortunately, then they will need to traverse along all access the login and data-mover nodes individually and check for orphan processes on each of them. Currently there may be 12 login nodes available to users going from setonix-01 to setonix-12.
At any given time, the set of login and data-mover nodes that are accessible may be determined by running the following commands from a terminal session on whichever login or data-mover node you have logged into
| Code Block |
|---|
username@setonix-06:~> dig @150.229.2.5 setonix.pawsey.org.au +noall +answer
setonix.pawsey.org.au. 3600 IN A 146.118.12.26
setonix.pawsey.org.au. 3600 IN A 146.118.12.27
setonix.pawsey.org.au. 3600 IN A 146.118.12.22
username@setonix-06:~>
username@setonix-06:~> nslookup 146.118.12.26 150.229.2.5
26.12.118.146.in-addr.arpa name = setonix-05.pawsey.org.au.
username@setonix-06:~>
username@setonix-06:~> nslookup 146.118.12.27 150.229.2.5
27.12.118.146.in-addr.arpa name = setonix-06.pawsey.org.au.
username@setonix-06:~>
username@setonix-06:~> nslookup 146.118.12.22 150.229.2.5
22.12.118.146.in-addr.arpa name = setonix-01.pawsey.org.au.
username@setonix-06:~> |
Here, having logged into setonix-06, we obtain the list of IP addresses for the currently accessible login nodes, and then convert those IP addresses back into the individual nodes names.
in this instance, we can see that we should also check for leftover processe on setonix-01 and setonix-05
The following example shows the commands to obtain the list of names for the currently available data-mover nodes, having logged into setonix-dm01
| Code Block |
|---|
username@setonix-dm01:~> dig @150.229.2.5 data-mover.pawsey.org.au +noall +answer
data-mover.pawsey.org.au. 3600 IN A 146.118.74.161
data-mover.pawsey.org.au. 3600 IN A 146.118.74.160
data-mover.pawsey.org.au. 3600 IN A 146.118.74.163
data-mover.pawsey.org.au. 3600 IN A 146.118.74.162
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.161 150.229.2.5
26.12.118.146.in-addr.arpa name = setonix-dm02.pawsey.org.au.
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.160 150.229.2.5
27.12.118.146.in-addr.arpa name = setonix-dm01.pawsey.org.au.
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.163 150.229.2.5
22.12.118.146.in-addr.arpa name = setonix-dm04.pawsey.org.au.
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.162 150.229.2.5
22.12.118.146.in-addr.arpa name = setonix-dm03.pawsey.org.au.
username@setonix-dm01:~> |
| Column |
|---|
|
| Note |
|---|
| title | Only connect to specific login nodes to perform killing of orphan processes |
|---|
| Only use direct connection to specific login nodes when performing cleaning of orphan processes. For the rest of your connections users should be using the generic name setonix.pawsey.org.au, which provides access assigning the connection to different login nodes in a round robin fashion. This allows for better load balancing of resources among all users. Furthermore, the use of the generic name provides a more reliable access as it can provide service to users on active login nodes while some specific login nodes may have been taken down by Pawsey staff for technical reasons. |
|
...