One of our servers needs rebooting
Update: Reboot complete, all services are restored.
One of our servers needs rebooting
Update: Reboot complete, all services are restored.
We’re currently investigating. More information shortly
Update: All servers should be back up and running now.
server1 is down, affecting email access for some users. We’re now rebooting the server with an updated kernel
Update: server1 is back up and working, and with the updated kernel that should provide better reliability
We’re going to move the file storage across to another disk array while we conduct intensive tests on the one that failed the other day. This will take an estimated 1/2 hour during which file storage will not be working for all users.
Also, ‘last modified’ timestamps on files will be lost, with all files appearing to have been created about a day ago when we started preparing for this transfer.
Filestorage is working again.
The server containing the file storage has failed. We are checking now to see if anything has been lost – in the worst case the backups are about 4 hours old.
All users with file storage are affected.
Update: This was affecting the web interface, but service is now mostly restored (you still can’t access your file storage, but you should be able to do everything else).
Update: The storage enclosure that all the file storage is on is not responding to our repeated attempts to bring it online. The current plan of attack is to point everything at our latest backup.
Update: We’ve got the file storage unit back up, connected and mounted and everything should be back to normal now.
There was a very short outage affecting all imap servers for less than 5 minutes when a change to logging policy confused the imap server processes. The servers restarted themselves automatically, but users may have experienced error messages.
The servers are all back online.
