66.34.217.64 Unix12 Refusing Connections

Apache has been refusing http connections for about 20 minutes now. I tried to open a trouble ticket but the link just points to a knowledgebase with now option of opening a ticket.

From my monitoring service (websitepulse.com):
04/15/2004 23:01:45 Connection refused 46.2650 0.00% 43.60 44.46 45.01
04/15/2004 23:05:31 Connection refused 46.8390 0.00% 44.05 44.46 45.04
04/15/2004 23:10:04 Connection refused 111.7830 0.00% 43.61 44.18 45.41
04/15/2004 23:11:12 Connection refused 47.1530 0.00% 44.87 46.53 47.09

It's back up now...

But it's incredibly slow....lol (this only happens when I need to do an important update)

[bigdave]

You can always submit a ticket by going to www.vortechsupport.com.

Thanks Big Dave. I submitted a ticket this morning as I'm still seeing some strange intermittent problems.

Have you run a traceroute to determine if the problem lies in your network? Since noone else is complaining of issues, I would say perhaps your network is having an issue somewhere...

tracert <domain.com> from Windows Command prompt.

Big Dave helped me and everything is all better now.

Ok your server alias for unix12 was pointing to the wrong IP address, I have fixed this issue but it will have to propagate throught out the internet which could take a couple of hours. Dave

It was strange though. Webshell wasn't working for any of my domains and FTP was crawling at like .08 kbps for almost a day. Then my monitoring service kept paging me every 3 minutes with a connection refused error. Website pulse was checking from Miami so it wasn't just me.

ok, since everyone thinks I'm crazy, as of 9:05pm PST, my site at http://www.raincitystory.com

Location Last check Status Resp. time
216.157.141.111
(ms.) Ping Loss Min Avg Max
Miami, FL 23:02 Connection refused
EDT: 5 min. 46.6350 20.00% 43.59 44.07 44.67

28 short failures today. This is a check from Miami, FL and I t get a failure from Seattle, WA.

Of course, since I posted, it has come back up but what could be causing Apache to refuse http connections?

[Carly]

Apache restarts every night around midnight (EST) on the Unix servers, IIS on the Windows servers. Usually the downtime is less than a minute. Somtimes there is a hiccup which may cause just a little longer to come back up.

Sorry for the inconvenience!

That's ok Carly, I guess Apache would need to restart each time it adds a virtual host. So Apache must be choking...

Coincidentally, I moved here because my last host had a monthly uptime of 68.9% in Feb. due to Apache refusing connections. They didn't monitor http so they kept telling me I was full of it despite lots of other custs complaining and my reports from Alertra and Website Pulse. So I guess I shouldn't complain at the few here.

Actually, apache checks to see if the config files have changed every 5 minutes. If they have, it restarts. It takes less than a second, and you probably won't ever notice. If you start loading a page and it restarts in the middle, chances are it will just restart or pick up and it may seem like it just took an extra second, but I've never happened upon it restarting on any sites and noticed it as downtime.

We also do full server monitoring, CPU usage, disk usage, Apache status, etc. And if something is down we get a nice warning tone throughout the office.

Simply put, your "apache refusing connections" needs to be submitted in a ticket as its an issue only happening to you. Be sure to include a full traceroute from the affected machines and we'll see if we can help you determine the issue.

[Brangwyn]

IIS will restart your website too if you make a change to your global.asa ... obviously thats not the case here, just throwing it in as it's sometimes a usefull trick to get IIS to recycle your site if nothing else seems to work.