cinder_api报错

最新推荐文章于 2023-11-23 11:11:20 发布
最新推荐文章于 2023-11-23 11:11:20 发布
阅读量1.1k 收藏
点赞数 1
分类专栏： openstack 文章标签： openstack
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/skyroach/article/details/103872165
版权

OpenStack queens版本安装cinder后报错

1.cinder_api报错日志内容

2019-07-29 23:09:27.663 28685 INFO cinder.api.openstack.wsgi [req-d910b210-0bd0-4056-a5d2-3945937c4091 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] GET http://controller:8776/v2/cf080665b3e54c8b8456ee1b7f66cf9c/os-volume-transfer/detail?bootable=1&status=available
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines [req-d910b210-0bd0-4056-a5d2-3945937c4091 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] Database connection was found disconnected; reconnecting: DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'SELECT 1'] (Background on this error at: http://sqlalche.me/e/e3q8)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines Traceback (most recent call last):
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/engines.py", line 73, in _connect_ping_listener
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     connection.scalar(select([1]))
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 880, in scalar
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     return self.execute(object, *multiparams, **params).scalar()
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 948, in execute
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     return meth(self, multiparams, params)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     return connection._execute_clauseelement(self, multiparams, params)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     compiled_sql, distilled_params
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     context)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1409, in _handle_dbapi_exception
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     util.raise_from_cause(newraise, exc_info)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     reraise(type(exception), exception, tb=exc_tb, cause=cause)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     context)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     cursor.execute(statement, parameters)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 166, in execute
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     result = self._query(query)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 322, in _query
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     conn.query(q)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 856, in query
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     self._affected_rows = self._read_query_result(unbuffered=unbuffered)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1057, in _read_query_result
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     result.read()
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1340, in read
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     first_packet = self.connection._read_packet()
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 998, in _read_packet
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines     "Lost connection to MySQL server during query")
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'SELECT 1'] (Background on this error at: http://sqlalche.me/e/e3q8)
2019-07-29 23:09:27.667 28685 ERROR oslo_db.sqlalchemy.engines
2019-07-29 23:09:27.668 28680 INFO cinder.api.openstack.wsgi [-] GET http://controller:8776/
2019-07-29 23:09:27.670 28680 INFO cinder.api.openstack.wsgi [-] http://controller:8776/ returned with HTTP 300
2019-07-29 23:09:27.671 28680 INFO eventlet.wsgi.server [-] 172.30.14.10 "GET / HTTP/1.1" status: 300  len: 959 time: 0.0029979
2019-07-29 23:09:27.676 28685 INFO cinder.api.openstack.wsgi [req-d910b210-0bd0-4056-a5d2-3945937c4091 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] http://controller:8776/v2/cf080665b3e54c8b8456ee1b7f66cf9c/os-volume-transfer/detail?bootable=1&status=available returned with HTTP 200
2019-07-29 23:09:27.678 28685 INFO eventlet.wsgi.server [req-d910b210-0bd0-4056-a5d2-3945937c4091 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] 172.30.14.10 "GET /v2/cf080665b3e54c8b8456ee1b7f66cf9c/os-volume-transfer/detail?bootable=1&status=available HTTP/1.1" status: 200  len: 279 time: 0.0222340
2019-07-29 23:09:27.684 28688 INFO cinder.api.openstack.wsgi [req-ce5dff98-753a-4fb4-8bfb-ba32ae3277cb 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] GET http://controller:8776/v3/cf080665b3e54c8b8456ee1b7f66cf9c/limits
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines [req-ce5dff98-753a-4fb4-8bfb-ba32ae3277cb 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] Database connection was found disconnected; reconnecting: DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'SELECT 1'] (Background on this error at: http://sqlalche.me/e/e3q8)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines Traceback (most recent call last):
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/engines.py", line 73, in _connect_ping_listener
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     connection.scalar(select([1]))
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 880, in scalar
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     return self.execute(object, *multiparams, **params).scalar()
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 948, in execute
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     return meth(self, multiparams, params)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     return connection._execute_clauseelement(self, multiparams, params)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     compiled_sql, distilled_params
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     context)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1409, in _handle_dbapi_exception
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     util.raise_from_cause(newraise, exc_info)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     reraise(type(exception), exception, tb=exc_tb, cause=cause)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     context)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     cursor.execute(statement, parameters)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 166, in execute
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     result = self._query(query)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 322, in _query
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     conn.query(q)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 856, in query
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     self._affected_rows = self._read_query_result(unbuffered=unbuffered)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1057, in _read_query_result
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     result.read()
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1340, in read
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     first_packet = self.connection._read_packet()
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines   File "/usr/lib/python2.7/site-packages/pymysql/connections.py", line 998, in _read_packet
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines     "Lost connection to MySQL server during query")
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines DBConnectionError: (pymysql.err.OperationalError) (2013, 'Lost connection to MySQL server during query') [SQL: u'SELECT 1'] (Background on this error at: http://sqlalche.me/e/e3q8)
2019-07-29 23:09:27.689 28688 ERROR oslo_db.sqlalchemy.engines
2019-07-29 23:09:27.693 28685 INFO cinder.api.openstack.wsgi [req-68f26e12-a5d6-40d3-8276-e841fd3d7b73 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] GET http://controller:8776/v2/cf080665b3e54c8b8456ee1b7f66cf9c/volumes/detail?bootable=1&status=available
2019-07-29 23:09:27.699 28683 INFO cinder.api.openstack.wsgi [req-476817f6-cf62-495c-90ad-8f225fb0fc57 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] GET http://controller:8776/v2/cf080665b3e54c8b8456ee1b7f66cf9c/snapshots/detail?status=available
2019-07-29 23:09:27.722 28683 INFO cinder.volume.api [req-476817f6-cf62-495c-90ad-8f225fb0fc57 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] Get all snapshots completed successfully.
2019-07-29 23:09:27.723 28683 INFO cinder.api.openstack.wsgi [req-476817f6-cf62-495c-90ad-8f225fb0fc57 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] http://controller:8776/v2/cf080665b3e54c8b8456ee1b7f66cf9c/snapshots/detail?status=available returned with HTTP 200
2019-07-29 23:09:27.724 28683 INFO eventlet.wsgi.server [req-476817f6-cf62-495c-90ad-8f225fb0fc57 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] 172.30.14.10 "GET /v2/cf080665b3e54c8b8456ee1b7f66cf9c/snapshots/detail?status=available HTTP/1.1" status: 200  len: 279 time: 0.0305140
2019-07-29 23:09:27.740 28688 INFO cinder.api.openstack.wsgi [req-ce5dff98-753a-4fb4-8bfb-ba32ae3277cb 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] http://controller:8776/v3/cf080665b3e54c8b8456ee1b7f66cf9c/limits returned with HTTP 200
2019-07-29 23:09:27.742 28688 INFO eventlet.wsgi.server [req-ce5dff98-753a-4fb4-8bfb-ba32ae3277cb 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] 172.30.14.10 "GET /v3/cf080665b3e54c8b8456ee1b7f66cf9c/limits HTTP/1.1" status: 200  len: 630 time: 0.0661900
2019-07-29 23:09:27.750 28685 INFO cinder.volume.api [req-68f26e12-a5d6-40d3-8276-e841fd3d7b73 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] Get all volumes completed successfully.
2019-07-29 23:09:27.753 28685 INFO cinder.api.openstack.wsgi [req-68f26e12-a5d6-40d3-8276-e841fd3d7b73 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] http://controller:8776/v2/cf080665b3e54c8b8456ee1b7f66cf9c/volumes/detail?bootable=1&status=available returned with HTTP 200
2019-07-29 23:09:27.755 28685 INFO eventlet.wsgi.server [req-68f26e12-a5d6-40d3-8276-e841fd3d7b73 43c0ed7adb8d43deb278b93b39af8a70 cf080665b3e54c8b8456ee1b7f66cf9c - 20bec2a0f92c41aa8c74194cc7203ca0 20bec2a0f92c41aa8c74194cc7203ca0] 172.30.14.10 "GET /v2/cf080665b3e54c8b8456ee1b7f66cf9c/volumes/detail?bootable=1&status=available HTTP/1.1" status: 200  len: 277 time: 0.0662479

2.mariadb错误日志

2019-07-29 23:09:21 140155895875776 [Warning] GSSAPI plugin : default principal 'mariadb/controller@' not found in keytab
2019-07-29 23:09:21 140155895875776 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure.  Minor code may provide more information. Keytab FILE
:/etc/krb5.keytab is nonexistent or empty.
2019-07-29 23:09:21 140155895875776 [ERROR] Plugin 'gssapi' init function returned error.
2019-07-29 23:09:21 140155895875776 [Note] Server socket created on IP: '::'.
2019-07-29 23:09:21 140155895875776 [Note] /usr/libexec/mysqld: ready for connections.
Version: '10.1.20-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2019-07-29 23:09:36 140154945231616 [Note] /usr/libexec/mysqld: Normal shutdown

3.解决办法
编辑文件/etc/my.cnf.d/auth_gssapi.cnf包含该行

#plugin-load-add=auth_gssapi.so

将其注释掉并重新启动该服务。服务器应该停止加载插件。

mysql 报Plugin ‘InnoDB‘ init function returned error. 解决方案
ふりこ细工の心
02-03 6124
异常信息 210203 09:40:34 mysqld_safe mysqld from pid file /data/mysql/mysql.pid ended 210203 09:41:20 mysqld_safe Starting mysqld daemon with databases from /data/mysql 210203 9:41:20 InnoDB: The InnoDB memory heap is disabled 210203 9:41:20 InnoDB: Mutexes
cinder-api启动过程学习
qeelee的专栏
03-21 1305
cinder-api启动过程学习
openstack cinder模块报错，求求大佬帮帮孩子，马上作业截至了
weixin_51402309的博客
04-25 421
完成所有配置后，使用命令：openstack volume service list，报错为。1.cinderAPI的端口8776未打开，但是各个服务启动正常，不知道为什么。2.cinder无法连接到rabbit。
Lost connection to MySQL server during query (by quqi99)
技术并艺术着
11-06 4786
版权声明：可以任意转载，转载时请务必以超链接形式标明文章原始出处和作者信息及本版权声明 (作者：张华 发表于：2018-11-06) 问题 neutron designate日志中发现错误"Got lower serial for", 并且创建zone时永远停留在PENDING状态. 解决 minidns中看到下列日志: var/log/designate/designate-mdns.log.2......
keystone执行报错WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed
linuxvfast的博客
06-24 1380
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
生效admin环境变量后执行cinder service-list报错ERROR: Unable to establish connection to http://controller:35357/
Zcoder`Blog
11-02 4852
ERROR: Unable to establish connection to http://controller:35357/一、报错信息二、解决方法 一、报错信息 [root@controller ~]# . admin-openrc [root@controller ~]# cinder service-list ERROR: Unable to establish connection ...
查看journalnode节点状态信息_OpenStack Cinder服务状态排错
weixin_32243309的博客
02-01 985
作者：舒祝最近手动搭建了一个openstack环境，创建硬盘时失败，查看日志，提示无法进行调度，怀疑是cinder节点出现问题，去cinder节点查看服务 ，状态显示正常。systemctl status openstack-cinder-volume.service然后在控制节点查看cinder服务，openstack volume service list正常情况下显示：结果显示cinder-...
OpenStack_Horizon登录报错问题的解决
wang_san_shi的专栏
04-17 5442
OpenStack使用Horizon登录报错问题的解决 1、现象 安装完horizon后，输入URL可以访问登录页面，但是在登录页面输入用户名和密码，登录报错。 2、分析及解决 分别使用keystone、cinder、glance、neutron、nova（这次环境中控制节点上安装了这些组件）的客户端命令调用其API进行检测： 如使用以下命令： #keyston
cinder 创建backup volume
IT灬驴
06-27 1万+
cinder支持创建backup volume，需要指定源volume。在做测试的时候出现创建失败，做以记录。
openstack 创建虚拟机时cinder 读取info文件权限问题
火云邪神的博客
03-15 382
1.报错信息 2021-03-15 16:30:25.343 49590 ERROR oslo_messaging.rpc.server with open(filename, 'r') as f: 2021-03-15 16:30:25.343 49590 ERROR oslo_messaging.rpc.server IOError: [Errno 13] Permission denied: u'/var/lib/cinder/mnt/6ee3397902b681df883306df8b4f...
解决Lost connection to MySQL server during query错误方法
weixin_40362806的博客
11-23 1916
这种错误一般出现在Navicat刷sql时会报错，有时不会报错，但是sql或者备份刷进数据库后发现数据缺失也可以用这种方法解决。解决：在my.ini配置文件 mysqld 节点下添加max_allowed_packet = 500M并重启mysql。原因：配置文件限制刷数据库的大小。
DataBase Connection Failed的一点解决办法（PHP项目）
weixin_34075551的博客
05-18 2392
今天配置一个以前的PHP项目，当数据库、服务器都配置好以后，php也更改为合适版本以后，项目运行后一直显示DataBase Connection Failed，检查项目 config_mysql.inc.php 文件中的数据库参数也没发现错误，苦恼了好久 后来发现是因为没有打开PHP中的extension扩展导致的，打开php/php.ini文件，搜索extension ，如下图： ...
CDH中安装Hue连接不上数据库 Unexpected error. Unable to verify database connection 完美解决方案
热门推荐
晰中的博客
11-02 2万+
在安装CDH时，走到验证数据库连接部分时候，Hue总是验证不过去，报错为： Unexpected error. Unable to verify database connection。原因大都是因为缺少环境包所致。   我安装的过程中分别使用过postgresql和mysql，都出现过相同问题最终都得以解决，解决方法如下： 比如：我把Hue安装在slave1节点上 当使用Postgres...
数据库连接错误
csj50的专栏
03-24 2567
0） org.springframework.jdbc.UncategorizedSQLException: ### Error querying database. Cause: java.sql.SQLException: ORA-01089: immediate shutdown in progress - no operations are permitted 1） Couldn't rollback jdbc connection. Io exception: Connection time..
CentOS下的MySQL爬坑（Plugin 'InnoDB' init function returned error.）
makersy的博客
04-26 1万+
mysql version : 5.1.7 centos version : 6.8 用户权限设置 为了远程连接我的服务器的mysql数据库，需要为该连接用户设置合适的访问权限。比如我想让makers这个用户远程连接，且给他访问某个库比如test的权限，那么就用root登入mysql。随后输入以下语句： use mysql; grant privileges on test.* to 'maker...
keystone 无法导入解决方法
boqiangqing9840的博客
07-14 981
su -s /bin/sh -c “keystone-manage db_sync” keystone 无法导入解决方法其中出现以下两个问题：SQL connection failed. 9 attempts left.: DBConnectionError: (pymysql.err.OperationalError) (2003, “Can’t connect to MySQL server ...
MySQL 8.0.11版本连接报错: Could not create connection to database server.
大痴小乙的博客
11-05 7617
准备使用mybatis-plus + Hikari + SpringBoot 搭建一个项目，结果一直报错Could not create connection to database server 报错信息如下： 2018-11-05 00:35:23.749 INFO 7252 --- [ main] com.zaxxer.hikari.HikariDataSource ...
控制节点cinder启动错误
最新发布
05-22
### 可能的原因分析 Cinder 控制节点启动失败可能由多种因素引起，以下是常见的几种可能性及其对应的解决方法： #### 1. 配置文件错误 如果 Cinder 的配置文件 `/etc/cinder/cinder.conf` 中存在语法错误或者参数不匹配的情况，则可能导致服务无法正常启动。例如，数据库连接字符串、RabbitMQ 地址或者其他依赖的服务地址配置有误。 可以通过以下命令检查配置文件是否有问题： ```bash grep -v "^#" /etc/cinder/cinder.conf | grep -v "^$" ``` 确认无误后尝试重新加载服务并查看日志： ```bash systemctl restart openstack-cinder-api.service openstack-cinder-scheduler.service tail -f /var/log/cinder/*.log ``` 此操作有助于定位具体的错误信息[^1]。 --- #### 2. 数据库同步未完成 如果 Cinder 数据库尚未初始化或同步到最新版本，可能会导致服务启动失败。可以运行以下命令来验证和修复数据库状态： ```bash su -s /bin/sh -c "cinder-manage db sync" cinder ``` 如果该命令执行成功而没有报错，则说明数据库已准备就绪；如果有异常，请根据返回的日志进一步排查[^2]。 --- #### 3. iSCSI 或其他存储驱动程序问题 某些情况下，iSCSI 存储驱动程序可能出现兼容性问题，尤其是在手动修改过 `driver.py` 文件之后。例如，在引用中提到的注释掉某行代码的操作虽然能够暂时解决问题，但也可能引入新的隐患[^3]。 建议恢复原始文件内容，并通过官方文档推荐的方式调整相关参数。例如，确保 `tgtadm` 工具安装正确且可用： ```bash apt-get install tgt service tgt start ``` 随后再次测试 Cinder 节点功能是否恢复正常。 --- #### 4. 权限不足或其他外部依赖缺失 当系统缺少必要的权限（如 SELinux 设置不当）、网络连通性受限或是 RabbitMQ 等消息队列不可达时，也可能引发类似的错误现象。此时应逐一核实这些条件是否满足需求。 对于 SELinux 用户来说，可临时将其切换至宽容模式观察效果变化： ```bash setenforce 0 ``` 待问题得到彻底根治后再考虑如何安全启用强制策略。 --- ### 解决方案总结 综上所述，针对当前描述的现象可以从以下几个方面入手寻找根本原因并加以修正：核查配置项准确性、保障基础架构层面上各组件间通信顺畅以及遵循最佳实践处理第三方插件集成事宜等等。最终目标是要让整个 OpenStack 平台稳定可靠地运作起来。 ```python # 示例 Python 脚本用于自动化部分诊断流程 import os def check_cinder_status(): services = ["openstack-cinder-api", "openstack-cinder-scheduler"] for svc in services: result = os.system(f"systemctl is-active --quiet {svc}") if result != 0: print(f"{svc} service is not running.") check_cinder_status() ```
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值