Too_many_connections

[Guest]

Hi


I´ve been running a toaster for a very long time, but suddenly today the server stopped delivering mail.

The maillog tells me this but I can´t see why and how to fix it....


Mar 10 16:56:49 mx1 qmail: 1078934209.060314 starting delivery 42: msg 111 to local mailto:waveit.com-kristian@waveit.com" target="_blank">waveit.com-kristian@waveit.com
Mar 10 16:56:49 mx1 qmail: 1078934209.061851 status: local 2/10 remote 0/200
Mar 10 16:56:49 mx1 qmail: 1078934209.075141 delivery 41: deferral: could_not_connect_to_mysql_update_server_Too_many_connections_with_database/could_not_connect_to_mysql_update_server_Too_many_connections/
Mar 10 16:56:49 mx1 qmail: 1078934209.083338 status: local 1/10 remote 0/200
Mar 10 16:56:51 mx1 qmail: 1078934211.149252 delivery 42: deferral: could_not_connect_to_mysql_update_server_Too_many_connections_with_database/could_not_connect_to_mysql_update_server_Too_many_connections/



Please help me.

[matt]

The quick fix is restarting the MySQL server. However, unless you got a freak one time spike of SQL load, it'll likely happen again.  It's time for you to spend some time learning MySQL.

Matt

[Guest]

Hi Matt


I´ve already tried the restart thingy;-) It doesn´t help me that much though...

The server gives me this error when doing the qmail doqueue (just for speeding things up)

Mar 11 00:37:50 mx1 qmail: 1078961870.186479 status: local 3/10 remote 2/200
Mar 11 00:37:50 mx1 qmail: 1078961870.194124 delivery 94: deferral: could_not_connect_to_mysql_update_server_Too_many_connections_with_database/vmysql:_sql_error[1]:_Can't_create_database_'vpopmail'._Database_exists/
Mar 11 00:37:50 mx1 qmail: 1078961870.194609 status: local 2/10 remote 2/200
Mar 11 00:37:50 mx1 qmail: 1078961870.202694 delivery 99: deferral: could_not_connect_to_mysql_update_server_Too_many_connections_with_database/could_not_connect_to_mysql_update_server_Too_many_connections/
Mar 11 00:37:50 mx1 qmail: 1078961870.203216 status: local 1/10 remote 2/200


I´m really out on the deep here... Not that great when a production server suddenly does this...



Best Regards
Kristian

[matt]

I didn't expect it would. MySQL will only allow so many connection attempts per second before it locks out a client, which you've just experienced.  

In general, this error will only ever get seen when there as been too many connection failures, not an excessive number of connections. I've literally beat the tar out of a MySQL server testing it's performance in a variety of lab settings and never gotten this error.

In the wild, I've only ever run into this on one occasion, and that was with a flakey network connection between the MySQL client and the MySQL server. The MySQL client couldn't get a stable connection and kept retrying frequently enough that the MySQL server throttled it.

This is only my experience. The problem could be different in the case but I'd expect some parallels. Again, it's time for you to become more familiar with the tools you are using, in this case, MySQL.