Bug #64789 | "unauthenticated user" issue with rpc ypbind in mysql logs | ||
---|---|---|---|
Submitted: | 28 Mar 2012 17:51 | Modified: | 7 Oct 2012 19:28 |
Reporter: | Vaibhav Narula | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.1.55-log | OS: | Linux (5,2 & 5.8) |
Assigned to: | CPU Architecture: | Any |
[28 Mar 2012 17:51]
Vaibhav Narula
[31 Mar 2012 10:22]
Sveta Smirnova
Thank you for the report. I see no clnt_call, neither do_ypcall calls in MySQL server sources. Where does this log come from? Is it MySQL error log or some other? Please also explain in detail your environment: how LDAP authentication related to MySQL server in your installation?
[4 Apr 2012 16:37]
Vaibhav Narula
Thanks a lot for responding.I am seeing those errors in error.log and we are not using any ldap authentication for mysql but we are using ldap authentication for but when this happens we see unauthenticated users in the show processlist . Let me know if you need any other debug logs do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Timed out YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused YPBINDPROC_DOMAIN: Domain not bound
[4 Apr 2012 17:08]
Sveta Smirnova
Thank you for the feedback. Please send us full MySQL error log file.
[5 Apr 2012 2:33]
Vaibhav Narula
Errologs
Attachment: error.log (application/octet-stream, text), 481.11 KiB.
[5 Apr 2012 8:04]
Sveta Smirnova
Thank you for the feedback. Please provide your configuration file also: I want to check value of bind-address
[5 Apr 2012 14:47]
Vaibhav Narula
[mysql] #protect the socket file socket=/tmp/mysql.sock [mysqld] ## let mysql-proxy have default port #port=3307 port=3306 #make innodb as the default storage engine default-storage-engine=innodb #specify characterset for the database server character-set-server=utf8 #specify location for the data directory datadir=/apps/mysql/data #protect the socket file socket=/tmp/mysql.sock #innodb data files innodb_data_file_path=ibdata1:50M:autoextend user=mysql # base installation directory basedir=/apps/mysql/current # Slow Query Log to help diagnose DB performance issues slow_query_log = 1 slow_query_log_file = /apps/logs/mysql/slow-query.log long_query_time = 10 # Error log location log-error = /apps/logs/mysql/error.log # Binary logs -- replication & recovery #log-bin=/apps/mysql/logs/mysql-bin # binary logging format - mixed recommended #binlog_format=mixed pid-file=/apps/mysql/mysqld.pid #limit the size of packets sent or received max_allowed_packet=64M # query caching settings query_cache_limit = 16M query_cache_size = 256M query_cache_type = 1 max_connections = 600 table_cache=512 thread_cache=64 #forcing lower case characters lower_case_table_names =1 #Setting innodb bufferpool to 2 GB. If not specified, this defaults to just 8mb. innodb_buffer_pool_size=1073741824
[5 Apr 2012 14:48]
Vaibhav Narula
In host file i have the following setting and is calling like this 127.0.0.1 databasehost
[5 Apr 2012 19:49]
Sveta Smirnova
Thank you for the feedback. This reminds me bug #18810 Please check if ypbind, nscd and ldap is up and running. If they do I am afraid this is ypbind error: mysqld calls bind and getaddrinfo only and don't call any of do_ypcall or clnt_call directly.
[9 Apr 2012 18:02]
Vaibhav Narula
Sveta, Thanks a lot the feedback but its not happening at system startup but starts happening in middle of the time when there are calls going to the database and application layer and then we see unauthenticated users . Regards Vaibhav
[7 Sep 2012 19:28]
Sveta Smirnova
Thank you for the feedback. Please check with current version 5.1.65 and if problem still exists provide this user-related information from your LDAP configuration, so we can recreate environment similar to yours. Please also specify if this machine works as LDAP server.
[8 Oct 2012 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".