Comments on: Apache mod_proxy

By: Eric Lubow

Eric Lubow — Fri, 05 Mar 2010 22:19:01 +0000

If you can, log in via SSH to MySQL and then when you restart apache do a
“SHOW FULL PROCESSLIST” and wait for the outcome. Also leave a terminal
open with the command to kill apache already typed out so all you have to do
it hit enter after you get the response from “SHOW FULL PROCESSLIST”.
Although your issue may only be relegated to the one machine, it would still
be handy/interesting to know what caused in case you run into it again in
the future.

By: crirus

crirus — Fri, 05 Mar 2010 21:30:18 +0000

I can't tell for sure, the load increase almost instantly, I can barely ssh in to kill the web server. As soon as I do that the load goes down.

Very strange stuff, I tested same idea on a different box and everything is just fine there, lighttpd receive the proxy requests just fine.

No idea what happened to this first box.

By: crirus

crirus — Fri, 05 Mar 2010 21:29:49 +0000

missed the reply button below

By: Eric Lubow

Eric Lubow — Fri, 05 Mar 2010 21:06:38 +0000

While MySQL is going at 70%, what is happening? If you go into MySQL and type either “SHOW PROCESSLIST” or “SHOW FULL PROCESSLIST”, what does it say is happening? Are there a lot of open connections made and kept open by your application if you turn proxy off?

By: crirus

crirus — Fri, 05 Mar 2010 14:02:18 +0000

Hello

I've got the strangest thing ever.. when I set ProxyRequests Off my mysql is going at 70% of CPU.
I am forced to keep the apache proxy on.
Any hints?