设为首页 收藏本站
查看: 1027|回复: 0

[经验分享] Openstack:计算节点没法启动的一次排查过程

[复制链接]

尚未签到

发表于 2018-5-31 09:11:19 | 显示全部楼层 |阅读模式
  openstack的控制节点和计算节点重启后,在控制节点上查看计算资源的状态:
[root@linux-node1 ~]# openstack compute service list
+----+------------------+------------------------+----------+---------+-------+----------------------
| ID | Binary           | Host                   | Zone     | Status  | State | Updated At                 |
+----+------------------+------------------------+----------+---------+-------+----------------------
|  1 | nova-conductor   | linux-node1.wanwan.com | internal | enabled | up    | 2017-03-10T03:00:40.000000 |
|  2 | nova-scheduler   | linux-node1.wanwan.com | internal | enabled | up    | 2017-03-10T03:00:41.000000 |
|  3 | nova-consoleauth | linux-node1.wanwan.com | internal | enabled | up    | 2017-03-10T03:00:45.000000 |
|  7 | nova-compute     | linux-node1.wanwan.com | nova     | enabled | up    | 2017-03-10T03:00:38.000000 |
|  8 | nova-compute     | linux-node2.wanwan.com | nova     | enabled | down  | 2017-03-10T02:28:39.000000 |
+----+------------------+------------------------+----------+---------+-------+----------------------  居然发现计算节点node02没有起来,如上在计算节点上查看下状态

[root@linux-node2 ~]# systemctl status openstack-nova-compute.service
● openstack-nova-compute.service - OpenStack Nova Compute Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service; enabled; vendor preset: disabled)
   Active: activating (start) since Fri 2017-03-10 10:49:08 CST; 12min ago
Main PID: 2261 (nova-compute)
   CGroup: /system.slice/openstack-nova-compute.service
           └─2261 /usr/bin/python2 /usr/bin/nova-compute
Mar 10 10:49:08 linux-node2.wanwan.com systemd[1]: Starting OpenStack Nova Compute Server...
[root@linux-node2 ~]# systemctl start openstack-nova-compute.service
启服务,发现一直处于卡住的状态,查看下日志文件
-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 10:58:19.846 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 10:58:51.944 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 10:59:24.076 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 10:59:56.191 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 11:00:28.302 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 11:01:00.411 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None
2017-03-10 11:01:33.521 2261 ERROR oslo.messaging._drivers.impl_rabbit [req-187b6306-0117-4c40-944d-53dd8bf054be - - - - -] [16162492-f445-4cb0-ad0e-f101b84fa432] AMQP server on 10.10.10.11:5672 is unreachable: [Errno 113] EHOSTUNREACH. Trying again in 32 seconds. Client port: None  提示AMQP不可达,这个时候我就开始怀疑消息队列是否正常,继续检查

[root@linux-node1 ~]# lsof -i :5672
COMMAND    PID     USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nova-cons 1171     nova    5u  IPv4  30613      0t0  TCP linux-node1:40614->linux-node1:amqp (ESTABLISHED)
beam.smp  1173 rabbitmq   52u  IPv6  29124      0t0  TCP *:amqp (LISTEN)
beam.smp  1173 rabbitmq   53u  IPv6  31152      0t0  TCP linux-node1:amqp->linux-node1:40614 (ESTABLISHED)
beam.smp  1173 rabbitmq   54u  IPv6  31176      0t0  TCP linux-node1:amqp->linux-node1:40624 (ESTABLISHED)
beam.smp  1173 rabbitmq   55u  IPv6  31180      0t0  TCP linux-node1:amqp->linux-node1:40626 (ESTABLISHED)
beam.smp  1173 rabbitmq   56u  IPv6  31183      0t0  TCP linux-node1:amqp->linux-node1:40628 (ESTABLISHED)
beam.smp  1173 rabbitmq   57u  IPv6  31193      0t0  TCP linux-node1:amqp->linux-node1:40630 (ESTABLISHED)
beam.smp  1173 rabbitmq   58u  IPv6  31197      0t0  TCP linux-node1:amqp->linux-node1:40632 (ESTABLISHED)
beam.smp  1173 rabbitmq   59u  IPv6  31255      0t0  TCP linux-node1:amqp->linux-node1:40640 (ESTABLISHED)
beam.smp  1173 rabbitmq   60u  IPv6  31321      0t0  TCP linux-node1:amqp->linux-node1:40646 (ESTABLISHED)
beam.smp  1173 rabbitmq   61u  IPv6  31355      0t0  TCP linux-node1:amqp->linux-node1:40654 (ESTABLISHED)
beam.smp  1173 rabbitmq   62u  IPv6  35079      0t0  TCP linux-node1:amqp->linux-node1:40670 (ESTABLISHED)
nova-sche 1186     nova    7u  IPv4  31192      0t0  TCP linux-node1:40630->linux-node1:amqp (ESTABLISHED)
nova-comp 2091     nova    4u  IPv4  31168      0t0  TCP linux-node1:40624->linux-node1:amqp (ESTABLISHED)
nova-comp 2091     nova    5u  IPv4  31179      0t0  TCP linux-node1:40626->linux-node1:amqp (ESTABLISHED)
nova-comp 2091     nova   21u  IPv4  31898      0t0  TCP linux-node1:40654->linux-node1:amqp (ESTABLISHED)
nova-comp 2091     nova   22u  IPv4  35882      0t0  TCP linux-node1:40670->linux-node1:amqp (ESTABLISHED)
nova-cond 3265     nova    7u  IPv4  31196      0t0  TCP linux-node1:40632->linux-node1:amqp (ESTABLISHED)
nova-cond 3265     nova    8u  IPv4  31833      0t0  TCP linux-node1:40646->linux-node1:amqp (ESTABLISHED)
nova-cond 3267     nova    7u  IPv4  30623      0t0  TCP linux-node1:40628->linux-node1:amqp (ESTABLISHED)
nova-cond 3267     nova    8u  IPv4  31750      0t0  TCP linux-node1:40640->linux-node1:amqp (ESTABLISHED)
没发现有异常,尝试清除下iptables
[root@linux-node1 ~]# iptables -F
[root@linux-node1 ~]# iptables -X
[root@linux-node1 ~]# iptables -Z
再次进行检查
[root@linux-node1 ~]# openstack compute service list
+----+------------------+------------------------+----------+---------+-------+----------------------
| ID | Binary           | Host                   | Zone     | Status  | State | Updated At                 |
+----+------------------+------------------------+----------+---------+-------+----------------------
|  1 | nova-conductor   | linux-node1.wanwan.com | internal | enabled | up    | 2017-03-10T03:08:40.000000 |
|  2 | nova-scheduler   | linux-node1.wanwan.com | internal | enabled | up    | 2017-03-10T03:08:41.000000 |
|  3 | nova-consoleauth | linux-node1.wanwan.com | internal | enabled | up    | 2017-03-10T03:08:45.000000 |
|  7 | nova-compute     | linux-node1.wanwan.com | nova     | enabled | up    | 2017-03-10T03:08:48.000000 |
|  8 | nova-compute     | linux-node2.wanwan.com | nova     | enabled | up    | 2017-03-10T03:08:40.000000 |
+----+------------------+------------------------+----------+---------+-------+----------------------  

  如上,可以发现计算节点已经恢复正常了,看来iptables一定要记得清空策略

运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.yunweiku.com/thread-483296-1-1.html 上篇帖子: 如何更新 OpenStack 组件? 下篇帖子: gitlab git@localhost:dev/django_openstack_auth.git问题
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表