[Nova] Failed to get shared “write“ lock Is another process using the image?

[Nova] Failed to get shared “write” lock Is another process using the image?

原因

此磁盘已经被其他进程占用。

解决方法

方法1

  1. ps -aux |grep " image(创建的磁盘名称)"
    //通过上述命令找到相关进程杀死(该磁盘可能被别人占用,建议询问后在杀)
  2. kill -9 “上述命令查出的进程号”
  3. 重新拉虚拟机

方法2

  1. sb.img文件镜像大小制作: qemu-img create -f qcow2 sb.img 50G
  2. 启动虚拟机 fdisk -l 查看查看磁盘信息 一般会输出/dev/vda或/dev/vdb信息
  3. mkfs.ext4 /dev/vda 格式化磁盘(分区磁盘,查看本地/document/Newer_enviroment_construct/分区磁盘命令)
  4. 新建一个文件夹mkdir /tmp , 并挂载磁盘 mount /dev/vda /tmp
  5. 替换原来的disk
  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Linux系统中,当服务启动失败时,通常会提示“Job for xxx.service failed because the control process exited with error code. See 'systemctl status xxx.service' and 'journalctl -xe' for details.”这个错误信息。这个错误信息提示我们可以通过运行'systemctl status xxx.service'和'journalctl -xe'来查看详细的错误信息。 对于'Job for openstack-nova-scheduler.service failed because the control process exited with error code.'这个错误,我们可以按照以下步骤来解决: 1. 运行'systemctl status openstack-nova-scheduler.service'命令来查看服务的状态和错误信息。 2. 运行'journalctl -xe'命令来查看系统日志,找到与服务启动相关的错误信息。 3. 根据错误信息来修复问题。可能的解决方案包括重新安装服务、更新配置文件、检查依赖项等。 以下是一个例子,演示如何通过运行'systemctl status'和'journalctl -xe'来查看错误信息并解决问题: ```bash $ systemctl status openstack-nova-scheduler.service ● openstack-nova-scheduler.service - OpenStack Nova Scheduler Server Loaded: loaded (/usr/lib/systemd/system/openstack-nova-scheduler.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2021-11-02 10:00:00 CST; 5s ago Process: 1234 ExecStart=/usr/bin/nova-scheduler (code=exited, status=1/FAILURE) Main PID: 1234 (code=exited, status=1/FAILURE) Nov 02 10:00:00 server systemd[1]: Starting OpenStack Nova Scheduler Server... Nov 02 10:00:00 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 1 seconds. Nov 02 10:00:01 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 2 seconds. Nov 02 10:00:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 4 seconds. Nov 02 10:00:07 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 8 seconds. Nov 02 10:00:15 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 16 seconds. Nov 02 10:00:31 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 32 seconds. Nov 02 10:01:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 64 seconds. Nov 02 10:02:07 server systemd[1]: openstack-nova-scheduler.service: main process exited, code=exited, status=1/FAILURE Nov 02 10:02:07 server systemd[1]: Failed to start OpenStack Nova Scheduler Server. ``` 从上面的输出中,我们可以看到服务启动失败,错误信息是“Unable to connect to AMQP server: [Errno 111] ECONNREFUSED.”。这个错误提示我们无法连接到AMQP服务器,可能是由于AMQP服务器未启动或配置错误导致的。 接下来,我们可以运行'journalctl -xe'命令来查看系统日志,找到与服务启动相关的错误信息: ```bash $ journalctl -xe ... Nov 02 10:00:00 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 1 seconds. Nov 02 10:00:01 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 2 seconds. Nov 02 10:00:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 4 seconds. Nov 02 10:00:07 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 8 seconds. Nov 02 10:00:15 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 16 seconds. Nov 02 10:00:31 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 32 seconds. Nov 02 10:01:03 server nova-scheduler[1234]: ERROR: Unable to connect to AMQP server: [Errno 111] ECONNREFUSED. Trying again in 64 seconds. ... ``` 从上面的输出中,我们可以看到与服务启动相关的错误信息是“Unable to connect to AMQP server: [Errno 111] ECONNREFUSED.”,这个错误信息与'systemctl status'命令输出的错误信息是一致的。 因此,我们可以得出结论,服务启动失败是由于无法连接到AMQP服务器导致的。我们需要检查AMQP服务器是否已启动,并确保配置文件中的AMQP服务器地址和端口号正确。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值