openstack给keystone同步数据库出错WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 8 attempts le

最新推荐文章于 2023-09-15 10:50:33 发布
原创 最新推荐文章于 2023-09-15 10:50:33 发布 · 9.5k 阅读 · 4 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#openstack

本文记录了在执行Keystone数据库同步过程中遇到的连接失败问题，并提供了详细的错误日志及解决方法，即通过修改控制器节点上的/etc/hosts文件来解决数据库连接问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

执行su -s /bin/sh -c “keystone-manage db_sync” keystone 报错

解决方法：

· 在controller节点上，修改 /etc/hosts
添加:
192.168.221.101 controller

注意，192.168.221.101是controller节点的ip，请根据自己的更改 ·

报错如下：

Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
     * Setting up iSCSI targets
   ...done.
2013-12-02 11:56:28  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 10 attempts left.
2013-12-02 11:56:41  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 9 attempts left.
2013-12-02 11:56:54  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 8 attempts left.
2013-12-02 11:57:07  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 7 attempts left.
2013-12-02 11:57:20  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 6 attempts left.
2013-12-02 11:57:33  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 5 attempts left.
2013-12-02 11:57:46  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 4 attempts left.
2013-12-02 11:57:59  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 3 attempts left.
2013-12-02 11:58:12  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 2 attempts left.
2013-12-02 11:58:25  WARNING [cinder.db.sqlalchemy.session] SQL connection failed. 1 attempts left.
2013-12-02 11:58:38 CRITICAL [cinder] (OperationalError) (2003, "Can't connect to MySQL server on '172.30.0.200' (113)") None None
Traceback (most recent call last):
  File "/usr/bin/cinder-manage", line 794, in <module>
    main()
  File "/usr/bin/cinder-manage", line 791, in main
    fn(*fn_args)
  File "/usr/bin/cinder-manage", line 219, in sync
    return migration.db_sync(version)
  File "/usr/lib/python2.7/dist-packages/cinder/db/migration.py", line 33, in db_sync
    return IMPL.db_sync(version=version)
  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/migration.py", line 76, in db_sync
    current_version = db_version()
  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/migration.py", line 88, in db_version
    return versioning_api.db_version(get_engine(), repository)
  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/session.py", line 138, in get_engine
    _ENGINE.connect()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2471, in connect
    return self._connection_cls(self, **kwargs)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 878, in __init__
    self.__connection = connection or engine.raw_connection()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2557, in raw_connection
    return self.pool.unique_connection()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 184, in unique_connection
    return _ConnectionFairy(self).checkout()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 401, in __init__
    rec = self._connection_record = pool._do_get()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 746, in _do_get
    con = self._create_connection()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 189, in _create_connection
    return _ConnectionRecord(self)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 282, in __init__
    self.connection = self.__connect()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/pool.py", line 344, in __connect
    connection = self.__pool._creator()
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py", line 80, in connect
    return dialect.connect(*cargs, **cparams)
  File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 281, in connect
    return self.dbapi.connect(*cargs, **cparams)
  File "/usr/lib/python2.7/dist-packages/MySQLdb/__init__.py", line 81, in Connect
    return Connection(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 187, in __init__
    super(Connection, self).__init__(*args, **kwargs2)
OperationalError: (OperationalError) (2003, "Can't connect to MySQL server on '172.30.0.200' (113)") None None
0+0 records in
0+0 records out
0 bytes (0 B) copied, 1.2862e-05 s, 0.0 kB/s
  Physical volume "/dev/loop2" successfully created
  Volume group "cinder-volumes" successfully created
cinder-api stop/waiting
cinder-api start/running, process 18907
cinder-scheduler stop/waiting
cinder-scheduler start/running, process 18918
stop: Unknown instance: 
cinder-volume start/running, process 18929

或者是这样报错

fatal: [controller]: FAILED! => {"changed": true, "cmd": "su -s /bin/sh -c \"keystone-manage db_sync\" keystone", "delta": "0:01:44.650785", "end": "2017-12-07 12:09:09.043452", "msg": "non-zero return code", "rc": 1, "start": "2017-12-07 12:07:24.392667", "stderr": "2017-12-07 12:07:28.645 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 10 attempts left.\n2017-12-07 12:07:38.658 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 9 attempts left.\n2017-12-07 12:07:48.669 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 8 attempts left.\n2017-12-07 12:07:58.683 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 7 attempts left.\n2017-12-07 12:08:08.689 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 6 attempts left.\n2017-12-07 12:08:18.702 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 5 attempts left.\n2017-12-07 12:08:28.714 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 4 attempts left.\n2017-12-07 12:08:38.726 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 3 attempts left.\n2017-12-07 12:08:48.738 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 2 attempts left.\n2017-12-07 12:08:58.758 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 1 attempts left.\n2017-12-07 12:09:08.771 11174 CRITICAL keystone [-] DBConnectionError: (pymysql.err.OperationalError) (2003, \"Can't connect to MySQL server on 'controller' ([Errno 111] Connection refused)\")\n2017-12-07 12:09:08.771 11174 ERROR keystone Traceback (most recent call last):\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/bin/keystone-manage\", line 10, in <module>\n2017-12-07 12:09:08.771 11174 ERROR keystone     sys.exit(main())\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/cmd/manage.py\", line 44, in main\n2017-12-07 12:09:08.771 11174 ERROR keystone     cli.main(argv=sys.argv, config_files=config_files)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py\", line 1294, in main\n2017-12-07 12:09:08.771 11174 ERROR keystone     CONF.command.cmd_class.main()\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py\", line 461, in main\n2017-12-07 12:09:08.771 11174 ERROR keystone     CONF.command.version)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py\", line 207, in offline_sync_database_to_version\n2017-12-07 12:09:08.771 11174 ERROR keystone     expand_schema()\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py\", line 232, in expand_schema\n2017-12-07 12:09:08.771 11174 ERROR keystone     _sync_common_repo(version=None)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py\", line 123, in _sync_common_repo\n2017-12-07 12:09:08.771 11174 ERROR keystone     with sql.session_for_write() as session:\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/contextlib.py\", line 17, in __enter__\n2017-12-07 12:09:08.771 11174 ERROR keystone     return self.gen.next()\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 874, in _transaction_scope\n2017-12-07 12:09:08.771 11174 ERROR keystone     allow_async=self._allow_async) as resource:\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/contextlib.py\", line 17, in __enter__\n2017-12-07 12:09:08.771 11174 ERROR keystone     return self.gen.next()\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 518, in _session\n2017-12-07 12:09:08.771 11174 ERROR keystone     bind=self.connection, mode=self.mode)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 277, in _create_session\n2017-12-07 12:09:08.771 11174 ERROR keystone     self._start()\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 363, in _start\n2017-12-07 12:09:08.771 11174 ERROR keystone     engine_args, maker_args)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 387, in _setup_for_connection\n2017-12-07 12:09:08.771 11174 ERROR keystone     sql_connection=sql_connection, **engine_kwargs)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py\", line 155, in create_engine\n2017-12-07 12:09:08.771 11174 ERROR keystone     test_conn = _test_connection(engine, max_retries, retry_interval)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py\", line 339, in _test_connection\n2017-12-07 12:09:08.771 11174 ERROR keystone     six.reraise(type(de_ref), de_ref)\n2017-12-07 12:09:08.771 11174 ERROR keystone   File \"<string>\", line 2, in reraise\n2017-12-07 12:09:08.771 11174 ERROR keystone DBConnectionError: (pymysql.err.OperationalError) (2003, \"Can't connect to MySQL server on 'controller' ([Errno 111] Connection refused)\")\n2017-12-07 12:09:08.771 11174 ERROR keystone ", "stderr_lines": ["2017-12-07 12:07:28.645 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 10 attempts left.", "2017-12-07 12:07:38.658 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 9 attempts left.", "2017-12-07 12:07:48.669 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 8 attempts left.", "2017-12-07 12:07:58.683 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 7 attempts left.", "2017-12-07 12:08:08.689 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 6 attempts left.", "2017-12-07 12:08:18.702 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 5 attempts left.", "2017-12-07 12:08:28.714 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 4 attempts left.", "2017-12-07 12:08:38.726 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 3 attempts left.", "2017-12-07 12:08:48.738 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 2 attempts left.", "2017-12-07 12:08:58.758 11174 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 1 attempts left.", "2017-12-07 12:09:08.771 11174 CRITICAL keystone [-] DBConnectionError: (pymysql.err.OperationalError) (2003, \"Can't connect to MySQL server on 'controller' ([Errno 111] Connection refused)\")", "2017-12-07 12:09:08.771 11174 ERROR keystone Traceback (most recent call last):", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/bin/keystone-manage\", line 10, in <module>", "2017-12-07 12:09:08.771 11174 ERROR keystone     sys.exit(main())", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/cmd/manage.py\", line 44, in main", "2017-12-07 12:09:08.771 11174 ERROR keystone     cli.main(argv=sys.argv, config_files=config_files)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py\", line 1294, in main", "2017-12-07 12:09:08.771 11174 ERROR keystone     CONF.command.cmd_class.main()", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/cmd/cli.py\", line 461, in main", "2017-12-07 12:09:08.771 11174 ERROR keystone     CONF.command.version)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py\", line 207, in offline_sync_database_to_version", "2017-12-07 12:09:08.771 11174 ERROR keystone     expand_schema()", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py\", line 232, in expand_schema", "2017-12-07 12:09:08.771 11174 ERROR keystone     _sync_common_repo(version=None)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/keystone/common/sql/migration_helpers.py\", line 123, in _sync_common_repo", "2017-12-07 12:09:08.771 11174 ERROR keystone     with sql.session_for_write() as session:", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/contextlib.py\", line 17, in __enter__", "2017-12-07 12:09:08.771 11174 ERROR keystone     return self.gen.next()", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 874, in _transaction_scope", "2017-12-07 12:09:08.771 11174 ERROR keystone     allow_async=self._allow_async) as resource:", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/contextlib.py\", line 17, in __enter__", "2017-12-07 12:09:08.771 11174 ERROR keystone     return self.gen.next()", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 518, in _session", "2017-12-07 12:09:08.771 11174 ERROR keystone     bind=self.connection, mode=self.mode)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 277, in _create_session", "2017-12-07 12:09:08.771 11174 ERROR keystone     self._start()", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 363, in _start", "2017-12-07 12:09:08.771 11174 ERROR keystone     engine_args, maker_args)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py\", line 387, in _setup_for_connection", "2017-12-07 12:09:08.771 11174 ERROR keystone     sql_connection=sql_connection, **engine_kwargs)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py\", line 155, in create_engine", "2017-12-07 12:09:08.771 11174 ERROR keystone     test_conn = _test_connection(engine, max_retries, retry_interval)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py\", line 339, in _test_connection", "2017-12-07 12:09:08.771 11174 ERROR keystone     six.reraise(type(de_ref), de_ref)", "2017-12-07 12:09:08.771 11174 ERROR keystone   File \"<string>\", line 2, in reraise", "2017-12-07 12:09:08.771 11174 ERROR keystone DBConnectionError: (pymysql.err.OperationalError) (2003, \"Can't connect to MySQL server on 'controller' ([Errno 111] Connection refused)\")", "2017-12-07 12:09:08.771 11174 ERROR keystone "], "stdout": "", "stdout_lines": []}
openstak各种服务同步数据库出错问题
controllerha的博客
12-03 4433
一般来说首先想到的是配置文件下[database]中connection（配置数据库连接）的设置问题数据库名字啊，连接对象啊。 但是有时候检查却发现没有错，那么多半就是创建那个服务数据库时出错比如数据库名字问题啊，授予权限问题 通常只要把connection连接确定，大不了删掉数据库重新创建赋值便可以 我发现同步keystone的数据库还有种坑人情况，就算你connection写错了
openstack mysql起不来_openstack是如何修复mysql问题
weixin_33561350的博客
01-21 644
openstack是如何修复mysql问题发布时间：2020-04-30 15:42:14来源：亿速云阅读：173作者：三月栏目：数据库本文主要给大家介绍openstack是如何修复mysql问题，文章内容都是笔者用心摘选和编辑的，openstack是如何修复mysql问题具有一定的针对性，对大家的参考意义还是比较大的，下面跟笔者一起了解下主题内容吧。同事一台openstack单节点云服务器由于未...
keystone执行报错WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed
linuxvfast的博客
06-24 1407
su -s /bin/sh -c "keystone-manage db_sync" keystone执行报错 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed https://blog.csdn.net/cow66/article/details/78714899
python连接mysql数据库报错pymysql.err.OperationalError
liu_xue_xue的专栏
09-15 4798
2、可能新版mysql默认使用的caching_sha2_password认证方式，换成mysql_native_password就可以。2、进入msql服务，执行mysql -u root -p 回车，输入密码，也可以通过navicat/DBeaver连接数据库。优化思考，一般程序里头不会直接使用root，权限范围过大，这里新建用户，并授予特定数据库权限，供ai服务使用。1、创建账号：ai_user，密码：pw@666的用户。4、刷新内存，重新加载权限信息。3、刷新内存，重新加载权限信息。
python使用sqlalchemy和pymysql连接mysql报错err(1055)解决方法
weixin_63009611的博客
02-20 1446
出现的变量值中没有only_full_group_by的字段说明修改正确。提高sqlalchemy和pymsyql版本。
OpenStack公共组件oslo之九——oslo.db
上善若水的木偶戏
11-22 6773
本文对oslo.db的实现与使用方法进行了详细分析，阐明了oslo.db如何与SQLAlchemy框架结合为OpenStack各组件提供数据库连接与操作。
openstack mysql 故障_Openstack mysql自发连接错误2006，“mysql服务器已经离开
weixin_39956558的博客
02-08 1061
我正在openstack ansible部署上运行openstackqueens，最近我发现很多组件，比如nova&Neuton，开始在日志中抛出以下错误堆栈，一切正常，但是这个错误让我担心，有人知道这一点吗？在我有检查基本的东西，像F5LB，MySQL，网络连接都很好。在2018-08-13 10:36:23.552 17533 ERROR oslo_db.sqlalchemy.engi...
Openstack配置常见错误
sunSHINEEzy的博客
04-20 3179
碰到哪些Bug可以留言到评论区，我会定期查看BUG并给予反馈 1. 配置keystone时: su -s /bin/sh -c "keystone-manage db_sync" keystone 2017-11-05 18:04:23.307 7286 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 10 atte...
OpenStack 计算节点加入失败： oslo_service.service nova.exception.ServiceTooOld: This service is older (v51) t
哈哈虎的博客
11-21 2208
OpenStack 安装完之后，再找一个虚拟机作为 compute2 加入，奇怪的是，nove service 怎么都加不上，而 networking 倒是没有什么问题 原来是没有单独加入 add-apt-repository cloud-archive:xena
openstack_rocky.tar.gz
10-21
OpenStack是一个开源的云计算平台，用于构建私有云和公共云服务。它的设计目标是提供一个基础设施即服务（IaaS）的解决方案，让组织能够在其硬件上创建和管理计算、存储和网络资源。"OpenStack_Rocky"是OpenStack的...
sql warning报错出错信息说明
10-03
错误 严重度 描述（消息文本） 1 10 上次升级的版本日期: 10/11/90. 21 10 警告:严重错误 %1! 发生于 %2!。请记下错误和时间，然后与系统管理员联系。 102 15 在 ''%1!'' 附近有语法错误。 103 15 以 ''%2!'' 开头的 %1! 太长。最大长度为 %4!。 104 15 如果语句中包含 UNION 运算符，那么 ORDER BY 子句中的项就必须出现在选择列表中。 105 15 字符串 ''%1!'' 之前有未闭合的引号。 106 16 查询中的表名太多。允许的最大数目为 %1!。 ........... .............
oslo_db与sqlalchemy的应用
上官栋
05-14 854
sqlalchemy是python中对象关系模型的实现库，就是将数据库的每一条记录在查询时转化为一个类实例。而oslo_db是OpenStack中对于数据库的封装，应用的也是sqlalchemy。在说明使用方法之前，先谈目录的编排方式： 文件目录 --db |--__init__.py |--api.py |--sqlalchemy |--__init__.py |--api.py |--models.py 从目录上可以看出对于oslo_db，数据库经过了多层封装
openstack常常会入的坑
weixin_45697293的博客
04-16 2110
文章目录配置的时候重启之后常见错误ERROR oslo.messaging._drivers.impl_rabbi 配置的时候 在配置nova时 常常会出现一些莫名其妙的问题（启动不起来） 首先查看自己安装的包是不是—自己所需要的版本（比如说T版本tr ain） 在每个控制节点，计算节点，重新使用yum看一遍，所安装的包是不是同意版本的（T） 如果不同，说明yum源有问题，就需要统一yum源 并且删掉rdo源-----可能会导致版本过新 建议： 在配置控制节点和计算节点的时候----配置都一致 并且都有
keystone的mysql无法进入,keystone同步时无法连接数据库的失败解决方法
weixin_39528559的博客
03-16 829
问题：root@swift:/etc/mysql/mariadb.conf.d# su -s /bin/sh -c "keystone-manage db_sync" keystone2017-05-17 21:38:28.105 5553 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. 10 attempts left....
安装openstack时碰到的错误
热门推荐
gsl371的专栏
12-05 2万+
目录 安装keystone identity时遇到的错误信息 glance验证操作错误信息 计算节点安装openstack-nova-compute找不到包 openstack-nova-compute安装后服务起不来 openstack-nova-compute安装后验证没有输出 dashboard安装后打不开 OpenStack云平台涉及到的相关服务进程的日志记录的默认存放地址 总结
sqlalchemy 连接数据库报错 Background on this error at: http://sqlalche.me/e/e3q8
eerywh的博客
01-11 1万+
from sqlalchemy import create_engine engine = create_engine( 'mysql+pymysql://user:password@1.1.1.1:3306') con = engine.connect() 报错： Background on this error at: http://sqlalche.me/e/e3q8 【解决方法】 engine = create_engine( 'mysql+pymysql://user:pass
mysql 访问失败_MySQL 性能瓶颈导致访问失败
weixin_36366711的博客
01-19 432
作者：Maxwell Li日期：2017/01/20未经作者允许，禁止转载本文任何内容。如需转载请留言。问题发现近段时间 Compass4NFV 物理部署 OpenStack Newton Ubuntu 极其不稳定，各种常见的不常见的概率性问题频发，提高代码稳定性与部署成功率刻不容缓。1月20日，发现 aodh 在进行数据库同步时失败，而且仅仅出现在 huawei-pod2 和 intel-pod...
openstack neutron日志报错2025-03-28 05:41:04.618 3507 WARNING oslo_db.sqlalchemy.engines [req-7f76d042-321a-42f1-b28d-3260fa8271dd - - - - -] SQL connection failed. 1 attempts left.: oslo_db.exception.DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '192.168.44.100' ([Errno 111] ECONNREFUSED)")
最新发布
03-28
<think>嗯，用户遇到了OpenStack Neutron组件中的MySQL连接被拒绝的问题，错误是pymysql.err.OperationalError Errno 111 ECONNREFUSED。我需要先分析可能的原因，然后给出解决方案。 首先，ECONNREFUSED通常意味着无法连接到目标地址和端口。可能的原因包括MySQL服务未运行、配置错误、防火墙设置或权限问题。用户提到修改过mysql.sock的路径，可能导致了socket文件不匹配。需要检查Neutron配置文件中的数据库连接字符串是否正确，特别是socket路径或主机地址是否正确。 然后，要确认MySQL服务是否在运行，可以通过systemctl status mysql查看状态。如果服务没启动，需要启动服务。另外，检查MySQL是否监听正确的地址和端口，netstat命令可以查看。如果MySQL只绑定了本地地址，而Neutron配置使用的是IP地址，可能需要修改bind-address为0.0.0.0。 还要检查防火墙设置，确保3306端口开放。SELinux也可能阻止连接，需要暂时禁用或调整策略。用户权限方面，确认Neutron使用的数据库用户是否有权限从指定主机访问，可能需要GRANT命令授权。 日志排查也很重要，查看Neutron的日志和MySQL的错误日志，找到更详细的错误信息。最后，测试连接，使用mysql命令尝试连接，确认凭证和网络可达性。 用户之前修改过socket路径导致过错误，所以需要特别注意配置文件中的socket路径是否正确。可能还需要检查my.cnf中的socket配置是否和Neutron配置一致。同时，引用中的例子显示修改socket路径后出现连接问题，所以必须确保所有相关配置一致。 总结下来，步骤应该是检查服务状态，配置文件中的连接信息，网络和权限设置，以及日志分析。可能需要一步步排除每个可能性，从服务是否运行开始，到配置是否正确，再到网络和权限问题。</think>### OpenStack Neutron MySQL连接被拒问题排查步骤 #### 1. 验证MySQL服务状态 首先检查MySQL服务是否正常运行： ```bash systemctl status mysql # 适用于systemd系统 service mysql status # 适用于SysVinit系统 ps -ef | grep mysqld # 检查进程是否存在 ``` 如果服务未运行，使用`systemctl start mysql`启动服务[^1]。 #### 2. 检查连接配置 在Neutron配置文件（通常为`/etc/neutron/neutron.conf`）中确认数据库连接字符串： ```ini [database] connection = mysql+pymysql://neutron:密码@控制节点IP/neutron?charset=utf8 ``` 重点检查： - IP地址是否为MySQL服务器真实地址 - 端口是否明确指定（默认3306） - 用户名密码是否与MySQL记录一致 #### 3. 网络连通性验证 使用telnet测试端口可达性： ```bash telnet 控制节点IP 3306 ``` 如果连接失败，检查： ```bash iptables -L -n | grep 3306 # 查看防火墙规则 netstat -antp | grep 3306 # 查看监听状态 ``` MySQL配置需包含： ```ini [mysqld] bind-address = 0.0.0.0 # 允许远程连接 ``` #### 4. 权限配置检查 在MySQL中执行： ```sql SHOW GRANTS FOR 'neutron'@'%'; ``` 若缺少权限，需执行授权： ```sql GRANT ALL PRIVILEGES ON neutron.* TO 'neutron'@'%' IDENTIFIED BY '密码'; FLUSH PRIVILEGES; ``` #### 5. Socket文件校验（本地连接时） 当使用本地socket连接时： ```ini [database] connection = mysql+pymysql://neutron:密码@localhost/neutron?unix_socket=/var/lib/mysql/mysql.sock ``` 需确保： ```bash ls -l /var/lib/mysql/mysql.sock # 检查socket文件存在性 ``` 注意该路径需与`my.cnf`中的`socket`配置一致。 #### 6. 日志分析 关键日志位置： ```bash /var/log/neutron/*.log # Neutron服务日志 /var/log/mysql/error.log # MySQL错误日志 ``` 典型错误线索： ``` Can't connect to MySQL server on '10.0.0.11' (111) # 网络层连接失败 Access denied for user 'neutron'@'compute-node' # 权限问题 ``` #### 7. 测试连接 手动验证连接有效性： ```bash mysql -uneutron -p密码 -h 控制节点IP -P 3306 -D neutron ``` ### 典型解决方案示例 某环境因MySQL配置错误导致的问题解决过程： 1. 发现`SHOW VARIABLES LIKE 'bind_address'`返回`127.0.0.1` 2. 修改`my.cnf`设置`bind-address=0.0.0.0` 3. 执行`mysql> CREATE USER 'neutron'@'%' IDENTIFIED BY 'new_password';` 4. 重启MySQL服务后连接恢复正常[^1][^2]
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值