glance无法正常启动
2017-07-13 16:41
113 查看
笔者日前部署openstack-ocata遇到一坑 glance服务无法正常启动
首先就是服务正常使用
然后好好的,好好的 突然之间glance就不嫩用了!
查一下是服务没有启动,手动启动一下,发现提示服务重启次数太多,然后就自己挂了
就是找不到了哦!难怪找不到
于是乎
首先就是服务正常使用
然后好好的,好好的 突然之间glance就不嫩用了!
查一下是服务没有启动,手动启动一下,发现提示服务重启次数太多,然后就自己挂了
● openstack-glance-api.service - OpenStack Image Service (code-named Glance) API server Loaded: loaded (/usr/lib/systemd/system/openstack-glance-api.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2017-07-13 15:12:24 CST; 313ms ago Process: 81979 ExecStart=/usr/bin/glance-api (code=exited, status=1/FAILURE) Main PID: 81979 (code=exited, status=1/FAILURE) Jul 13 15:12:24 node01 systemd[1]: Unit openstack-glance-api.service entered failed state. Jul 13 15:12:24 node01 systemd[1]: openstack-glance-api.service failed. Jul 13 15:12:24 node01 systemd[1]: openstack-glance-api.service holdoff time over, scheduling restart. Jul 13 15:12:24 node01 systemd[1]: start request repeated too quickly for openstack-glance-api.service Jul 13 15:12:24 node01 systemd[1]: Failed to start OpenStack Image Service (code-named Glance) API server. Jul 13 15:12:24 node01 systemd[1]: Unit openstack-glance-api.service entered failed state. Jul 13 15:12:24 node01 systemd[1]: openstack-glance-api.service failed. ● openstack-glance-registry.service - OpenStack Image Service (code-named Glance) Registry server Loaded: loaded (/usr/lib/systemd/system/openstack-glance-registry.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2017-07-13 15:12:24 CST; 319ms ago Process: 81980 ExecStart=/usr/bin/glance-registry (code=exited, status=1/FAILURE) Main PID: 81980 (code=exited, status=1/FAILURE) Jul 13 15:12:24 node01 systemd[1]: Unit openstack-glance-registry.service entered failed state. Jul 13 15:12:24 node01 systemd[1]: openstack-glance-registry.service failed. Jul 13 15:12:24 node01 systemd[1]: openstack-glance-registry.service holdoff time over, scheduling restart. Jul 13 15:12:24 node01 systemd[1]: start request repeated too quickly for openstack-glance-registry.service Jul 13 15:12:24 node01 systemd[1]: Failed to start OpenStack Image Service (code-named Glance) Registry server. Jul 13 15:12:24 node01 systemd[1]: Unit openstack-glance-registry.service entered failed state. Jul 13 15:12:24 node01 systemd[1]: openstack-glance-registry.service failed.于是
#grep 'fail' /lib/systemd/system/openstack-glance-api.service Restart=on-failure #sed -i '/fail/ s/^/#/g' /lib/systemd/system/openstack-glance-api.service #systemctl daemon-reload再次重启服务,报错信息变成
● openstack-glance-api.service - OpenStack Image Service (code-named Glance) API server Loaded: loaded (/usr/lib/systemd/system/openstack-glance-api.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2017-07-13 15:18:42 CST; 10s ago Process: 83673 ExecStart=/usr/bin/glance-api (code=exited, status=1/FAILURE) Main PID: 83673 (code=exited, status=1/FAILURE) Jul 13 15:18:41 node01 systemd[1]: Started OpenStack Image Service (code-named Glance) API server. Jul 13 15:18:41 node01 systemd[1]: Starting OpenStack Image Service (code-named Glance) API server... Jul 13 15:18:42 node01 glance-api[83673]: ERROR: Unable to locate paste config file for glance-api. Jul 13 15:18:42 node01 systemd[1]: openstack-glance-api.service: main process exited, code=exited, status=1/FAILURE Jul 13 15:18:42 node01 systemd[1]: Unit openstack-glance-api.service entered failed state. Jul 13 15:18:42 node01 systemd[1]: openstack-glance-api.service failed. ● openstack-glance-registry.service - OpenStack Image Service (code-named Glance) Registry server Loaded: loaded (/usr/lib/systemd/system/openstack-glance-registry.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2017-07-13 15:18:42 CST; 10s ago Process: 83674 ExecStart=/usr/bin/glance-registry (code=exited, status=1/FAILURE) Main PID: 83674 (code=exited, status=1/FAILURE) Jul 13 15:18:41 node01 systemd[1]: Started OpenStack Image Service (code-named Glance) Registry server. Jul 13 15:18:41 node01 systemd[1]: Starting OpenStack Image Service (code-named Glance) Registry server... Jul 13 15:18:42 node01 glance-registry[83674]: ERROR: Unable to locate paste config file for glance-registry. Jul 13 15:18:42 node01 systemd[1]: openstack-glance-registry.service: main process exited, code=exited, status=1/FAILURE Jul 13 15:18:42 node01 systemd[1]: Unit openstack-glance-registry.service entered failed state. Jul 13 15:18:42 node01 systemd[1]: openstack-glance-registry.service failed.发现无法找到paste文件,再次回头来看看glance-api.conf 发现这么一行
#If the paste configuration file is not found, the service will not start. # …………………… # (string value) #config_file = glance-api-paste.ini那么找找这个文件呢
#rpm -ql openstack-glance|grep glance-api-paste.ini > /dev/null # echo $? 1木有,煤油,麻油!!
就是找不到了哦!难怪找不到
于是乎
ln -s/usr/share/glance/glance-api-dist-paste.ini /usr/share/glance/glance-api-paste.ini ln -s/usr/share/glance/glance-registry-dist-paste.ini /usr/share/glance/glance-registry-paste.ini再次重启服务,一切正常了>>>>>
相关文章推荐
- Avira AntiVir 造成 SqlServer 服务无法正常启动问题的解决
- 在window 2003 下安装 Macromedia Flash 8 无法正常启动,读取字体后自动关闭
- 活动目录实战系列二(主域控无法正常启动)
- 活动目录实战系列二(主域控无法正常启动)
- 关于IP转换器无法正常启动的问题
- 无法正常启动系统
- IIS服务器正常启动,但无法浏览ASP
- gdb启动时,进程收到中断信号造成无法正常启动的解决办法
- eclipse3.5下载后无法正常启动的研究与解决
- “因以下文件损坏〈window root>/system32/hal.dll 损坏无法正常启动请安装以上的拷贝文件”解决
- 为什么IIS无法正常启动?
- OracleOraDb10g_home1iSQL*Plus服务无法正常启动的解决方法
- Fedora10安装vmware-tools后系统无法正常启动的解决方法
- ArcServer 无法正常启动,卸载IE7.0!
- 试图抓取非英文windows操作系统镜像时PE无法正常启动解决方法
- windows安装apache,无法正常启动
- windows无法正常启动(停止在欢迎界面或蓝屏)的解决方法之一
- SQL Server 2005无法正常启动一例
- oracle可执行文件s位导致的Cluster资源组无法正常启动的问题解决
- ORACLE9I 实例无法正常启动