Imagine waking up one morning, taking your first cup of coffee over to your computer with a plan on writing a new blog entry, only to find your blog’s host is down.
Scot K9JY found his hosting service had become unreliable and write of his transition: New Hosting Company for K9JY.com
….. I have given the posting a break because of a problem: my previous hosting company has become steadily unreliable.
This unreliable service translates to readers as “500 Internal Server Error” messages, long load times, “Hello, World” postings, and — my favorite — presenting an “install WordPress” option as the home page. This allows anyone on the planet to not only overwrite my version of the software on the system, it gives them access to the entire site! Wonderful!
And clearly unacceptable. ……
Scott W4PA had announced he was stopping his blog (and taking a break from Radio Contesting) in a message that few of us read, as his Blog Host service went down, and it seems for good:
Journalspace is no more.
DriveSavers called today to inform me that the data was unrecoverable.
Here is what happened: the server which held the journalspace data had two large drives in a RAID configuration. As data is written (such as saving an item to the database), it’s automatically copied to both drives, as a backup mechanism.
The value of such a setup is that if one drive fails, the server keeps running, using the remaining drive. Since the remaining drive has a copy of the data on the other drive, the data is intact. The administrator simply replaces the drive that’s gone bad, and the server is back to operating with two redundant drives.
But that’s not what happened here. There was no hardware failure. Both drives are operating fine; DriveSavers had no problem in making images of the drives. The data was simply gone.Overwritten.
The data server had only one purpose: maintaining the journalspace database. There were no other web sites or processes running on the server, and it would be impossible for a software bug in journalspace to overwrite the drives, sector by sector.
The list of potential causes for this disaster is a short one. It includes a catastrophic failure by the operating system (OS X Server, in case you’re interested), or a deliberate effort. A disgruntled member of the Lagomorphics team sabotaged some key servers several months ago after he was caught stealing from the company; as awful as the thought is, we can’t rule out the possibility of additional sabotage.
But, clearly, we failed to take the steps to prevent this from happening. And for that we are very sorry.
So, after nearly six years, journalspace is no more.
If you haven’t yet, visit Dorrie’s Fun Forum; it’s operated by a long-time journalspace member. If you’re continuing your blog elsewhere, you can post the URL there so people can keep up with you.
We’re considering releasing the journalspace source code to the open source community. We may also sell the journalspace domain and trademarks. Follow us on twitter at twitter.com/jsupgradesfor news.
And large numbers of Amateur Radio websites of all sorts went down as Al K3TKJ retired (no idea if this was announced in advance or widely known) and all QSL.net and QTH.net hosted services are being migrated to Scott KA9FOX (QTH.com appears unaffected):
QSL.net & QTH.net Announcement
December 31, 2008
Dear fellow hams,
After 13 years of providing hams with no cost web space, e-mail forwarding and mailing list services through QSL.net and QTH.net, I have decided to retire. All QSL.net and QTH.net servers and Internet connections at my home QTH are being turned down.
Scott KA9FOX has graciously decided to pick up where I left off, and he is in the process of migrating all services to new hardware. See below for an update on the status of the migration.
I want to thank all of you for all of your support over the years, and I hope that you will support Scott as he takes over the reigns.
See you on the air!
73 – Al Waller, K3TKJ
Server Migration Update from Scott KA9FOX
Last Update: Dec 31, 2008 21:34z
Thank you for your patience as this transition is made. All qsl.net/qth.net services are being moved onto brand new hardware in a well-connected data center in the central US. This web page will be updated so you can stay informed of the progress.
If you would like to make a contribution to support my efforts to keep QSL.net / QTH.net on the web, see the Donation Page.
SERVICE SERVER STATUS
Web Sites http://www.qsl.net
(ftp.qsl.net) Original server down, User data being transported to data center. ETA Jan 3rd, 2009.
Mailing Lists mailman.qth.net Original server still up, data will be migrated shortly. Expect some downtime during transition.
E-mail Forwarding mail.qsl.net Original server still up, data will be migrated shortly. Expect some downtime during transition.
DX Info/Log Search dx.qsl.net Original server still up, data will be migrated shortly. Expect some downtime during transition.
On the bright side Scot K9JY was able to recognize his old host’s problems in the making, and fully port everything he wanted to retain to a new hosting service.
Scott W4PA had announced his refocus and end-of-blog so his project’s continuity was not as a critical when Journalspace crashed & burned.
The QSL.net/QTH.net services being affected are greatly mailing lists and are transitioning in an orderly fashion. Downtime hopefully will be only the time the Internet’s DNS server systems need to populate the new server information.
But do you as a writer have a good plan to back up parts of your web-presence that you would like to keep no matter what?
And those of you who are readers, do you have a a system to save web-information you want for future reference? Remember bookmarking the URL is not going to be much use if that page disappears from the web.
Very interested in your thinking and planning along these lines!
More to follow in additional posts,