1. Skip to navigation
  2. Skip to content
  3. Skip to sidebar
Source link: http://archive.mises.org/18549/hardware-failure/

Hardware Failure (Not)

September 27, 2011 by

It’s been a troubling day. One of our two most gigantic hard drives on the server failed, and we’ve been working all day with technicians to bring it back. It will be up in tie but the waiting is tedious. Meanwhile, the store and other features are shut down. Truly, we are sorry for this, but it reinforces the next goal of moving entirely to the cloud, not just for user interface purposes but also for fundamental server functioning itself. The physical world is forever decaying, especially given the extreme traffic and use we’ve been undergoing for about 45 days. We’ll be back to normal functioning by this evening certainly.
—-

Added: It turns out not to be a hardware failure but a network failure from the host itself. Sadly, this is something that no one can prevent. There is nothing we could do on our end. And of course no host is perfect, no technician omniscient. The only good that comes from a flaky day like this is that we were able to lean on our provider to provide us a massive upgrade in several areas, and at no charge. Here’s to the future!

{ 12 comments }

J. Murray September 27, 2011 at 4:31 pm

I thought the cloud was supposed to keep this from happening.

Jeffrey Tucker September 27, 2011 at 4:49 pm

The cloud works as an interface between the server and you. The server itself needs to move to the cloud, which is stage two. We scheduled that move for October 1. We didn’t make it in time.

incidentally, even with one drive off line, we have the entire linux box plus 1.5TB on the windows fully functional. Even then, it is not enough. That gives you an idea of the city-sized operation we are running here.

J. Murray September 27, 2011 at 4:53 pm

Ah, I wasn’t aware it wasn’t finished yet. But, it seems to be fixed already, getting the regular home page again.

Nielsio September 27, 2011 at 4:50 pm

It’s at the moment (only) a front-end caching cloud for static pages.

S. Fortson September 27, 2011 at 4:57 pm

Mises.org is the “cloud” to everyone except Mises.org. The notion of moving to the so-called cloud is simply putting your data on someone else’s hardware and paying them to handle hardware maintenance, with all the same types of risks and some new ones. The “cloud” costs versus those of directly employed IT are often comparable, though I suppose it is an obvious and simple exercise in the concept of comparative advantage. I just hate the term cloud because it implies something more complex than it is.

Rick Hull September 27, 2011 at 5:04 pm

I’m not sure exactly what mises.org means by ‘cloud’. But generally it means decoupling the software from the hardware. Instead of a stack whereby a single piece of hardware hosts the OS which hosts the application, you have a “cluster” of hardware nodes that run a distributed OS, and the distributed OS hosts the application. Concrete examples of “cloud” service providers include Amazon, Rackspace, Heroku, etc.

EDIT: Actually, i’m not sure how common the distributed OS model is. You might have a “cloud” of homogenous nodes running single-machine OS, whereby your app has persistent storage outside of the app nodes, and app nodes are restarted on demand if any node has issues.

It’s a different model than simple “colocation” which can reasonably be applied to your description.

S. Fortson September 27, 2011 at 8:54 pm

It is (over-)used as a marketing term to mean nearly any service that can be accessed remotely, generally via the Internet. The term seems to originate from what IT folk have long used to represent networks external to the one they’re mapping (such as the Internet). That icon was a small cloud instead of a block, to represent the indeterminate and arbitrary nature.

Generally, it now seems to be used to signify that one need not be concerned about the workings of some service to which you desire access. For example, Security-as-a-Service (SaaS) is antivirus/computer security software that purports to utilize the “cloud” to manage your business’ computer security needs while Netflix streaming can be considered a “cloud” movie service. They offer very different services with non-similar functional methods. Both still run software on your machine (which is needed to interact with the remote service). My issue is that they’re often marketed as nearly the same thing (cloud services), simply because a casual user need not know the internal workings of either service.

It isn’t a big deal, just a personal annoyance; particularly so when vendors try to sell such services to my company as if it were something novel.

Tom E. Snyder September 27, 2011 at 5:33 pm

I was wondering what happened to my daily .epub fix. Now I know. ;-)

Marc Sheffner September 27, 2011 at 6:41 pm
FDominicus September 28, 2011 at 2:22 am

Sorry something still is broken at least for a few days. If I try to get to the ControlPanel I most of the time get timeouts:
Server Error in ‘/Community’ Application.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +404
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +412
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1363
System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +59
System.Data.SqlClient.SqlDataReader.get_MetaData() +118
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +6387873
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +6389442
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String meth

And this at least since a week or so. It’s a pitty, this blog has found quite a lot of readers AFAIKT

Ned Netterville September 28, 2011 at 7:45 am

Wot, no………..cloud?

G8R HED September 28, 2011 at 9:14 am

Solar flare?

Comments on this entry are closed.

Previous post:

Next post: