[原]openstack-kilo--issue(十一)Failed connect to 169.254.169.254:80; No route to host
2017-01-04 17:32
609 查看
本博客已经添加"打赏"功能，"打赏"位置位于右边栏红色框中，感谢您赞助的咖啡.
# curl http://169.254.169.254/latest/user-data curl: (7) Failed connect to 169.254.169.254:80; No route to host
解决方案：
重点检查是否是metadata agent出了问题。
1002 cd /etc/sysconfig/network-scripts/ 1003 ls 1004 vim route-eth0 1005 route add -host 169.254.169.254 gw 10.10.10.1 dev eth0 1006 route -n 1007 curl http://169.254.169.254[/code]
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- rsync: failed to connect to X.X.X.X: No route to host (113)
- Get value from agent failed: cannot connect to [[192.168.186.130]:10050]: [113]No route to host
- Get value from agent failed: cannot connect to [[192.168.1.110]:10050]: [113] No route to host
- Get value from agent failed: cannot connect to [[192.168.186.130]:10050]: [113]No route to host
- android报错：connect failed: EHOSTUNREACH (No route to host)
- Get value from agent failed: cannot connect to [[192.168.1.205]:10050]: [113]No route to host
- rsync: failed to connect to X.X.X.X: No route to host (113)
- android 网络请求遇到的坑：connect failed: EHOSTUNREACH (No route to host)
- rsync: failed to connect to X.X.X.X: No route to host (113)
- Failed to connect to /XXXfor block, add to deadNodes and continue. java.net.NoRouteToHostException:
- nginx connect() failed (113: No route to host) while connecting to upstream
- 解决负载均衡中遇到Failed to connect to 10.3.3.173 port 443: No route to host
- rsync: failed to connect to x.x.x.x: No route to host (113)
- rsync: failed to connect to X.X.X.X: No route to host (113)
- Failed connect to 192.168.213.129:8080; No route to host
- Failed to connect to the host via ssh: ssh: connect to host 192.68.1.75 port 22: No route to host
- rsync: failed to connect to 192.168.19.160: No route to host (113)
- OpenStack之noVNC问题(Failed to connect to server (code: 1006))处理
- Connect error: No route to host(errno:113) 连接错误解决办法－－关闭iptables防火墙
- telnet: connect to address xx: No route to host