NT16 problems?

OK, we will stay on NT16 until you have tested the new server move functionality.

In the meantime I will keep watching this thread closely for news regarding the issue with NT16 and what you are doing to resolve it.

[jmbeach]

ADMIN:

PLEASE, I beg of you - what is the status of NT16???

continuous outages are like sharp needles in my eye when I'm trying to work on my projects... okay maybe not that bad, but...

Also, big trouble with sites hanging for about 30 seconds before starting to load.

Also Access db's - Requests are just hanging on a dsn-less - is the driver missing?

What else is this server suffering from? Please we all just need to know what's happening to the server, and what is being done to fix it.

[jmbeach]

Here is the latest I see

On top of it's inability to keep IIS running for more than 20 minutes at a time, it seems the server has taken to not liking any Access database request. Every time I make an access request (dsn-less) it hangs - then, strangely enough, if I try to go back and just go to a page with no database connection it hangs for about a minute.

Then everything is fine until I try to connect to a db again.

What is wrong with it? What is being done to fix it.

I dare not move to the new server, as I need to maintain all the COM's that are working on 16, plus my clients cannot handle the downtime for propagation. As it stands they cannot handle the downtime we're seeing with 16 either.

Help us Vortech, you're our only hope.

Hrm, that might actually be some good info for them, with the databases hanging, it might give some more clue about what is causing IIS to hang, anything else you see might also be worth sharing.

[admin]

Well I made some changes in IIS. It seems ok now but I can't tell you.. Please let me know if your having issues with asp pages.

[admin]

Ok NT16 seems some what stable now but its hard to tell as there is not much of a load right now.. Its been up for over 2 hours now and no restarts of IIS.

Looks like we are having another downtime incident right now... http://www.alertra.com/viewalerts?site_id=185319

...HELLO?!?

Our site has been down for nearly 2 hours now... It's about 4:20 AM in Florida, and I wonder if our site is going to stay down until Vortech's tech support gets up from bed...

I've sent in a trouble ticket... PLEASE HELP ASAP!!!

Please let me know where I can get a copy of your downtime policy. We are going to ask for a refund for this.

[admin]

The server just went down at 05:28:21. Also the server would need to be down for more then 8 hours at one time for a refund.


2003-3-11 05:44:47 NT16 Probe Server Recovered Attempting Alerts
2003-3-11 05:44:13 NT16 Probe Server Recovered Attempting Alerts
2003-3-11 05:44:11 NT16 Probe Server Recovered Attempting Alerts
2003-3-11 05:43:46 NT16 Probe Server Recovered Attempting Alerts
2003-3-11 05:42:46 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:42:10 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:42:09 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:41:45 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:40:44 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:40:27 Masterswitch7 Probe Server timed out Attempting Alerts
2003-3-11 05:40:08 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:40:06 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:39:44 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:38:42 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:38:05 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:38:03 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:37:43 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:36:41 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:36:02 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:36:00 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:35:42 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:34:40 NT16 Probe Incomplete packet Attempting Alerts
2003-3-11 05:34:00 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:33:58 NT16 Probe Connect failed Attempting Alerts
2003-3-11 05:32:39 NT16 Probe Server Recovered Attempting Alerts
2003-3-11 05:32:06 Masterswitch7 Probe Server timed out Attempting Alerts
2003-3-11 05:30:52 NT12 Probe Connect failed Attempting Alerts
2003-3-11 05:30:52 NT12 Probe Connect failed Attempting Alerts
2003-3-11 05:30:37 NT16 Probe Server timed out Attempting Alerts
2003-3-11 05:29:39 NT16 Probe Server timed out Attempting Alerts
2003-3-11 05:28:21 NT16 Probe Server timed out Attempting Alerts

You say the server needs to be down for "more than 8 hours at one time" to get a refund...

What about your "99.9% uptime or your money back" policy then???

Please explain exactly what that percentage refers to.

If refunds are issued based on the recurring monthly fee, then I believe we are well below 99.9% uptime for the current month.

[Vixen]

You may want to read this post http://matrixwebhosting.net/forum/sh...&threadid=3207

[Vixen]

Originally posted by Giacomo72

Our site has been down for nearly 2 hours now... It's about 4:20 AM in Florida, and I wonder if our site is going to stay down until Vortech's tech support gets up from bed...

Ummmmmmmm call me crazy but 5:28 - 5:44 is 16 minutes and not 2 hours. Unless there is a new form of math that no one told me about.

You may want to read this post http://matrixwebhosting.net/forum/sh...&threadid=3207

Is there a SLA for shared hosting resellers (H-Sphere CP)?

Ummmmmmmm call me crazy but 5:28 - 5:44 is 16 minutes and not 2 hours. Unless there is a new form of math that no one told me about.

