本篇内容介绍了“MySQL could not be resolved: Temporary failure in name resolution报错的解决方法”的有关知识,在实际案例的操作过程中,不少人都会遇到这...
本篇内容介绍了“MySQL could not be resolved: Temporary failure in name resolution报错的解决方法”的有关知识,在实际案例的操作过程中,不少人都会遇到这样的困境,接下来就让小编带领大家学习一下如何处理这些情况吧!希望大家仔细阅读,能够学有所成!
最近几天研发总是抱怨用Navicat连接MySQL数据库和打开数据表很慢,登录数据库分析,查看错误日志:
mysql> show variables like 'log_error';
+---------------+--------------------------------+
| Variable_name | Value |
+---------------+--------------------------------+
| log_error | /usr/local/mysql/data/idb3.err |
+---------------+--------------------------------+
1 row in set (0.00 sec)
查看错误日志:
[root@idb3 data]# cat /usr/local/mysql/data/idb3.err | grep failure |more
2016-05-24 16:06:44 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:06:47 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:09:00 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:09:03 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
2016-05-24 16:09:14 11382 [Warning] IP address '172.31.19.113' could not be resolved: Temporary failure in name resolution
..........................................................................................................................
解决方法:
在mysql的配置文件my.cnf中
[mysqld]
节点添加下面两行
skip-host-cache
skip-name-resolve
参数解释如下:
skip-host-cache:禁用主机名缓存
skip-name-resolve:禁用主机名解析
然后重启MySQL数据库即可解决:
# service mysqld restart
“MySQL could not be resolved: Temporary failure in name resolution报错的解决方法”的内容就介绍到这里了,感谢大家的阅读。如果想了解更多行业相关的知识可以关注捷杰建站网站,小编将为大家输出更多高质量的实用文章!