One of our enterprise database servers (MySQL 4.0.16-max on Solaris 9) recently refused connections with a 1203 error, "User [username] has already more than 'max_user_connections' active connections".
Show variables like '%conn%' displayed:
+----------------------+-------+ | Variable_name | Value | +----------------------+-------+ | connect_timeout | 20 | | max_connections | 3000 | | max_connect_errors | 10 | | max_user_connections | 1800 | +----------------------+-------+
... and show status like '%conn%' displayed:
+----------------------+---------+ | Variable_name | Value | +----------------------+---------+ | Aborted_connects | 3174 | | Connections | 6058425 | | Max_used_connections | 1771 | | Threads_connected | 4 | +----------------------+---------+
Setting max_user_connections to 0 (zero), which according to the manual sets the variable to unlimited, allowed *no* connections. I upped max_user_connections to a higher value, but I don't understand why MySQL refused connections when there were no more than 4 threads connected to the database at the time the connection was refused.
Is this a known problem? Is there a solution?
- ian
-- | Ian Sales Unmetered & ADSL solutions | database administrator for Home & Business | PlusNet Technologies Ltd. @ http://www.plus.net + ----- My Referrals - It pays to recommend PlusNet -----
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.516 / Virus Database: 313 - Release Date: 01/09/2003
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
