Moving clusters

From Molecular Modeling Wiki

(Difference between revisions)

Jump to: navigation, search

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.

@@ Line 1: / Line 1: @@
-== Warning ==
+== Actual status (last update: Friday, September 19) ==
-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
-a: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 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.
-== Actual status ==
 ; ''centrum''
-: <font color="green">Up and running.</font>
+: <font color="green">Server is up and running.</font>
 ; ''carol''
-: <font color="blue">Working on ...</font>
+: <font color="green">Server is up and running.</font>
 ; ''marge''
-: <font color="gray">... to be moved.</font>
+: <font color="green">Server is up and running.</font>
 ; ''teogate''
-: <font color="gray">... to be moved.</font>
+: <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
-: <font color="green">Up and running.</font>
+: <font color="green">Server is up and running.</font>
 ; lithium
-: <font color="orange">Server is up and running.
+: <font color="green">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).</font>
-: There will be more maintenance work on server, so it can be restarted several times; meanwhile you can access your data.
-: The cluster is being checked and nodes will be started as soon as everything is ok.</font>
-: '''Some clients will be available on Thursday morning. Watch this page.'''
 ; helium
 : <font color="green">Cluster is up and running.</font>
 ; francium
-: <font color="orange">Server is up and running.
+: <font color="green">Cluster is up and running.</font>
-: There will be more maintenance work on server, so it can be restarted several times; meanwhile you can access your data.
-: The cluster is being checked.
-: The nodes will not be started before the '''infiniband''' switch is returned from a warranty repair - it can take two or three weeks.</font>
 ; iridium
-: <font color="orange">Server is up and running.
+: <font color="green">Cluster is up and running. Enable queues as needed.</font>
-: There will be more maintenance work on server, so it can be restarted several times; meanwhile you can access your data.
-: The cluster is being checked.
-: Nodes will be started as soon as everything is done.</font>
-: <font color="red">Need to connect new power cables from distant outlets, hope to finish this on Friday.</font>
 ; cobalt
-: <font color="red">Not running. Server will be turned on on Friday.</font>
+: <font color="green">Cluster is up and running. Some older nodes are broken and will not be repaired.</font>
 ; argon
-: <font color="red">Not running. Server will be turned on on Friday.</font>
+: <font color="green">Cluster is up and running. All nodes have been repaired.</font>
 ; krypton
-: <font color="red">Not running. Server will be turned on on Friday.</font>
+: <font color="green">Cluster is up and running. All nodes have been repaired.</font>
 ; radon
-: <font color="red">Not running. Server will be turned on on Friday.</font>
+: <font color="green">Cluster is up and running. All nodes have been repaired.</font>
 ; palladium
-: <font color="red">Not running. Server will be turned on on Friday.</font>
+: <font color="green">Cluster is up and running. Some older nodes are broken and will not be repaired.</font>
 ; vanad
@@ Line 87: / Line 58: @@
 ; niob
 : <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
+a: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.

Moving clusters

From Molecular Modeling Wiki

Latest revision as of 08:31, 19 September 2008

Actual status (last update: Friday, September 19)

Warning

Views

Personal tools

Navigation

system

Search

Toolbox