[Derek Zeanah]

Try connecting to http://66.80.73.51 instead of the normal THR address and see if that works more cleanly.

Thanks.

[Derek Zeanah]

tell me if the problem went away first.

Made one more change, on the recommendation of an Apache guy...

[eoR]

Derek,

Both the normal address and the alternate you provided are slow for me.

Devin

[larryw]

Still getting "The page cannot be displayed" errors and slow response when a page is opened.

Second try to post this...

[cordex]

Darek,
That is the primary address I use at work. Still get slow and failed connections.

[Mike Irwin]

It's moving faster this morning, but is still slower than normal, as are a number of other sites I use regularly.

Over the last two days I've gotten a TON of SoBig viri e-mails. I'm wondering if the internet is still having problems in general...

[Duncan Idaho]

Both screaming fast for me now. No more errors.Page generated in 0.066285 seconds What ever you did seems to have worked, for me at least.

I'm on cable in WA state.

[cordex]

Mike,
I've been getting a boatload from a specific IP (142.179.156.106). You might check for persistant IPs and then report the infection to the ISP. Can't hurt, anyway.

[PenHolder]

I don't know if this helps or not, but:

1) I too have been experiencing the infamous "THR slowdown" for quite some time now. As others have noted, web pages fail to load, but hitting "reload" causes them to come up right away. In fact, when the site fails to respond after only 1-2 seconds, just hitting "stop" and "reload" almost always brings the page up at usual speed.

2) Whenever the site seems to be failing to respond and I've checked the status of the relevant connections, I see TCP connections to THR sitting in the SYN_SENT state, for a relatively long time:


Active Internet connections
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 xxx.xx.xx.xxx.zzzz 66.80.73.51.80 SYN_SENT


The SYN_SENT state is the client state right after the client starts to initiate a connection; it occurs before the connection is setup, hence before the client has sent the HTTP request. Unless the server is doing some very unconventional things, at this point in the connection, Apache is totally unaware of it.

Strickly from what I can see at this end, it appears as if the client's initial SYN or the server's responding SYN-ACK are being dropped or ignored at lower layers in the network. If the server never receives some SYNs, or ignores them for some reason (such as low-level resource constraints in the kernel), it will seem as if the corresponding clients don't even exist. If something is eating the SYN-ACKs -- or if you're under a SYN-flood attack -- then the server will show an unusual number of connections in the SYN_RCVD state.

Hope this helps,

-PH

[OF]

Yeah, what he said. I was just going to say that but he beat me to it.

;)

- Gabe

[gun-fucious]

the Automag Owners forum was under zombie attack this weekend:
http://www.automags.org/forums/showthread.php?s=&threadid=100526

[gun-fucious]

actually they were slashdotted


>>>>>>>>>>>>>>>>>

The latest thoughts on all this was that we had a particularly popular thread that ended up getting linked all over the net. Everyone linking here from another site automatically got guest status. The thing spread from one forum to another until we were over cooked. We no longer think it was a malicous attack just coincidence. We will allow guests again when the linking dies down.

[OF]

Server responding much better for me now. There was no change immediately following the reboot, but now it's responding normally.

Previously, I would often have to click a link twice to get it to function (first click = nothing, second click = works every time). Now it's running well.

- Gabe

[Derek Zeanah]

but now it's responding normally.Good. That's what we were looking for.

Anyone else think things look better? Anyone think things are still screwy?

[Larry Ashcraft]

It's been getting better all afternoon, but still loading slower than normal.

[BryanP]

Just using the regular URL it's better today than it has been, but I'm still regularly having to double-click or get a timeout error. It's just annoying as opposed to nearly unusable like it was a couple of days ago.

[OF]

Agreed. It's still a bit slow - and occasionally I'm having to hit a link or button twice to get a response.

But it's better.

- Gabe

[C.R.Sam]

Mo bettah from here.
Not totally smooth but very workable now.
thanks Derek.

Sam