Hi Jeff.
If you are the admin, then maybe you and only one or two
others should have the 'Super' privilege.
>From the 5.0.18 manual:
13.5.4.16. SHOW PROCESSLIST Syntax
SHOW [FULL] PROCESSLIST
SHOW PROCESSLIST shows you which threads are running. You
can also get this information using the mysqladmin
processlist statement. If you have the SUPER privilege, you
can see all threads. Otherwise, you can see only your own
threads (that is, threads associated with the MySQL account
that you are using). See Section 13.5.5.3, KILL Syntax. If
you do not use the FULL keyword, only the first 100
characters of each statement are shown in the Info field.
This statement is very useful if you get the too many
connections error message and want to find out what is going
on. MySQL reserves one extra connection to be used by
accounts that have the SUPER privilege, to ensure that
administrators should always be able to connect and check
the system (assuming that you are not giving this privilege
to all your users).
The output of SHOW PROCESSLIST may look like this:
Also, what about checking your logs for the rogue
connections. Would there be any clues there?
What about this also from the 5.0.18 manual:
5.9.4. Limiting Account Resources
One means of limiting use of MySQL server resources is to
set the max_user_connections system variable to a non-zero
value. However, this method is strictly global, and does not
allow for management of individual accounts. In addition, it
limits only the number of simultaneous connections made
using a single account, and not what a client can do once
connected. Both types of control are interest to many MySQL
administrators, particularly those working for Internet
Service Providers.
In MySQL 5.0, you can limit the following server resources
for individual accounts:
The number of queries that an account can issue per hour
The number of updates that an account can issue per hour
The number of times an account can connect to the server per
hour
Regards
Keith
In theory, theory and practice are the same;
in practice they are not.
To unsubscribe from this list, please see detailed
instructions already posted at:
http://marc.theaimsgroup.com/?l=php-install&m=114138567814319&w=2
On Fri, 14 Apr 2006, Jeff wrote:
> To: mysql@lists.mysql.com
> From: Jeff <[EMAIL PROTECTED]>
> Subject: Out of control connections
>
> Hello all,
>
> I've got a problem where a php web application is intermitantly making
> bursts of 500+ connections to a mysql database which then locks out all
> other connections. These connection don't apparently do anything query
> wise they just use up connections. The problem is when it happens I
> can't get a processlist to see what user is causing it due to too many
> connection and therefore track down the offending web app. I can do a
> netstat but that only confirms which web server the out of controll
> connections are coming from.
>
> The connections then just die off on their own in about a minute. Does
> anyone know of any way I can log these connections or some other way of
> catching it in progress from myslq so I can figure out which website is
> causing it and then go correct the code?
>
> Thanks,
>
> Jeff
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
