5+ hours down

[irdogg]

ticket#13098417 still down allmost 5+ hours down

i entrust your company with one of my best sites what a shame.

[JPC-Jim]

We are working on the issue, I can assure you. There is no need for you to continue posting in different threads. We already have your ticket number from another thread, and will have you back online as quickly as possible.

[irdogg]

ill be waiting

[Dayron]

It is necessary to continue to post. People browsing the forums to see what kind of issues they maybe facing when they sign up need to see this. It is odd to me that an ambiguous "power issue" can bring servers down when the Jag website touts no single point of failure and redundant power. Did the data centers get struck by lighting in GA and TX at the same time?

My server is still down after the "power issue" was supposedly resolved this morning. I too have websites hosted on my server that are very important to my clients.

How about an ETA on the FSCK job thats supposedly now running? How far into FSCK is the server? 10%? 49%... hung at 82%?



Ticket #13098441

[JPC-Jim]

You are free to post all that you want, but there is no need to open new threads. We have our hands full trying to get all the servers and sites back online, the less time spent checking new threads, the more time we have to deal with the issues at hand.

We will keep you updated as we get new information on each server that is still down.

[irdogg]

im guessing it struck both locations at the same time

[Dayron]

Point taken. Now how the FSCK status, ETA, and more detail on the reduntantly powered data center "power issue" and I'll stop bugging you guys. Sorry to be such a bother. Its just I have a server I pay for that nobody can access right now.

Let this bit of statistical data speak to all who are considering using this VPS service for your client's critical sites. Get used to what you see below.

Pinging sirius.nocdirect.com [69.73.188.90] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 69.73.188.90:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[wgiese]

You are free to post all that you want, but there is no need to open new threads.

History around this place has repeatedly shown, that those who whine the loudest in the forums get their problems resolved more quickly.

I can't count the number of times I've seen folks post they've been waiting on ticket responses and/or resolutions for hours/days, only to come here and have their problems addressed ASAP after b!tching about it.

'Tis a shame that's what it takes sometimes, but it is what it is.

And yes - I too, am anxiously awaiting a response as to why all these advertised redundant systems failed. Understanding of course, that the first priority is to get things back online - but this is a serious issue that needs explanation once things return to normal.

[JPC-Les]

Point taken. Now how the FSCK status, ETA, and more detail on the reduntantly powered data center "power issue" and I'll stop bugging you guys. Sorry to be such a bother. Its just I have a server I pay for that nobody can access right now.

Let this bit of statistical data speak to all who are considering using this VPS service for your client's critical sites. Get used to what you see below.

Pinging sirius.nocdirect.com [69.73.188.90] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 69.73.188.90:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Only a few server remain down, I'm sorry your vps is on one of them. As we've said we are working as hard as possible in restoring service 100%.

Also only a some servers in Atlanta were affected and none in any other facilities.

[Dayron]

Great. Now can anyone on your staff address the "no single point of failure" issue, and if the data centers are so well powered what the "power issue" was? Paying customers (as well as potential ones) should know. Also to the direct issue at hand what is the ETA of the FSCK job that we were told was running on servers that were keeping them offline?

[JPC-Jim]

Here is an update regarding servers that are having issues or down at the moment:

Share server Pegasus2.nocdirect.com is currently up and running fine but Apache service is not starting on it. So it is being worked on.

VZ nodes skywalker.nocdirect.com, and triton.nocdirect.com are running FSCK on it.

VZ nodes theoden.nocdirect.com, iri.nocdirect.com, and sirius.nocdirect.com servers are down and still being worked on.

[JPC-Les]

Great. Now can anyone on your staff address the "no single point of failure" issue, and if the data centers are so well powered what the "power issue" was? Paying customers (as well as potential ones) should know. Also to the direct issue at hand what is the ETA of the FSCK job that we were told was running on servers that were keeping them offline?

It's too early for me to say with any accuracy how this happened. There are both battery backups and generators. Once the report from the engineers are done we can pass it on.

[Dayron]

Ok great. I realize sirius.nocdirect.com is still down. Ping can tell me that. So what is being "worked on" in the last server list is FSCK isn't running on them and power has been restored?

[Dayron]

Thank you Les.
Any way to encourage technical staff to provide detail for the servers that aren't suffering from power issues, and not running FSCK? Those are the only 2 reasons given on the support site for outages, yet my server and a few others don't fit in either of those categories. I know some circumstances cannot be avoided, however, technical ambiguity may make the problem seem far greater than what is being told to the client.

[irdogg]

i hope their some type of punishment on whoever messed this up