Update : 4.37pm - named is back up and sites are resolving. Load is stll elevated but we are monitoring as the RAID is still verifying. Sorry for any inconvenience. It is no consolation but this is the first major outage on this server in a long time and we a truly sorry if you have been inconvenienced.
===========================================================
Update: 3.35pm - A level 3 tech is on the server now looking into why we cannot restart named service or rebuild named. We will update you as soon as possible. Thanks for your extended patience.
===========================================================
Update: 3.11pm - named.conf is throwing errors so unfortunately we need to rebuild it. Until that happens no websites on the server will resolve. We apologise for this ongoing issue and will update this thread once we have the server back up and running again.
===========================================================
Update: 2.55pm - we are still actively working at this server to get a resolution to the high load issue
===========================================================
Update: 2.42pm - Approximately 90 minutes ago we were alerted by our monitoring system to the fact server 12 was unresponsive. A reboot appeared to cure the issue. A few moments ago we saw the load spike to 18 and sites once again became unresponsive.
We have determined that since the reboot the server was undergoing a RAID array verification that is currently at 4%. This together with Cpanel log file updating has caused the ongoing issues this afternoon.
We have stopped the logs from being updated today and this has reduced the load somewhat. We will continue to monitor this server for the rest of the day.
Thanks for your patience if you are on this server