【OpenStack】SSH登录虚拟机出现"Read from socket failed: Connection reset by peer"问题的解决办法

最新推荐文章于 2021-11-15 18:59:23 发布

lynn_kong

最新推荐文章于 2021-11-15 18:59:23 发布

阅读量1.7w

点赞数 2

分类专栏： openstack 文章标签： openstack nova ssh ubuntu

本文链接：https://blog.csdn.net/lynn_kong/article/details/9112009

版权

本文详细记录了在使用OpenStack时遇到SSH登录虚拟机失败的问题，表现为"Read from socket failed: Connection reset by peer"。作者通过分析问题并进行搜索，最终找到了解决方案。

摘要由CSDN通过智能技术生成

声明：

本博客欢迎转发，但请保留原作者信息!

新浪微博：@孔令贤HW；

博客地址：http://blog.csdn.net/lynn_kong

内容系本人学习、研究和总结，如有雷同，实属荣幸！

1、问题现象

版本：Grizzly master分支代码2013.06.17
部署：三个节点（Controller/Compute + Network + Compute）
使用的镜像：precise-server-cloudimg-i386-disk1.img
创建虚拟机命令：nova boot ubuntu-keypair-test --image 1f7f5763-33a1-4282-92b3-53366bf7c695 --flavor 2 --nic net-id=3d42a0d4-a980-4613-ae76-a2cddecff054 --availability-zone nova:compute233 --key_name mykey

虚拟机ACTIVE之后，可以ping通虚拟机的fixedip（10.1.1.6）和floatingip（192.150.73.5）。VNC访问虚拟机正常，出现登录界面。因为Ubuntu的镜像无法使用密码登录，所以只能通过SSH访问，这也是创建虚拟机时指定key_name的原因。

在NetworkNode通过ssh登录虚拟机失败：

root@network232:~# ssh -i mykey.pem ubuntu@192.150.73.5 -v
OpenSSH_5.9p1 Debian-5ubuntu1.1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.150.73.5 [192.150.73.5] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file mykey.pem type -1
debug1: identity file mykey.pem-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.1
debug1: SSH2_MSG_KEXINIT sent
Read from socket failed: Connection reset by peer

虚拟机启动日志：

Begin: Running /scripts/init-bottom ... done.
[    1.874928] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Mon, 17 Jun 2013 03:39:11 +0000. up 4.59 seconds
no instance data found in start-local
ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
ci-info: eth0  : 1 10.1.1.6        255.255.255.0   fa:16:3e:31:f4:52
ci-info: route-0: 0.0.0.0         10.1.1.1        0.0.0.0         eth0   UG
ci-info: route-1: 10.1.1.0        0.0.0.0         255.255.255.0   eth0   U
cloud-init start running: Mon, 17 Jun 2013 03:39:14 +0000. up 8.23 seconds
2013-06-17 03:39:15,590 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: http error [404]
2013-06-17 03:39:17,083 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: http error [404]
2013-06-17 03:39:18,643 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]: http error [404]
2013-06-17 03:39:20,153 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: http error [404]
2013-06-17 03:39:21,638 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [6/120s]: http error [404]
2013-06-17 03:39:23,071 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [8/120s]: http error [404]
2013-06-17 03:41:15,356 - DataSourceEc2.py[CRITICAL]: giving up on md after 120 seconds

no instance data found in start
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
 * Starting AppArmor profiles                                            [ OK ] 
landscape-client is not configured, please run landscape-config.
 * Stopping System V initialisation compatibility                        [ OK ]
 * Stopping Handle applying cloud-config                                 [ OK ]
 * Starting System V runlevel compatibility                              [ OK ]
 * Starting ACPI daemon                                                  [ OK ]
 * Starting save kernel messages