Earlier today, at around 08:00 Sun 17 May 2015 UTC, ridley.fastlizard4.org suffered an unexpected downtime. \u00a0At this time, the problem seems to have been caused by a hardware issue of some kind, or some other problem with the hypervisor host that ran ridley. \u00a0CPU usage increased to 800% (all 8 cores under 100% load), seemingly due to iowait, while disk activity was reduced to near-zero. \u00a0This seems to point to a disk I\/O failure of some kind, which eventually caused the server to bog down so much that the CPUs “stalled” and the entire system became totally unresponsive. \u00a0The server also did not respond to a hypervisor shutdown command; eventually, the only way to bring down the system was to issue a “destroy” command that effectively “pulled the plug” on the system.<\/p>\n
In line with the I\/O problems ridley has been experiencing for a while now, I took advantage of this unscheduled downtime to also perform the waiting free Linode upgrade on ridley. \u00a0In addition to moving the system to a new hypervisor host, ridley’s RAM has now doubled and it has more bandwidth available; however, the number of vCPUs has decreased from 8 to 4.<\/p>\n
Ridley is now back up and running, and users may now log in to restart any services or programs they may have had running. \u00a0I have checked the system, and everything appears to now be functioning normally, with all daemons and services up and running. \u00a0The LizardIRC server daemon has also been brought back up, so ridley.lizardirc.org has been relinked to the network and services are also back up and running.<\/p>\n
Apologies for the\u00a0inconvenience, and thanks for bearing with me!<\/p>\n