shell.gradwell.com - Resolved
Service Incident
shell.gradwell.com
Tuesday 7th September 2010 @ 14:31 (BST) (Posted by Dean Green)
Affecting Web Hosting
Impact Level: High
As of Monday 13th September 2010 @ 15:09 (BST), we believe this issue to be resolved:
We are now satisfied that the new shell server is up and running with full functionality, including email and customer-editable crontabs.

Please note that this shell server is Debian-based, as opposed to the previous shell, which ran CentOS.
If you are still experiencing the problem described, please contact our support team.
Overview
shell.gradwell.com is currently offline
Customer Impact
All customers utilising our shell server
Gradwell Action
Our sysadmin team are working on bringing a replacement shell server online
Status
This post is closed
Update #1: Tuesday 7th September 2010 @ 16:16 (BST) (Posted by Lawrence Matthews)
Our engineers are still working with the shell server and aim to restore access as soon as possible. We apologise for any inconvenience.
Update #2: Tuesday 7th September 2010 @ 17:03 (BST) (Posted by Lawrence Matthews)
A new shell server has been installed and the DNS will propagate to it shortly. Until DNS propagates, it will be accessible from turtle.shell.gradwell.net. This server at present will only support basic shell functionality. Our engineers are working on bringing it to parity with the normal shell features.
Update #3: Wednesday 8th September 2010 @ 10:25 (BST) (Posted by Lawrence Matthews)
The new shell server is undergoing further work to make it ready for regular use.
Update #4: Wednesday 8th September 2010 @ 12:30 (BST) (Posted by Lawrence Matthews)
If you have our shell server or turtle.shell.gradwell.net in your known_hosts file (typically found in ~/.ssh/known_hosts), you may need to remove its entry as our host key has changed.
Update #5: Wednesday 8th September 2010 @ 16:29 (BST) (Posted by Lawrence Matthews)
shell.gradwell.net is now ready for customer use. Existing cron jobs will still be running, but users will be unable to edit their crontab.
Update #6: Thursday 9th September 2010 @ 10:07 (BST) (Posted by Lawrence Matthews)
Our systems administrators have identified and resolved an issue preventing some customers from accessing their home directories on the new shell server.
Update #7: Thursday 9th September 2010 @ 14:21 (BST) (Posted by Lawrence Matthews)
Our systems administrators are working to restore the ability to edit crontabs.
Update #8: Friday 10th September 2010 @ 09:47 (BST) (Posted by Lawrence Matthews)
We are still working on allowing customer-editable crontabs. This server does not have the full compliment of packages our previous shell server did; if there are any packages you require installed, please contact our support team and let us know which you need installed.
Update #9: Monday 13th September 2010 @ 15:09 (BST) (Posted by Lawrence Matthews)
We believe this issue is now resolved. The following closing update was provided:
We are now satisfied that the new shell server is up and running with full functionality, including email and customer-editable crontabs.

Please note that this shell server is Debian-based, as opposed to the previous shell, which ran CentOS.