MarkRH

Well, it looks like they've finally cracked this nut! Much better!



Kudos to support! (hopefully stays that way.. heh).

__________________

fury

Did they give you any info as far as what was the culprit?

__________________
fury™ - not helping the situation since 1987
robmonroe.net | | bullsux.com

MarkRH

Well.. one person set the DNS resolver of the server to 4.2.2.1 which did improve the time from 20-50 seconds for that script down to the 0-7 second range but I replied back that while it was better than before, it wasn't the best solution as they would then be dependent on the routing to that system and how busy or not busy it was.

It still wasn't as good as it had been before the power outage.

Next response was that they changed the resolver to the server's IP address which is what produced the under 1 second times and the end of this.

I have a feeling that more than that might have been done; otherwise, it shouldn't have taken over 30 hours to come upon just that. They probably had their hands full working on more pressing matters.

But it was a weird one.. I could ping google.com and what not from an SSH connection and get immediate responses... but PHP was having major lags when supplying fsockopen() with domain or sub-domain names and instant connects when supplying IP addresses.

Anyway, I did change the scripts that I could to just use IP addresses to connect to... doesn't work with my own sub-domains and add-on domains; however, as the server would have no idea where I was really trying to connect to.

__________________

MarkRH

Hmmm.. spoke too soon.. server took a dump or something.. just got rebooted 40 minutes ago with a load of 10.8 now and that script of mine just took 155 seconds and the pop service is down according to cpanel. 2 users are shelled into the system so maybe support is doing something with it.

Ticket time I guess..

__________________