cinder_api报错

最新推荐文章于 2023-11-23 11:11:20 发布
最新推荐文章于 2023-11-23 11:11:20 发布
阅读量1k 收藏
点赞数 1
分类专栏： openstack 文章标签： openstack
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/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 6110
异常信息 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连接mysql数据库_Openstack Queens 环境搭建（九）Cinder服务
weixin_28994357的博客
02-06 326
存储服务概念OpenStack块存储服务(Cinder)将持久性存储添加到一个虚拟机。块存储提供了管理卷的基础设施，并与OpenStack计算交互，为实例提供卷。该服务还支持卷快照和卷类型的管理。块存储服务由以下组件组成:cinder-api接收API请求，并将其路由到cinders -volume以进行操作。cinder-volume直接与块存储服务和进程(如cinders -scheduler...
openstack cinder模块报错，求求大佬帮帮孩子，马上作业截至了
weixin_51402309的博客
04-25 406
完成所有配置后，使用命令：openstack volume service list，报错为。1.cinderAPI的端口8776未打开，但是各个服务启动正常，不知道为什么。2.cinder无法连接到rabbit。
Lost connection to MySQL server during query (by quqi99)
技术并艺术着
11-06 4763
版权声明：可以任意转载，转载时请务必以超链接形式标明文章原始出处和作者信息及本版权声明 (作者：张华 发表于：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 1339
su -s /bin/sh -c "keystone-manage db_sync" keystone执行报错 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed https://blog.youkuaiyun.com/cow66/article/details/78714899
cinder-api启动过程学习
qeelee的专栏
03-21 1298
cinder-api启动过程学习
生效admin环境变量后执行cinder service-list报错ERROR: Unable to establish connection to http://controller:35357/
Zcoder`Blog
11-02 4833
ERROR: Unable to establish connection to http://controller:35357/一、报错信息二、解决方法 一、报错信息 [root@controller ~]# . admin-openrc [root@controller ~]# cinder service-list ERROR: Unable to establish connection ...
OpenStack_Horizon登录报错问题的解决
wang_san_shi的专栏
04-17 5418
OpenStack使用Horizon登录报错问题的解决 1、现象 安装完horizon后，输入URL可以访问登录页面，但是在登录页面输入用户名和密码，登录报错。 2、分析及解决 分别使用keystone、cinder、glance、neutron、nova（这次环境中控制节点上安装了这些组件）的客户端命令调用其API进行检测： 如使用以下命令： #keyston
查看journalnode节点状态信息_OpenStack Cinder服务状态排错
weixin_32243309的博客
02-01 970
作者：舒祝最近手动搭建了一个openstack环境，创建硬盘时失败，查看日志，提示无法进行调度，怀疑是cinder节点出现问题，去cinder节点查看服务 ，状态显示正常。systemctl status openstack-cinder-volume.service然后在控制节点查看cinder服务，openstack volume service list正常情况下显示：结果显示cinder-...
cinder 创建backup volume
IT灬驴
06-27 1万+
cinder支持创建backup volume，需要指定源volume。在做测试的时候出现创建失败，做以记录。
解决Lost connection to MySQL server during query错误方法
weixin_40362806的博客
11-23 1883
这种错误一般出现在Navicat刷sql时会报错，有时不会报错，但是sql或者备份刷进数据库后发现数据缺失也可以用这种方法解决。解决：在my.ini配置文件 mysqld 节点下添加max_allowed_packet = 500M并重启mysql。原因：配置文件限制刷数据库的大小。
DataBase Connection Failed的一点解决办法（PHP项目）
weixin_34075551的博客
05-18 2379
今天配置一个以前的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 2541
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...
OpenStack公共组件oslo之九——oslo.db
上善若水的木偶戏
11-22 6731
本文对oslo.db的实现与使用方法进行了详细分析，阐明了oslo.db如何与SQLAlchemy框架结合为OpenStack各组件提供数据库连接与操作。
keystone 无法导入解决方法
boqiangqing9840的博客
07-14 960
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 ...
我采用了方法三验证，输出[root@hmn0001 ycj]# curl -X GET http://172.25.26.250:5000/v2/_catalog {"repositories":["ai/gitea","aicc/aicc","aicc/aicc-site-controller","aicc/ainm","aicc/ainm_sidecar","airshipit/armada","baseimage/golang","beats/filebea","beats/filebeat","beats/filebeat-wolfi","bitnami/bitnami-shell","bitnami/elasticsearch","bitnami/kibana","bitnami/mariadb-galera","bitnami/minio","bitnami/nginx","bitnami/redis","bitnami/redis-sentinel","c1oudnative/eval-opencompass-arm","c1oudnative/evalscope-arm","c1oudnative/multi-arch-eval","calico/cni","calico/kube-controllers","calico/node","calico/pod2daemon-flexvol","cloud_native/model-hub","cloud_native/modelhub-backend","cloudnative/evalscope","cloudnative/model-evaluation","coredns","cuboss/golden-lion-api","cuboss/golden-lion-apps","cuboss/golden-lion-auth","cuboss/golden-lion-image","cuboss/vcuda","distroless/static","docker.io/memcached","docker.io/openstackhelm/ceph-config-helper","docker.io/openstackhelm/mariadb","docker.io/openstackhelm/rbd-provisioner","docker.io/openstackhelm/zookeeper","docker.io/rabbitmq","docker.io/release/stx-barbican","docker.io/release/stx-blackswan","docker.io/release/stx-cinder","docker.io/release/stx-designate","docker.io/release/stx-dimsagent","docker.io/release/stx-dimsmanager","docker.io/release/stx-glance","docker.io/release/stx-heat","docker.io/release/stx-ironic","docker.io/release/stx-keystone","docker.io/release/stx-nas","docker.io/release/stx-neutron","docker.io/release/stx-neutron-sdi","docker.io/release/stx-nova","docker.io/release/stx-octavia","docker.io/release/stx-openstackclients","docker.io/release/stx-sdi-agent","docker.io/release/stx-wnas","docker.io/starlingx/neutron-keepalived","docker.io/starlingx/neutron-nginx","docker.io/starlingx/neutron-telegraf","docker.io/starlingx/stx-libvirt","docker.io/starlingx/wnas-docker","dragonflyoss/busybox","dragonflyoss/dfdaemon","dragonflyoss/manager","dragonflyoss/mysql","dragonflyoss/openssl","dragonflyoss/redis","dragonflyoss/scheduler","dwinsdigitalservice/openstack-dashboard","ecr/cephfs-provisioner","ehpc/agent","ehpc/nginx","ehpc/oss-sync","ehpc/redis","ehpc/sshd","ehpc/ubuntu-sshd","ehpc/yum_centos","ehpc/yum_centos7","ehpc/yum_ule","elastic/elasticsearch","elastic/filebeat","elastic/kibana","gcc","gcr.io/google_containers/defaultbackend","gitea/bitnami-nginx","gitea/filebeat-httpout","gitea/gitea","gitea/nginx","gl-cluster-manager/gl-cluster-manager","goharbor/harbor-core","goharbor/harbor-db","goharbor/harbor-exporter","goharbor/harbor-jobservice","goharbor/harbor-log","goharbor/harbor-portal","goharbor/harbor-registryctl"]} 那我需要怎么修改我刚才的报错
最新发布
03-15
<think>嗯，用户刚才执行了一个curl命令来获取Docker registry的仓库列表，现在遇到了报错，需要帮助解决。首先，我需要理解用户的具体问题是什么。用户提到他们用了“方法三”验证，但报错了，不过输出的结果看起来是正常的，列出了很多仓库。可能用户认为这个输出本身就是错误，或者实际有错误信息没有显示出来。 首先，我应该检查用户提供的命令和输出是否有问题。用户的命令是： ``` curl -X GET http://172.25.26.250:5000/v2/_catalog ``` 返回的JSON显示了很多仓库，状态码应该是200，但用户可能遇到了其他错误，比如权限问题、连接问题，或者返回的内容不符合预期。但根据输出，似乎请求是成功的，所以可能报错出现在其他步骤，而用户没有提供具体的错误信息。 接下来，用户需要修改刚才的报错，但问题描述不够详细。可能的报错原因包括：认证失败、registry版本不支持/_catalog端点、网络问题等。我需要引导用户提供更多信息，比如具体的错误提示、使用的Docker registry版本，以及是否配置了认证。 可能的解决步骤包括： 1. 检查网络连接是否正常，确保IP和端口正确。 2. 确认registry服务是否运行正常，查看服务日志。 3. 检查是否需要认证，添加用户名密码到curl命令。 4. 确认registry配置是否允许访问/_catalog端点，可能需要修改config.yml。 5. 验证registry版本是否支持该API。 用户可能需要补充具体的错误信息，以便更准确地诊断问题。同时，建议用户检查服务状态和配置文件，确保没有权限或配置上的限制。</think>根据你提供的输出，该命令成功获取了Docker Registry的镜像仓库列表。如果遇到报错，请先补充具体错误信息。以下是常见的排查方向： --- ### **一、先确认基础信息** 1. **检查IP和端口** - 确保 `172.25.26.250:5000` 是有效的Registry地址 - 执行 `ping 172.25.26.250` 验证网络连通性 - 执行 `telnet 172.25.26.250 5000` 验证端口是否开放 2. **检查Registry服务状态** 在Registry服务器上运行： ```bash systemctl status docker-registry # 假设使用systemd管理 docker ps | grep registry # 如果使用Docker容器运行 ``` --- ### **二、常见错误及修复** #### **场景1：认证失败（401 Unauthorized）** 如果返回类似 `401 UNAUTHORIZED`，需添加认证信息： ```bash curl -X GET -u username:password http://172.25.26.250:5000/v2/_catalog ``` #### **场景2：API不支持（404 Not Found）** 如果返回
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值