[BlueOnyx:03635] Re: Tips for tracking down rogue mysqlconnection use?

[Rodrigo Ordonez Licona]

It might also mean that you application is very successful, 

In my case this happened when we passed 100 users ,

Had to add a script that ran this against mysql, after a reboot.
set global max_connections=2000;
set global max_allowed_packet=16777216;

The second max allowed apcket was to allowed  the post of big chunlks of
data to mysql (images)


You can check connections to mysql with 
netstat -an | grep 3306


HTH

Rodrigo O
Xnet



-----Original Message-----
From: blueonyx-bounces at blueonyx.it [mailto:blueonyx-bounces at blueonyx.it] On
Behalf Of Jeff Jones
Sent: Jueves, 18 de Febrero de 2010 11:44
To: BlueOnyx General Mailing List
Subject: [BlueOnyx:03629] Re: Tips for tracking down rogue mysqlconnection
use?

Yes, sorry, should have mentioned that this is an 'all in one'  
dedicated box running LAMP - with no external ports but 80, 443 open to the
Internet. MySQL only accepts connections from localhost.

Thankfully each website on this server has it's own dbuser account so
looking for which user has loads of connections will really help!

Thanks for the tips!

Jeff

Sent from my iPhone

On 19 Feb 2010, at 06:02, Michael Stauber <mstauber at blueonyx.it> wrote:

> Hi Chris,
>
>> There's really no reason to be
>> allowing remote MySQL connections to the public at-large.
>
> Indeed. My typical firewall also closes down port 3306 to prevent 
> remote MySQL connections. And if need be, exceptions can be made for 
> hosts that require remote access.
>
> -- 
> With best regards
>
> Michael Stauber
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
_______________________________________________
Blueonyx mailing list
Blueonyx at blueonyx.it
http://www.blueonyx.it/mailman/listinfo/blueonyx