在安装pike  compute node节点的时候遇到启动nova-compute失败,问题如下(注意红色字体):

[root@compute1 nova]# systemctl start 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.
[root@compute1 nova]# 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 Tue -- :: CST; 2s ago
Main PID: (nova-compute)
Tasks:
CGroup: /system.slice/openstack-nova-compute.service
└─ /usr/bin/python2 /usr/bin/nova-compute Sep :: compute1 systemd[]: openstack-nova-compute.service holdoff time over, scheduling restart.
Sep :: compute1 systemd[]: Starting OpenStack Nova Compute Server...
[root@compute1 nova]# date
Tue Sep :: CST
[root@compute1 nova]# journalctl -xe
Sep :: compute1 avahi-daemon[]: Withdrawing workstation service for lo.
Sep :: compute1 avahi-daemon[]: Withdrawing workstation service for virbr0-nic.
Sep :: compute1 avahi-daemon[]: Withdrawing address record for 192.168.122.1 on virbr0.
Sep :: compute1 avahi-daemon[]: Withdrawing workstation service for virbr0.
Sep :: compute1 avahi-daemon[]: Withdrawing address record for fe80::fc81:46e3:49a7:d1da on ens35.
Sep :: compute1 avahi-daemon[]: Withdrawing address record for fe80::8fb9:::d538 on ens35.
Sep :: compute1 avahi-daemon[]: Withdrawing address record for 192.168.70.73 on ens35.
Sep :: compute1 avahi-daemon[]: Withdrawing workstation service for ens35.
Sep :: compute1 avahi-daemon[]: Withdrawing address record for fe80::fe24:180a:91a7:8bdf on ens34.
Sep :: compute1 avahi-daemon[]: Host name conflict, retrying with compute1-
Sep :: compute1 avahi-daemon[]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Sep :: compute1 avahi-daemon[]: Registering new address record for fe80::fc81:46e3:49a7:d1da on ens35.*.
Sep :: compute1 avahi-daemon[]: Registering new address record for fe80::8fb9:::d538 on ens35.*.
Sep :: compute1 avahi-daemon[]: Registering new address record for 192.168.70.73 on ens35.IPv4.
Sep :: compute1 avahi-daemon[]: Registering new address record for fe80::fe24:180a:91a7:8bdf on ens34.*.
Sep :: compute1 avahi-daemon[]: Registering new address record for fe80:::9aae::6a4a on ens34.*.
Sep :: compute1 avahi-daemon[]: Registering new address record for 10.50.70.73 on ens34.IPv4.
Sep :: compute1 avahi-daemon[]: Registering new address record for 192.168.184.135 on ens33.IPv4.
Sep :: compute1 avahi-daemon[]: Registering HINFO record with values 'X86_64'/'LINUX'.
Sep :: compute1 systemd[]: openstack-nova-compute.service: main process exited, code=exited, status=/FAILURE
Sep :: compute1 systemd[]: Failed to start OpenStack Nova Compute Server.
-- Subject: Unit openstack-nova-compute.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit openstack-nova-compute.service has failed.
--
-- The result is failed.
Sep :: compute1 systemd[]: Unit openstack-nova-compute.service entered failed state.
Sep :: compute1 systemd[]: openstack-nova-compute.service failed.
Sep :: compute1 systemd[]: openstack-nova-compute.service holdoff time over, scheduling restart.
Sep :: compute1 systemd[]: Starting OpenStack Nova Compute Server...
[root@compute1 nova]#vim /var/log/nova/nova-compute.log 
... ERROR nova AccessRefused: (, ): () ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN.
For details see the broker logfile.

从上面的记录中可以推断应该message queue出了问题。导致无法login。

再想想涉及login到rabbit的使用的是用户名和密码:

查看rabbit server [on controller node]用户名密码:

[root@controller ~]# rabbitmq-plugins enable rabbitmq_management                 //开启rabbit web界面 
[root@controller ~]#lsof |grep rabbit                                            //查询rabbit web服务端口 15672
async_63   1089 2034       rabbitmq   49u     IPv4              32616       0t0        TCP *: (LISTEN)

在浏览器中输入controller:15672地址,如下图

再在compute node中的nova.conf中查找相关的用户名和密码

[DEFAULT]

。。。
enabled_apis = osapi_compute,metadata
transport_url = rabbit://openstack:rabbit@controller

用户名为openstack

密码为rabbit

login 失败

查看rabbit sever的用户列表发现没有openstack这个用户:

[root@controller ~]# rabbitmqctl list_users
Listing users ...
admin [administrator]
guest [administrator]

[重点]使用admin用户登录,由于忘记密码又不能直接查看明文密码,所以在rabbit_server[controller node]上重置用户为admin的用户密码:

[root@controller nova]# rabbitmqctl change_password admin admin

再次使用用户名和密码登录

用户名:admin

密码:admin

最后修改nova.conf [on compute node or controller node]

transport_url= rabbit://admin:admin@controller

启动nova-compute.service