As a matter of fact, our web site remained inaccessible from 08:29:29 to 12:00:13 GMT+0100 (that's about 3.5 hours) according to a service monitoring it every 5 minutes from several different geographic locations, as you can see from the following check log:

Time (GMT+0100) Checked From Result Size Secs
03-11-2003 12:05:15 London UK OK 58834 1.65
03-11-2003 12:00:13 Los Angeles USA Unable to connect N/A 0.66
03-11-2003 11:55:13 Frankfurt GERMANY Connection to HTTP se N/A 0.64
03-11-2003 11:50:42 Detroit USA Connection to HTTP se N/A 30.14
03-11-2003 11:45:40 Oklahoma City USA Connection to HTTP se N/A 34.42
03-11-2003 11:40:45 Montreal CANADA Connection to HTTP se N/A 34.69
03-11-2003 11:36:28 London UK Connection to HTTP se N/A 30.32
03-11-2003 11:31:05 Los Angeles USA N/A N/A 0.00
03-11-2003 11:25:37 Frankfurt GERMANY Connection to HTTP se N/A 30.54
03-11-2003 11:21:13 Detroit USA Connection to HTTP se N/A 67.96
03-11-2003 11:15:40 Oklahoma City USA Connection to HTTP se N/A 31.20
03-11-2003 11:10:45 Montreal CANADA Connection to HTTP se N/A 31.01
03-11-2003 11:05:43 London UK Connection to HTTP se N/A 30.58
03-11-2003 11:00:45 Los Angeles USA Connection to HTTP se N/A 30.16
03-11-2003 10:55:37 Frankfurt GERMANY Connection to HTTP se N/A 32.15
03-11-2003 10:50:38 Detroit USA Connection to HTTP se N/A 30.19
03-11-2003 10:46:00 Oklahoma City USA Connection to HTTP se N/A 57.31
03-11-2003 10:40:32 Montreal CANADA Connection to HTTP se N/A 30.95
03-11-2003 10:36:15 London UK Connection to HTTP se N/A 30.60
03-11-2003 10:30:52 Los Angeles USA Connection to HTTP se N/A 30.23
03-11-2003 10:25:35 Frankfurt GERMANY Connection to HTTP se N/A 32.87
03-11-2003 10:20:37 Detroit USA Connection to HTTP se N/A 30.29
03-11-2003 10:15:41 Oklahoma City USA Connection to HTTP se N/A 30.34
03-11-2003 10:10:34 Montreal CANADA Connection to HTTP se N/A 30.75
03-11-2003 10:05:44 London UK Connection to HTTP se N/A 30.31
03-11-2003 10:00:41 Los Angeles USA Connection to HTTP se N/A 30.19
03-11-2003 09:55:41 Frankfurt GERMANY Connection to HTTP se N/A 30.79
03-11-2003 09:50:41 Detroit USA Connection to HTTP se N/A 30.36
03-11-2003 09:45:40 Oklahoma City USA Connection to HTTP se N/A 30.71
03-11-2003 09:40:35 Montreal CANADA Connection to HTTP se N/A 30.79
03-11-2003 09:35:42 London UK Connection to HTTP se N/A 30.26
03-11-2003 09:30:43 Los Angeles USA Connection to HTTP se N/A 30.82
03-11-2003 09:25:46 Frankfurt GERMANY Connection to HTTP se N/A 30.45
03-11-2003 09:20:40 Detroit USA Connection to HTTP se N/A 30.19
03-11-2003 09:15:46 Oklahoma City USA Connection to HTTP se N/A 30.64
03-11-2003 09:10:46 Montreal CANADA Connection to HTTP se N/A 31.46
03-11-2003 09:05:42 London UK Connection to HTTP se N/A 30.39
03-11-2003 09:00:42 Los Angeles USA Connection to HTTP se N/A 30.15
03-11-2003 08:55:46 Frankfurt GERMANY Connection to HTTP se N/A 30.44
03-11-2003 08:50:36 Detroit USA Connection to HTTP se N/A 30.28
03-11-2003 08:45:53 Oklahoma City USA Connection to HTTP se N/A 30.94
03-11-2003 08:40:46 Montreal CANADA Connection to HTTP se N/A 30.89
03-11-2003 08:35:43 London UK Connection to HTTP se N/A 30.69
03-11-2003 08:34:24 Los Angeles USA Connection to HTTP se N/A 32.02
03-11-2003 08:33:05 Frankfurt GERMANY Connection to HTTP se N/A 36.60
03-11-2003 08:31:40 Detroit USA Connection to HTTP se N/A 69.11
03-11-2003 08:29:28 Oklahoma City USA Connection to HTTP se N/A 32.94

Source: http://www.alertra.com/viewalerts?site_id=185319 (click on the links for downtime details)

Talking about math... I would be curious to know how the "99.9% uptime" is calculated.

[admin]

Originally posted by Giacomo72


Is there a SLA for shared hosting resellers (H-Sphere CP)?

Not at this time, we are working up something for shared hosting and resellers.