解决openstack-nova-compute.service无法启动问题

在OpenStack环境中,尝试启动Nova计算服务时遇到问题,表现为`openstack-nova-compute.service`无法启动,错误日志显示AMQPLAIN身份验证失败。通过检查compute节点的日志,发现是由于认证机制问题导致登录被拒绝。关闭controller节点的防火墙并重启compute节点上的libvirtd和Nova服务后,问题仍未解决。进一步检查controller节点的rabbitmq服务,确认其运行正常且5672端口开放。在rabbitmq日志中发现openstack用户的凭证无效。清除并重新设置rabbitmq的openstack用户权限后,重启rabbitmq服务。最后,再次尝试启动`openstack-nova-compute.service`,成功解决问题。

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

1.启动服务

[root@computer ~]# systemctl restart openstack-nova-compute.service
Job for openstack-nova-compute.service failed because the control process exited with error code.\
 See "systemctl status openstack-nova-compute.service" and "journalctl -xe" for details.

2.查看compute节点上的nova-compute.log日志文件,发现身份验证机制AMQPLAIN拒绝登录。

[root@computer ~]# tail /var/log/nova/nova-compute.log
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/method_framing.py", line 55, in on_frame
2020-05-15 16:50:45.750 3180 ERROR nova     callback(channel, method_sig, buf, None)
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/connection.py", line 510, in on_inbound_method
2020-05-15 16:50:45.750 3180 ERROR nova     method_sig, payload, content,
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/abstract_channel.py", line 126, in dispatch_method
2020-05-15 16:50:45.750 3180 ERROR nova     listener(*args)
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/connection.py", line 639, in _on_close
2020-05-15 16:50:45.750 3180 ERROR nova     (class_id, method_id), ConnectionError)
2020-05-15 16:50:45.750 3180 ERROR nova AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile.
2020-05-15 16:50:45.750 3180 ERROR nova 
[root@computer ~]# tail /var/log/nova/nova-compute.log
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/method_framing.py", line 55, in on_frame
2020-05-15 16:50:45.750 3180 ERROR nova     callback(channel, method_sig, buf, None)
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/connection.py", line 510, in on_inbound_method
2020-05-15 16:50:45.750 3180 ERROR nova     method_sig, payload, content,
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/abstract_channel.py", line 126, in dispatch_method
2020-05-15 16:50:45.750 3180 ERROR nova     listener(*args)
2020-05-15 16:50:45.750 3180 ERROR nova   File "/usr/lib/python2.7/site-packages/amqp/connection.py", line 639, in _on_close
2020-05-15 16:50:45.750 3180 ERROR nova     (class_id, method_id), ConnectionError)
2020-05-15 16:50:45.750 3180 ERROR nova AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile.
2020-05-15 16:50:45.750 3180 ERROR nova 

3.关闭防火墙

[root@controller ~]# systemctl  stop  firewalld
[root@controller ~]# systemctl  disable  firewalld

4.在compute节点上,重启libvirtd.service,openstack-nova-compute.service。发现libvirtd.service正常启动,openstack-nova-compute.service仍然无法启动。

[root@computer ~]# systemctl  start  libvirtd.service 
[root@computer ~]# systemctl  status  libvirtd.service 
● libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
   Active: active (running) since 五 2020-05-15 17:18:07 CST; 5s ago
     Docs: man:libvirtd(8)
           https://libvirt.org
 Main PID: 10976 (libvirtd)
    Tasks: 17 (limit: 32768)
   CGroup: /system.slice/libvirtd.service
           └─10976 /usr/sbin/libvirtd

5月 15 17:18:07 computer systemd[1]: Starting Virtualization daemon...
5月 15 17:18:07 computer systemd[1]: Started Virtualization daemon.

[root@computer ~]# systemctl restart openstack-nova-compute.service
Job for openstack-nova-compute.service failed because the control process exited with error code.\
 See "systemctl status openstack-nova-compute.service" and "journalctl -xe" for details.

5.返回到controller节点,核查rabbitmq服务是否开启,5672端口是否打开,结果显示都是正常打开。