[root@compute1 nova]# systemctl start openstack-nova-compute.service
[root@compute1 nova]# 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: active (running) since Tue -- :: CST; 49s ago
Main PID: (nova-compute)
Tasks:
CGroup: /system.slice/openstack-nova-compute.service
└─ /usr/bin/python2 /usr/bin/nova-compute Sep :: compute1 systemd[]: Starting OpenStack Nova Compute Server...
Sep :: compute1 systemd[]: Started OpenStack Nova Compute Server.

问题解决

[原][openstack-pike][compute node][issue-1]openstack-nova-compute.service holdoff time over, scheduling restart.的更多相关文章

  1. 《转》 Openstack Grizzly 指定 compute node 创建 instance

    声明:此文档仅仅做学习交流使用,请勿用作其它商业用途 作者:朝阳_tony 邮箱:linzhaolover@gmail.com 2013年6月4日9:37:44 星期二 转载请注明出处:http:// ...

  2. Openstack组件部署 — Nova_Install and configure a compute node

    目录 目录 前文列表 Prerequisites 先决条件 Install and configure a compute node Install the packages Edit the etc ...

  3. openstack pike 集群高可用 安装 部署 目录汇总

    # openstack pike 集群高可用 安装部署#安装环境 centos 7 史上最详细的openstack pike版 部署文档欢迎经验分享,欢迎笔记分享欢迎留言,或加QQ群663105353 ...

  4. openstack pike 使用 openvswitch + vxlan

    # openstack pike 使用 openvswitch + vxlan# openstack pike linuxbridge-agent 换为 openvswitch-agent #open ...

  5. openstack pike 单机 一键安装 shell

    #openstack pike 单机  centos 一键安装 shell #openstack pike 集群高可用  安装部署 汇总 http://www.cnblogs.com/elvi/p/7 ...

  6. CentOS7.2非HA分布式部署Openstack Pike版 (实验)

    部署环境 一.组网拓扑 二.设备配置 笔记本:联想L440处理器:i3-4000M 2.40GHz内存:12G虚拟机软件:VMware® Workstation 12 Pro(12.5.2 build ...

  7. openstack pike与ceph集成

    openstack pike与ceph集成 Ceph luminous 安装配置 http://www.cnblogs.com/elvi/p/7897178.html openstack pike 集 ...

  8. OpenStack Pike超详细搭建文档 LinuxBridge版

    前言 搭建前必须看我 本文档搭建的是分布式P版openstack(1 controller + N compute + 1 cinder)的文档. openstack版本为Pike. 搭建的时候,请严 ...

  9. 照着官网来安装openstack pike之创建并启动instance

    有了之前组件(keystone.glance.nova.neutron)的安装后,那么就可以在命令行创建并启动instance了 照着官网来安装openstack pike之environment设置 ...

随机推荐

  1. js 事件冒泡、捕获;call()、apply()

    他们是描述事件触发时序问题的术语.事件捕获指的是从document到触发事件的那个节点,即自上而下的去触发事件.相反的,事件冒泡是自下而上的去触发事件.绑定事件方法的第三个参数,就是控制事件触发顺序是 ...

  2. python之进程和线程3

    1 multiprocessing模块 (1.)直接导入 from multiprocessing import Process import os import time def info(name ...

  3. GMA Round 1 大吉大利,晚上吃鸡

    传送门 大吉大利,晚上吃鸡 新年走亲访友能干点啥呢,咱开黑吃鸡吧. 这里有32个人,每个人都可能想玩或者不想玩,这样子一共有$2^{32}$种可能.而要开黑当然得4人4人组一队(四人模式),所以说如果 ...

  4. 11、python阶段测试

    1.执行Python脚本的两种方式 如果想要永久保存代码,就要用文件的方式 如果想要调试代码,就要用交互式的方式 2.Pyhton单行注释和多行注释分别用什么? 单行注释:# 多行注释: '' &qu ...

  5. 通过Tag标签回退版本修复bug

    tag是对历史一个提交id的引用,如果理解这句话就明白了使用git checkout tag即可切换到指定tag,例如:git checkout v0.1.0 切换到tag历史记录会处在分离头指针状态 ...

  6. 转: linux centos7 下安装maven

    转: https://www.tecmint.com/install-apache-maven-on-centos-7/

  7. grid - 使用相同的名称命名网格线和设置网格项目位置

    1.使用repeat()函数可以给网格线分配相同的名称.这可以节省一定的时间 使用repeat()函数可以给网格线命名,这也导致多个网格线具有相同的网格线名称. 相同网格线名称指定网格线的位置和名称, ...

  8. VS插件File Nesting

    开发者们一直以来都是使用Visual Studio的解决方案管理器 中的嵌套功能管理项目的子文件夹,使得文件组织清晰.便于访问.鉴于现在的项目巨大的文件数目,如果能将这种嵌入能力应用于项目的其他子项上 ...

  9. Mac下多版本JDK安装

    1.下载 JDK1.6官方未提供1.6的mac版本,需要去apple的开发者网站 JDK1.7.JDK1.8可以去Oracle官方下载 此处提供网盘下载地址: 链接: http://pan.baidu ...

  10. Linux 驱动开发

    linux驱动开发总结(一) 基础性总结 1, linux驱动一般分为3大类: * 字符设备 * 块设备 * 网络设备 2, 开发环境构建: * 交叉工具链构建 * NFS和tftp服务器安装 3, ...