server1 is experiencing the same problem server1 had yesterday, and requires a reboot. We will make a configuration change later today which we hope will resolve this problem (which is related to the oustanding Linux kernel bug that has been causing problems for a while).
Update: the server is back online
