| Bug #827 | Access denied for user: kultur@localhost' (Using password: YES) | ||
|---|---|---|---|
| Submitted: | 10 Jul 2003 6:20 | Modified: | 6 Sep 2003 12:30 |
| Reporter: | Admin Admin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 4.1.0-alpha | OS: | Linux (Linux - Debian) |
| Assigned to: | Konstantin Osipov | CPU Architecture: | Any |
[10 Jul 2003 6:23]
Admin Admin
We only got the error if we are connected from the same IP-Address like a proxy or router. Stand alone its not possible to produce the error. Thx Matthias
[11 Jul 2003 6:14]
Jani Tolonen
This is a permission problem, a solution can be found from MySQL manual, chapter '4.2.11 Causes of Access denied Errors'. Regards, Jani
[11 Jul 2003 7:22]
Admin Admin
This is a permission problem, a solution can be found from MySQL manual, chapter '4.2.11 Causes of Access denied Errors I know this chapter. It is not a problem of the user and password. Access denies appear from the same interface which works fine (well, not all the time - that's the problem)
[12 Jul 2003 1:10]
Jani Tolonen
Reopened for further investigations. Regards, Jani
[15 Jul 2003 1:29]
Admin Admin
hi, I was able to reproduce the error with a simple shell-script. The script connects to the database and exits immediately. regards peter
[9 Aug 2003 10:19]
Manolo Gómez
I got that error while trying to connect to MySQL 4.1.0. Alpha from an VB6 app, using MyODBC 3.5. All running over Windows XP and in the same Intel PC I get an "Unsupported auth method. Please upgrade client" It disappears when I remove the password. Exactly the same occurs when connecting from MySQL Front or MySQLCC Manolo
[22 Aug 2003 6:43]
[ name withheld ]
I observed the same behavior. I use phpMyAdmin to administrate mysql server and when I click Home on the left frame sometimes I get Access denied error. Sometimes it is on of five, somtimes one of twenty clicks. The same I observe when running mysqldump command. I use script to dump individual tables from a database and mysqldump fails randomly always on different tables. I run self compiled lateset bk pull-ed mysql-4.1.1-alpha. Production version runs with no error with exactly same setup. Regards, Ing. Jozef Sakalos
[22 Aug 2003 6:53]
[ name withheld ]
Hi Jani, this bug is assigned Priority: Low and Severity: Non-critical. I'd like to let you know that for me it' priority: High and Severity: Critital. User can repeat an action if he gets Access Denied error but I run automated backup of data and I get random errors (whole tables missed from backup). Therefore, until this bug is fixed this version of mysql is unusable for me. Regards, Ing. Jozef Sakalos
[22 Aug 2003 9:20]
Sergei Golubchik
I wasn't able to repeat it having two scripts simultaneously connecting to mysqld server in an endless loop. can you show the result of SHOW GRANTS for this failing user ?
[22 Aug 2003 15:11]
[ name withheld ]
Yes, here is output of show grants for: Still I don't think it's a wrong grants problem - if wouldn't work at all. But, sometimes it works and sometimes not. I would hint the new encoding of passwords as it's different from production version. At least they seem different using select password from user; Grants for pmauser@% GRANT CREATE TEMPORARY TABLES, LOCK TABLES ON *.* TO 'pmauser'@'%' IDENTIFIED BY PASSWORD '468cdc9320ac086b' GRANT SELECT, INSERT, UPDATE, DELETE, CREATE TEMPORARY TABLES, LOCK TABLES ON `phpmyadmin`.* TO 'pmauser'@'%' GRANT SELECT ON `mysql`.`db` TO 'pmauser'@'%' GRANT SELECT ON `mysql`.`host` TO 'pmauser'@'%' GRANT SELECT (User, Column_priv, Table_priv, Table_name, Host, Db) ON `mysql`.`tables_priv` TO 'pmauser'@'%' GRANT SELECT (Create_priv, Delete_priv, Drop_priv, Execute_priv, Host, Select_priv, Super_priv, Lock_tables_priv, User, Insert_priv, Grant_priv, Shutdown_priv, Show_db_priv, References_priv, Alter_priv, File_priv, Reload_priv, Update_priv, Process_priv, Create_tmp_table_priv, Index_priv, Repl_slave_priv, Repl_client_priv) ON `mysql`.`user` TO 'pmauser'@'%' Regards, Ing. Jozef Sakalos
[23 Aug 2003 20:01]
[ name withheld ]
Here is the error message I get when trying to access the server from MySQL front or VB with user & pass not blank: "1249 - Client does not support authentication protocol requested by server. Consider upgrading MySQL client" Manolo
[25 Aug 2003 14:04]
Sergei Golubchik
ok, seems like it's something related to new password code. It'll be changed in 4.1.1. We'll try to double-check that this bug is not present in the new code.
[27 Aug 2003 2:55]
Michael Widenius
This bug reports is about two independent errors. The case with "Client does not support authentication protocol requested by server. Consider upgrading MySQL client" happens because the server is MySQL 4.1 which is using the new more secure autenticaion protocol and you are connecting with a client that is using client library older than 4.1.0 Possible fixes for this is one of the following: - Upgrade the client library to use the same version as the server. - Start mysqld with --old-passwords, which will force the server to use the old password format and the old autentication protocol. This is a good thing to do if you know old clients are going to access the server. When all clients are updated you can remove the --old-password option. The client will use the old autentication until you upgrade the passwords next time. - Update the users password with the OLD_PASSWORD() functions instead of PASSWORD(). You can find more information about this at: http://www.mysql.com/doc/en/Password_hashing.html About the second problem: - We need more information to be able to repeat this (maybe the script that was mentioned in the bug report would help). Note hower that we will very shortly update the autentication protocol for 4.1.1 becasue we found a security problem with the current one and the new one will be significantly faster than the current 4.1.0 version. This code will replace the 4.1.0 autentication and it's very likely that it will fix the other problems mentioned in this bug report. The new autentication code should be in the source repository within two week. Regards, Monty
[3 Sep 2003 11:21]
Konstantin Osipov
New authentication code is now pushed to the MySQL 4.1 repository. Similar tests were run against the server to ensure that the problem does not occur any more. Would you please check if your problem's been solved now?
[6 Sep 2003 2:42]
[ name withheld ]
Hi there, regarding the necessity to re-authenticate (phpMyAdmin fails from time to time) the problem seems to be solved. Thank you. Ing. Jozef Sakalos
[6 Sep 2003 12:30]
Konstantin Osipov
Then I'm closing the bug with the note: Fixed in 4.1.1 Feel free to reopen it if the problem will occur again.
[6 Sep 2003 12:30]
Konstantin Osipov
Fixed in 4.1.1
[17 Feb 2010 13:12]
prakash pmd
Access Denied is not open but i want to witch website of open any website for bloked and access denied. so please help this coment and do the needful. Regards Prakash prakash_pmd@rediffmail.com
Description: We are using MySQL-4.1.0-alpha on a Linux-Debian3(latest Version from June-2003) with the PHP-4.3.1 We compiled all that versions by hand. (like configure, make , make install) and also compiled the module mysql.so for PHP by hand As we work with a single user we got sometimes an error this is what i see in the mysql.log: 030710 14:33:18 17307 Connect kultur@localhost on 17307 Init DB kultur 17307 Query select user............ <-snip-> 030710 14:33:23 17308 Connect Access denied for user: kultur@localhost' (Using password: YES) 030710 14:35:01 17309 Connect kultur@localhost on 17309 Init DB kultur 17309 Query SELECT i........ <-snip-> The Logfile of PHP is empty as we are using the latest stable Version of PHP (4.3.2) there was no different of its behaivor. The my.cnf: -------------------- [client] port = 3306 socket = /tmp/mysql.sock [mysqld_safe] err-log = /var/log/mysql/mysql.err [mysqld] user = mysql pid-file = /var/run/mysqld/mysqld.pid port = 3306 log = /var/log/mysql/mysql.log log-error = /var/log/mysql/mysql.err basedir = /usr/local datadir = /usr/local/var tmpdir = /tmp skip-locking skip-networking set-variable = key_buffer=64M set-variable = max_allowed_packet=1M set-variable = thread_stack=128K set-variable = table_cache=256 set-variable = sort_buffer=4M set-variable = read_buffer_size=1M skip-name-resolve skip-host-cache set-variable = log_warnings=ON log-slow-queries = /var/log/mysql/mysql-slow.log skip-innodb [mysqld_safe] open-files-limit=8192 [mysqldump] quick set-variable = max_allowed_packet=1M [mysql] --------------------------------------- In the php.ini at the [MYSQL] part its all set to default. What information do you need more to fix or solve the Problem ? Greetings Matthias How to repeat: We could only repeat it by surfing on the same sites at the same time from 2 PC's. Suggested fix: What information do you need more to fix the Problem ?