CloudStack: unable to add the host

简介:

一、故障现象

cloudstack添加宿主机,报错“unable to add the host”,然后虚拟机宿主机也没法添加到cloudstack的管理。


二、处理过程

然后查看了下宿主机的/var/log/cloudstack/agent/agent.log日志,没有发现有什么异常,查看管理的日志,也没有发现蛛丝马迹,正当没有头绪的时候,同事说要不再看下/var/log/message

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
# tail -30 /var/log/messages 
Dec  4 19:23:42 cloudstack5 systemd: Started CloudStack Agent.
Dec  4 19:23:42 cloudstack5 systemd: Starting CloudStack Agent...
Dec  4 19:23:42 cloudstack5 sh:  /bin/sh /usr/lib/jvm/jre/bin/java : No such  file  or directory
Dec  4 19:23:42 cloudstack5 systemd: cloudstack-agent.service: main process exited, code=exited, status=1 /FAILURE
Dec  4 19:23:42 cloudstack5 systemd: Unit cloudstack-agent.service entered failed state.
Dec  4 19:23:42 cloudstack5 systemd: cloudstack-agent.service failed.
Dec  4 19:23:52 cloudstack5 systemd: cloudstack-agent.service holdoff  time  over, scheduling restart.
Dec  4 19:23:52 cloudstack5 systemd: Started CloudStack Agent.
Dec  4 19:23:52 cloudstack5 systemd: Starting CloudStack Agent...
Dec  4 19:23:52 cloudstack5 sh:  /bin/sh /usr/lib/jvm/jre/bin/java : No such  file  or directory
Dec  4 19:23:52 cloudstack5 systemd: cloudstack-agent.service: main process exited, code=exited, status=1 /FAILURE
Dec  4 19:23:52 cloudstack5 systemd: Unit cloudstack-agent.service entered failed state.
Dec  4 19:23:52 cloudstack5 systemd: cloudstack-agent.service failed.
Dec  4 19:24:03 cloudstack5 systemd: cloudstack-agent.service holdoff  time  over, scheduling restart.

如上信息,可以知道提示的信息可能与java相关,但我看了下,我的java版本是安装了的,版本是jdk1.8.0_144-1.8.0_144-fcs.x86_64

后面对比了下其它宿主机的java版本,发现都是java-1.8.0-openjdk.x86_64,于是:

1
2
#  yum remove jdk1.8.0_144-1.8.0_144-fcs.x86_64
#  yum install java-1.8.0-openjdk.x86_64

然后重新添加宿主机,问题得到解决。











本文转自 冰冻vs西瓜 51CTO博客,原文链接:http://blog.51cto.com/molewan/2047398,如需转载请自行联系原作者
目录
相关文章
|
8月前
|
网络协议 Linux 网络安全
weavescope curl -L git.io/scope -o /usr/local/xx failed to connect to 2001: Network is unreachable
weavescope curl -L git.io/scope -o /usr/local/xx failed to connect to 2001: Network is unreachable
117 0
|
8天前
|
应用服务中间件 nginx Docker
Docker:WARNING: Published ports are discarded when using host network mode 解决方法
Docker在使用 `host`网络模式时会忽略端口映射,因为此模式下容器已经直接暴露在主机网络上。通过理解并合理选择网络模式,可以有效解决 `WARNING: Published ports are discarded when using host network mode`的警告。根据具体需求,选择适合的网络模式,以便在保证性能的同时确保灵活性和安全性。希望本文提供的方法和分析能帮助您在使用Docker时更好地处理网络配置问题。
39 12
|
7月前
|
网络安全
ssh: Could not resolve hostname centos02: Temporary failure in name resolution
ssh: Could not resolve hostname centos02: Temporary failure in name resolution
584 0
|
Docker 容器
docker: Error response from daemon: driver failed programming external connectivity on endpoint mysq
docker: Error response from daemon: driver failed programming external connectivity on endpoint mysq
|
存储 Cloud Native Linux
Failed to open/create the internal network ‘HostInterfaceNetworking-VirtualBox Host-Only Ethernet
Failed to open/create the internal network ‘HostInterfaceNetworking-VirtualBox Host-Only Ethernet
|
Docker 容器
docker报错ERROR: for hass “host” network_mode is incompatible with port_bindings
docker报错ERROR: for hass “host” network_mode is incompatible with port_bindings
2884 0
|
jenkins Linux 网络安全
【Docker】 Error response from daemon: driver failed programming external connectivity on endpoint
【Docker】 Error response from daemon: driver failed programming external connectivity on endpoint
1657 0
【Docker】 Error response from daemon: driver failed programming external connectivity on endpoint
|
网络协议 应用服务中间件 Docker
Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999
Docker - 解决 Error response from daemon: driver failed programming external connectivity on endpoint tomcat9999
3361 0
|
网络协议 虚拟化