FQ Alert: Slowness?

[Deb]

We currently are experiencing a problem with the Ethernet port in the router.[nbsp][nbsp]Andrew is currently at the NOC with the lead techs within NOC working on a fix.[nbsp][nbsp]This should be solved soon.[nbsp][nbsp]Rest assured the sites should NOT be as slow as they are right now.[nbsp][nbsp]You should experience a major speed increase soon.

Our sincere apologies for this particular snafu…. There may be a brief outage while the repair is made.[nbsp][nbsp]We’re doing our best to bring you the best.

All open issues will be addressed once this area is fixed.[nbsp][nbsp]We are not done until it’s done right.

Deb
[nbsp]- I'm in it for the long haul.

[jimbo]

Does Andrew sleep?

-jim

[Deb]

OUCH! That hurt :( As was made obvious by the forums being down Morph (the server FQ/Aota uses) and ASTRO had some problems with the router fixes.... these are now solved.

Our sincere apologies for the extended delay on this issue.

Andrew is on his way back home and will begin addressing the other open issues.[nbsp][nbsp]I do realize that some are having problems with FTP, RealAudio, Email, SSL, and counters... these are now going back up near the top of the list.

Thank you so much for your patience... I promise you we're tackling each thing as fast as we can on this end.

Deb
[nbsp]- He takes a lick'n and keeps on tick'n


[This message has been edited by Deb (edited 09-03-00@7:22 pm)]

[Nicole]

Congratulations and thanks for all the hard work.

Here's a thought.

Visitors to our sites during the move would have got the "Upgrading" page into their browser cache.[nbsp][nbsp]After the move the browsers might see that page as later than the "real page" that was uploaded earlier, and might still display it.[nbsp][nbsp]At least that was my own experience.

So it might be wise to upload a "later" version of the whole site.[nbsp][nbsp](Index page alone would not be enough for visitors who went straight to a page of their choice).

Make sense?[nbsp][nbsp]Or am I missing something (as usual :)).

- Nicole

[Juan G]

I think jimbo means that, after all the long night and all the Sunday working, it seems that Andrew and others are still working without stop! Not good for health.

Reinstalling everything in a new location is evidently not easy, but the results seem really nice. Thank you very much for the excellent speed of the new connection! :)

And please rest a little sometimes. ;)

[This message has been edited by Juan G (edited 09-03-00@9:13 pm)]

[Deb]

The expire was set to June 11th 1998 to prevent the type of issue you are thinking of.[nbsp][nbsp]The page tells the browser that it expired a long time ago so the browser shouldn't cache it.[nbsp][nbsp]Additionally the Upgrading page was on your old IPs and your site is now being viewed on the new IPs so this in effect nullifies the upgrade page :)

Deb
[nbsp]- Dev/Null

[TDarlington]

Well, I have 11 sites hosted here at FQ, and they're all back up... except this one: www.sw-inc.com (http://www.sw-inc.com) still shows the "Progress in Progress" screen.[nbsp][nbsp]Since the DNS for that site is provided by the client's ISP, I'm guessing that they're pointing to the old IP address and not the new one.

I can get their ISP to fix this, but not quickly.[nbsp][nbsp]Can you set up some sort of bounce from the old site's IP to the new one?

FYI, I know this isn't a browser cache problem because I telnetted to a machine on the other side of the country, fired up Lynx to check it, and got the same result.

Thomas

[Deb]

There really isn't anything we can do in that area.[nbsp][nbsp]The ones handling the DNS need to make those updates.[nbsp][nbsp]If we were in control it'd be different but since you are not using us for the DNS we're pretty tied in that area.[nbsp][nbsp]Hopefully the other ISP will be able to step in quicker than you think as the edit shouldn't take but a couple of seconds....

Deb
[nbsp]- What's yours, is not mine.

[TDarlington]

Well, OK, but what should I tell them?[nbsp][nbsp]I went through the backdoor to CNC for the site (http://xsw-inc.futurequest.net/CNC/), clicked "Server Info", and saw that the IP address is supposedly 63.95.221.82.[nbsp][nbsp]So I type in that IP address in a web browser and get a "404 File Not Found" page.[nbsp][nbsp]Something weird going on here?

(I'm willing to take this to e-mail if this isn't relevant to anyone else.)

[Deb]

You just need to have them update what they currently have for your IP to the IP it is now showing within your CNC.

http://xsw-inc.futurequest.net/, the temp url, will lead you to your site.[nbsp][nbsp]The IP address will not work as this site is not on a dedicated IP.

But yes, simply providing them with the current IP, 63.95.221.82, and having them change the old to the new should do the trick.

Deb
[nbsp]- It's a women's right...
[This message has been edited by Deb (edited 09-03-00@10:18 pm)]

[TDarlington]

I'm satisfied.[nbsp][nbsp]Thanks for the speedy response.[nbsp][nbsp]I'll see if I can prod those folks at NetReach into action.

Thomas