Problems with login nodes on Fram

login-2 has successfully been rebooted now, and is back in production.

login-2.fram is currently not responding. Unfortunately, while trying to reboot it, we rebooted login-1 instead. (This is probably due to a configuration error - we are looking into it to prevent it happen again.)
We will try to reboot login-2 physically, but if we cannot do that now (people are on vacation), we will remove it from the pool of login nodes one gets to when ssh’ing to login.fram.sigma2.no.