Your message dated Wed, 08 Sep 2010 13:21:23 +0300
with message-id <[email protected]>
and subject line Closing very old Mysqld bugs (fixed during the etch cycle)
has caused the Debian Bug report #320020,
regarding mysqld: Incorrect "exceeded the 'max_connections' resource (current
value: 40)"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
320020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320020
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server
Version: 4.0.24-10
Severity: important
Hello,
unfortunately case 'B' from bug #285044 still exists, I was able to track it
down a little bit on my all sarge machine.
About 50% of my users have the following limits set (set in phpmyadmin user
permissions/ressource limits and also show up in mysql users table):
max_questions 50000
max_updates 20000
max_connections 5000
other users have no limits set (all limits 0).
After a full stop and start of mysqld (also on complete server reboot) the
max_connection limit for the users set is not 5000 as specified in the mysql
users table but only 40 (!). Users with no limits set have none of these
problems.
DBI connect('database=usr_test_1;host=localhost','test',...) failed: User
'test' has exceeded the 'max_connections' resource (current value: 40) at
./dbconnect.pl line 18
The same is true if the max_connections limit is set to 45, 102, 4000 and
8888, mysqld always denies after the 40th connect per hour (and also always
shows a limit of 40 in the error response).
If I start mysql, reload the user table manually a couple of times it does
not change anything, the limit remains 40.
Now the strange: If a user reaches the limit of 40, gets locked and I reload
the user table manually (eg in phpmyadmin) to unlock him the limit is reset
to the real value in the users table (eg 45, 102, 4000, 8888,...), but only
for users that were locked before, other users stay on a limit of 40 (until
they reach the limit and the user table is reloaded).
Now the even more strange: If the max_connections limit is set to a number
smaller than 40 (eg. 35) it is taken on mysql start and works as expected
(little bit low ;-)
Commenting out the automatic table check on start while testing did not
change anything with the limits.
I will keep testing on the max_questions and max_updates limits, maybe there
hide similar problems on a higher value.
Any chance to get a fix in sarge r1 or r2 ?
Best regards, René
--- End Message ---
--- Begin Message ---
Version: 4.1.7-1
This bug was reported back when the bts didn't have version tracking, and the
maintainer apparently forgot to close this bug when etch was released.
The maintainer claims in the bug report log that this bug was fixed in
upstream Mysql 4.1, the first 4.1 series version uploaded to Debian unstable
was 4.1.7-1.
--
Arto Jantunen
--- End Message ---
