Win13

Appartently this server has been down a lot lately… I’ve recently been asked to monitor an account on this server.

I noticed it’s been down a couple mins now.

We have our best client on that server and he’s getting pretty fed up about seeing “Service Unavailable” all the time.

What can and is being done about this issue??

I am not aware of any such issue. Our ASP asp.NET checks are reporting 100% uptime for this month.

Can you PM me which domain. Is he using asp.net 2.0. Any tickets about this issue? I’ll investigate

It is not running asp.net, just a plane old asp Soop portal.

It’s rather inacurate if your reporting software says asp.net was up 100% for this month. As I saw the server drop from ipcheck yesturday for over 5 minutes.

I have been told this is happening very often on Win13. I am surprised there is no other cutomers complaining about it.

Sure it usually only lasts for a short while, but it’s enough to have our customer considering dropping us.

He just switched from 1and1 for slow performance from his site.

How can we be competitive when even you say there is no problem. I am only using the same IpCheck that you have made available, and it clearly showed the server drop.

I am not sure if there was a ticket created, but this is a server wide problem that should be noticed and fixed from you guys even before a ticket is created.

Wheemer, There have been a few sites causing problems on the pools in Win13, this happens on most of the servers that are poen to signups, we have to find and get them sorted/isolated/notified of problems when found. In addition to that, for the first few days of the server the techs were utilizing the MS ASP.NET fast switch for ASP.net 1.1 and 2.0, this caused the pools to crash and need a restart to come back up.

We have discontinued use of their fast switch and gone back to doing it manually which does not require a restart.

Sometimes a pool can go down and IPcheck won’t see it, as it is not monitoring that pool.

I am not talking about anything IPCheck cannot see. I am talking about a problem that was very easily seen buy open eyes and looking at the red marks on win13’s asp and asp.net check graphs.

It always happens that when there is a problem you guys say something like: “Well everything is fine, there is no problems or we would know about it”.

Yet anybody that has good vision can see the problem perfectly easily looking at IPCheck. Perhaps you should delete whatever horrible software you are using to alert you of problems and just sit someone down at the IPCheck page.

It even plays a sound and turns red, so it should be real easy.

Besides, this is an IIS reset anyways. Or why else would the site load saying service unavailable. I can’t believe you don’t have the ability to detect when IIS is dropped for 5 mins.

Wheemer, I told you IISresets are done by the techs after some asp.net changes, so of course it says it is down.

Following is a log of the slowdown our customer has given me:

January 21, 2006

1:16 a.m. E.S.T.
Service Unavailable

Then:

The page cannot be displayed
No pages accessible

3 Minutes later @ 1:19 a.m. E.S.T. the site came back online…

Again at 1:35 a.m. E.S.T.

Then:

The page cannot be displayed again
No pages accessible … no .asp, .html, etc…

FTP still works.
@ 1:38 a.m. E.S.T. the site came back up again…

Before and after error, speeds seemed fine; no obvious slow-down.


January 22, 2006 @ 3:31 A.M. E.S.T.

this guy already had problem with application pool crashing and site getting frozen. now if this error continues he might just switch back to 1and1 which will be big loss to us.

i promised him great uptime what we got for our sites on jodo servers. please look into this matter and make sure this doesnt happen again.

You would be best to send a ticket if this is still happening, a lot of time was spent optimizing the pools yesterday afternoon.
By your datestamps, I think this is already resolved.

As Stephen has said, some pool reorganisation was done on Win13 and some mistakes were made by us, using fast switch..

We plan to turn off the server for signups within a week. The maximum abuse on a server happens during the signup phase… :frowning: