Moving clusters
From Molecular Modeling Wiki
(Difference between revisions)
| (16 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | == | + | == Actual status (last update: Friday, September 19) == |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
; ''centrum'' | ; ''centrum'' | ||
| Line 30: | Line 5: | ||
; ''carol'' | ; ''carol'' | ||
| - | : <font color=" | + | : <font color="green">Server is up and running.</font> |
; ''marge'' | ; ''marge'' | ||
| - | : <font color=" | + | : <font color="green">Server is up and running.</font> |
; ''teogate'' | ; ''teogate'' | ||
| - | : <font color=" | + | : <font color="green">Server is up and running.</font> |
| + | |||
| + | ; ''humboldt'' | ||
| + | : <font color="green">Server is up and running.</font> | ||
| + | |||
| + | ; ''camel'' | ||
| + | : <font color="green">Server is up and running.</font> | ||
; althea | ; althea | ||
| Line 47: | Line 28: | ||
: <font color="green">Cluster is up and running.</font> | : <font color="green">Cluster is up and running.</font> | ||
| - | ; francium | + | ; francium |
| - | : <font color=" | + | : <font color="green">Cluster is up and running.</font> |
| - | + | ||
| - | + | ||
| - | + | ||
; iridium | ; iridium | ||
| Line 57: | Line 35: | ||
; cobalt | ; cobalt | ||
| - | : <font color=" | + | : <font color="green">Cluster is up and running. Some older nodes are broken and will not be repaired.</font> |
; argon | ; argon | ||
| - | : <font color="green">Cluster is up and running. | + | : <font color="green">Cluster is up and running. All nodes have been repaired.</font> |
; krypton | ; krypton | ||
| - | : <font color="green">Cluster is up and running. | + | : <font color="green">Cluster is up and running. All nodes have been repaired.</font> |
; radon | ; radon | ||
| - | : <font color="green">Cluster is up and running. | + | : <font color="green">Cluster is up and running. All nodes have been repaired.</font> |
; palladium | ; palladium | ||
| - | : <font color=" | + | : <font color="green">Cluster is up and running. Some older nodes are broken and will not be repaired.</font> |
| Line 80: | Line 58: | ||
; niob | ; niob | ||
: <font color="black">Discontinued.</font> | : <font color="black">Discontinued.</font> | ||
| + | |||
| + | |||
| + | == Warning == | ||
| + | |||
| + | Due to the security problems, the SSH server keys will be regenerated on most cluster servers. This means that you can receive a warning similar to the following when trying to log in for the first time: | ||
| + | |||
| + | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ | ||
| + | @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ | ||
| + | @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ | ||
| + | IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! | ||
| + | Someone could be eavesdropping on you right now (man-in-the-middle attack)! | ||
| + | It is also possible that the RSA host key has just been changed. | ||
| + | The fingerprint for the RSA key sent by the remote host is | ||
| + | 9a:a3:68:49:29:f6:a0:f4:c1:64:a0:fd:98:67:b2:67. | ||
| + | Please contact your system administrator. | ||
| + | Add correct host key in /root/.ssh/known_hosts to get rid of this message. | ||
| + | Offending key in /root/.ssh/known_hosts:53 | ||
| + | RSA host key for iridium has changed and you have requested strict checking. | ||
| + | Host key verification failed. | ||
| + | |||
| + | To get rid of this warning and get access to the cluster, do the following: | ||
| + | # Find a row that starts with ''Offending key ... '' in the text of the warning and remember line number after a colon (53 in the above example). | ||
| + | # Open the ''~/.ssh/known_hosts'' file and delete the line which number was mentioned in the warning (in '''vi''', press <5><3><shift-G><d><d> in case of the above example; replace numbers according to your needs). | ||
| + | # Save the file and try to connect to the cluster. | ||
| + | # If the connection fails again with the same or similar warning, repeat all steps. | ||
Latest revision as of 08:31, 19 September 2008
Actual status (last update: Friday, September 19)
- centrum
- Server is up and running.
- carol
- Server is up and running.
- marge
- Server is up and running.
- teogate
- Server is up and running.
- humboldt
- Server is up and running.
- camel
- Server is up and running.
- althea
- Server is up and running.
- lithium
- Cluster is up and running, except for clients l07 and l22-l25 that need some repair (l22-l24 are probably ok, but have to be tested, l25's memory module failed so it is in a service).
- helium
- Cluster is up and running.
- francium
- Cluster is up and running.
- iridium
- Cluster is up and running. Enable queues as needed.
- cobalt
- Cluster is up and running. Some older nodes are broken and will not be repaired.
- argon
- Cluster is up and running. All nodes have been repaired.
- krypton
- Cluster is up and running. All nodes have been repaired.
- radon
- Cluster is up and running. All nodes have been repaired.
- palladium
- Cluster is up and running. Some older nodes are broken and will not be repaired.
- vanad
- Discontinued.
- titanium
- Discontinued.
- niob
- Discontinued.
Warning
Due to the security problems, the SSH server keys will be regenerated on most cluster servers. This means that you can receive a warning similar to the following when trying to log in for the first time:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 9a:a3:68:49:29:f6:a0:f4:c1:64:a0:fd:98:67:b2:67. Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message. Offending key in /root/.ssh/known_hosts:53 RSA host key for iridium has changed and you have requested strict checking. Host key verification failed.
To get rid of this warning and get access to the cluster, do the following:
- Find a row that starts with Offending key ... in the text of the warning and remember line number after a colon (53 in the above example).
- Open the ~/.ssh/known_hosts file and delete the line which number was mentioned in the warning (in vi, press <5><3><shift-G><d><d> in case of the above example; replace numbers according to your needs).
- Save the file and try to connect to the cluster.
- If the connection fails again with the same or similar warning, repeat all steps.