[root@controller ~]# ps -ef|grep rabbitmq
rabbitmq  12372      1  1 17:01 ?        00:00:19 /usr/lib64/erlang/erts-8.3.5.3/bin/beam.smp -W w -A 64 -P 1048576 -t 5000000 -stbt db -zdbbl 128000 -K true -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.16/ebin -noshell -noinput -s rabbit boot -sname rabbit@controller -boot start_sasl -config /etc/rabbitmq/rabbitmq -kernel inet_default_connect_options [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false -rabbit error_logger {file,"/var/log/rabbitmq/rabbit@controller.log"} -rabbit sasl_error_logger {file,"/var/log/rabbitmq/rabbit@controller-sasl.log"} -rabbit enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir "/usr/lib/rabbitmq/plugins:/usr/lib/rabbitmq/lib/rabbitmq_server-3.6.16/plugins" -rabbit plugins_expand_dir "/var/lib/rabbitmq/mnesia/rabbit@controller-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false -mnesia dir "/var/lib/rabbitmq/mnesia/rabbit@controller" -kernel inet_dist_listen_min 25672 -kernel inet_dist_listen_max 25672
rabbitmq  12583  12372  0 17:01 ?        00:00:00 erl_child_setup 1024
rabbitmq  12605  12583  0 17:01 ?        00:00:00 inet_gethost 4
rabbitmq  12606  12605  0 17:01 ?        00:00:00 inet_gethost 4
root      13718  13360  0 17:21 pts/1    00:00:00 grep --color=auto rabbitmq
[root@controller ~]# netstat -na|grep 5672
tcp        0      0 0.0.0.0:25672           0.0.0.0:*               LISTEN
tcp6       0      0 :::5672                 :::*                    LISTEN

6.查看rabbitmq日志(/var/log/rabbitmq/rabbit@controller.log ),结果显示用户openstack拥有无效凭证,如下:

=ERROR REPORT==== 15-May-2020::16:59:17 ===
Error on AMQP connection <0.17344.0> (10.0.0.20:52414 -> 10.0.0.20:5672, state: starting):
AMQPLAIN login refused: user 'openstack' - invalid credentials

解决

[root@controller rabbitmq]# rabbitmqctl list_users
Listing users
openstack	[]
guest	[administrator]
[root@controller rabbitmq]# rabbitmqctl -q  delete_user openstack
[root@controller rabbitmq]# rabbitmqctl list_users
Listing users
guest	[administrator]
[root@controller ~]# rabbitmqctl add_user openstack Com.123
[root@controller rabbitmq]# rabbitmqctl set_permissions -p / openstack '.*' '.*' '.*'
Setting permissions for user "openstack" in vhost "/" ...
[root@controller ~]# rabbitmqctl list_users
Listing users
openstack	[]

[root@controller rabbitmq]# systemctl restart rabbitmq-server.service   
[root@controller rabbitmq]#  cat  rabbit@controller.log
=INFO REPORT==== 15-May-2020::17:01:28 ===
accepting AMQP connection <0.436.0> (10.0.0.20:52722 -> 10.0.0.20:5672)
=INFO REPORT==== 15-May-2020::17:01:28 ===
Connection <0.436.0> (10.0.0.20:52722 -> 10.0.0.20:5672) has a client-provided name: nova-scheduler:11913:87613471-ab6b-470a-a964-d7f530c8bf32
=INFO REPORT==== 15-May-2020::17:01:28 ===
connection <0.436.0> (10.0.0.20:52722 -> 10.0.0.20:5672 - nova-scheduler:11913:87613471-ab6b-470a-a964-d7f530c8bf32): user 'openstack' authenticated and granted access to vhost '/'

启动服务测试

[root@computer ~]# systemctl restart openstack-nova-compute.service

 转载地址:Openstack部署compute计算节点时,openstack-nova-compute无法启动 - 知乎 (zhihu.com)

Vivado2023是一款集成开发环境软件,用于设计和验证FPGA(现场可编程门阵列)和可编程逻辑器件。对于使用Vivado2023的用户来说,license是必不可少的。 Vivado2023的license是一种许可证,用于授权用户合法使用该软件。许可证分为多种类型,包括评估许可证、开发许可证和节点许可证等。每种许可证都有不同的使用条件和功能。 评估许可证是免费提供的,让用户可以在一段时间内试用Vivado2023的全部功能。用户可以使用这个许可证来了解软件的性能和特点,对于初学者和小规模项目来说是一个很好的选择。但是,使用评估许可证的用户在使用期限过后需要购买正式的许可证才能继续使用软件。 开发许可证是付费的,可以永久使用Vivado2023的全部功能。这种许可证适用于需要长期使用Vivado2023进行开发的用户,通常是专业的FPGA设计师或工程师。购买开发许可证可以享受Vivado2023的技术支持和更新服务,确保软件始终保持最新的版本和功能。 节点许可证是用于多设备或分布式设计的许可证,可以在多个计算机上安装Vivado2023,并共享使用。节点许可证适用于大规模项目或需要多个处理节点进行设计的用户,可以提高工作效率和资源利用率。 总之,Vivado2023 license是用户在使用Vivado2023时必须考虑的问题。用户可以根据自己的需求选择合适的许可证类型,以便获取最佳的软件使用体验。
评论 5
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值