cinder-volume服务状态为down 解决方法
程序员文章站
2024-02-15 19:30:16
...
[[email protected] ~]# cinder service-list
+------------------+-------------+------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------------------+-------------+------+---------+-------+----------------------------+-----------------+
| cinder-scheduler | controller | nova | enabled | up | 2019-04-17T18:15:24.000000 | - |
| cinder-volume | [email protected] | nova | enabled | down | 2019-04-17T18:15:20.000000 | - |
+------------------+-------------+------+---------+-------+----------------------------+-----------------+
cinder-volume服务没起来 已经重启服务也还是down状态,启动日志看看有没有报错
[[email protected] ~]# systemctl restart openstack-cinder-volume.service
[[email protected] log]# tail -f messages
Apr 17 18:17:33 controller cinder-volume: 2019-04-17 18:17:33.112 3085 ERROR cinder.volume.manager Stderr: u' Volume group "cinder-volumes" not found\n Cannot process volume group cinder-volumes\n'
Apr 17 18:17:33 controller cinder-volume: 2019-04-17 18:17:33.112 3085 ERROR cinder.volume.manager
Apr 17 18:17:33 controllern cinder-volume: 2019-04-17 18:17:33.337 3085 INFO cinder.volume.manager [req-1c834e71-3c13-474e-8f96-8391d7d471f7 - - - - -] Initializing RPC dependent components of volume driver LVMVolumeDriver (3.0.0)
Apr 17 18:17:33 controller cinder-volume: 2019-04-17 18:17:33.339 3085 WARNING cinder.volume.drivers.lvm [req-1c834e71-3c13-474e-8f96-8391d7d471f7 - - - - -] Unable to update stats on non-initialized Volume Group: cinder-volumes
Apr 17 18:17:33 controller cinder-volume: 2019-04-17 18:17:33.355 3085 INFO cinder.volume.manager [req-1c834e71-3c13-474e-8f96-8391d7d471f7 - - - - -] Driver post RPC initialization completed successfully.
大致报错信息是指找不到cinder-volumes这个卷组
[[email protected]~]# vgs 没有卷组
[[email protected] ~]# pvcreate /dev/vda7 创建一个物理卷
[[email protected] ~]# vgcreate cinder-volumes /dev/vda7 创建卷组
[[email protected] ~]# vgs
VG #PV #LV #SN Attr VSize VFree
cinder-volume 1 0 0 wz--n- 4.75g 4.75g 现在有了
#再去看一下配置文件 确保万一
[lvm]
volume_group = cinder-volumes
#重启服务
[[email protected] ~]# systemctl restart openstack-cinder-volume.service target.service
[[email protected] ~]# cinder service-list
+------------------+--------------+------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+------------------+--------------+------+---------+-------+----------------------------+-----------------+
| cinder-scheduler | controller | nova | enabled | up | 2019-04-17T18:36:09.000000 | - |
| cinder-volume | [email protected] | nova | enabled | up | 2019-04-17T18:36:04.000000 | - |
+------------------+--------------+------+---------+-------+----------------------------+-----------------+
这样就解决了。
转载于:https://blog.51cto.com/9103824/2380221
上一篇: linux下建立ssh tunnel
下一篇: VIM编辑器的使用(大小写区分)
推荐阅读
-
cinder-volume服务状态为down 解决方法
-
php file_get_contents 的网址状态码为500时,不想让错误出现在应用服务器的error_log应该怎么做呢?
-
dell服务器硬盘的状态变成外来(foreign)的解决方法
-
Win10系统提示已禁用对该状态进行检测的服务的原因及两种解决方法
-
ASP.NET State service状态服务的问题解决方法
-
Spring boot admin 节点状态一直为DOWN的排查
-
Redis(设计与实现):--->Sentinel之检测服务器、Sentinel下线状态(down-after-milliseconds、quorum、is-master-down-by-addr)
-
WPS2013开发工具中的VBA为灰色不可用状态的解决方法
-
Oracle 日志状态为stale解决方法
-
ASP.NET State service状态服务的问题解决方法