Re: [Openstack] Can't ssh into instance
Thank you very much guys Sébastien and Leander It was very interesting case. I thought if I see this lines in compute.log then sshkey injection was successfully 1fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap qemu-nbd -c /dev/nbd15 /var/lib/nova/instances/instance-000c/disk from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap kpartx -a /dev/nbd15 from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap mount /dev/mapper/nbd15p1 /tmp/tmpffuOQJ from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap mkdir -p /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap chown root /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap chmod 700 /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap tee -a /tmp/tmpffuOQJ/root/.ssh/authorized_keys from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b it's from Leander compute log http://paste.openstack.org/show/18149/ And I was sure I have few vms with metadata server access issue and without ssh connection issue . It looks like I need some additional tests and need more time for code reading : - ) And by the way if we did not have ssh key in authorised key I thought we would have different output from ssh client something like this debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA b8:7e:bd:80:ae:72:61:51:8f:d0:fc:e1:7d:47:81:a6 debug1: Host '10.1.0.7' is known and matches the ECDSA host key. debug1: Found key in /root/.ssh/known_hosts:2 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: rhelkey.pem debug1: read PEM private key done: type RSA debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). Leander ouput was looking strange for me: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer Connection reset by peer after debug1: SSH2_MSG_KEXINIT sent it looks like network issue. Anyway thank you very much. On Fri, May 25, 2012 at 3:19 AM, Sébastien Han han.sebast...@gmail.comwrote: Ok ok, no offense in my previous emails :) Good to know that everything is working. Cheers. On Fri, May 25, 2012 at 1:00 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm in no way saying that openstack is to blame for the current problem, but it occurred
Re: [Openstack] Can't ssh into instance
It depend on your image, but if you picked an image from the ubuntu cloud image repo you should use the 'ubuntu' user to ssh connect otherwise won't be able to connect to your instance. Hope it helps! On Fri, May 25, 2012 at 11:04 AM, Anton Haldin ahal...@griddynamics.comwrote: Thank you very much guys Sébastien and Leander It was very interesting case. I thought if I see this lines in compute.log then sshkey injection was successfully 1fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap qemu-nbd -c /dev/nbd15 /var/lib/nova/instances/instance-000c/disk from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap kpartx -a /dev/nbd15 from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap mount /dev/mapper/nbd15p1 /tmp/tmpffuOQJ from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap mkdir -p /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap chown root /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap chmod 700 /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap tee -a /tmp/tmpffuOQJ/root/.ssh/authorized_keys from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b it's from Leander compute log http://paste.openstack.org/show/18149/ And I was sure I have few vms with metadata server access issue and without ssh connection issue . It looks like I need some additional tests and need more time for code reading : - ) And by the way if we did not have ssh key in authorised key I thought we would have different output from ssh client something like this debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA b8:7e:bd:80:ae:72:61:51:8f:d0:fc:e1:7d:47:81:a6 debug1: Host '10.1.0.7' is known and matches the ECDSA host key. debug1: Found key in /root/.ssh/known_hosts:2 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: rhelkey.pem debug1: read PEM private key done: type RSA debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). Leander ouput was looking strange for me: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer Connection reset by peer after debug1:
Re: [Openstack] Can't ssh into instance
Thank you Sébastien yes I see. It looks like ssh key injection through nbd is not sufficient for using ubuntu login. On Fri, May 25, 2012 at 1:10 PM, Sébastien Han han.sebast...@gmail.comwrote: It depend on your image, but if you picked an image from the ubuntu cloud image repo you should use the 'ubuntu' user to ssh connect otherwise won't be able to connect to your instance. Hope it helps! On Fri, May 25, 2012 at 11:04 AM, Anton Haldin ahal...@griddynamics.comwrote: Thank you very much guys Sébastien and Leander It was very interesting case. I thought if I see this lines in compute.log then sshkey injection was successfully 1fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap qemu-nbd -c /dev/nbd15 /var/lib/nova/instances/instance-000c/disk from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap kpartx -a /dev/nbd15 from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap mount /dev/mapper/nbd15p1 /tmp/tmpffuOQJ from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap mkdir -p /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap chown root /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap chmod 700 /tmp/tmpffuOQJ/root/.ssh from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b403f91fc4e8b132647ec] Running cmd (subprocess): sudo nova-rootwrap tee -a /tmp/tmpffuOQJ/root/.ssh/authorized_keys from (pid=1208) execute /usr/lib/python2.7/dist-packages/nova/utils.py:219 2012-05-24 13:25:00 DEBUG nova.utils [req-5c28365b-7b33-4788-b044-d0144efaeeb8 b568e6c7911042339705042bb75ee1a7 1a4f83e3463b it's from Leander compute log http://paste.openstack.org/show/18149/ And I was sure I have few vms with metadata server access issue and without ssh connection issue . It looks like I need some additional tests and need more time for code reading : - ) And by the way if we did not have ssh key in authorised key I thought we would have different output from ssh client something like this debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-ctr hmac-md5 none debug1: kex: client-server aes128-ctr hmac-md5 none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA b8:7e:bd:80:ae:72:61:51:8f:d0:fc:e1:7d:47:81:a6 debug1: Host '10.1.0.7' is known and matches the ECDSA host key. debug1: Found key in /root/.ssh/known_hosts:2 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: rhelkey.pem debug1: read PEM private key done: type RSA debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). Leander ouput was looking strange for me: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for
Re: [Openstack] Can't ssh into instance
On Fri, 25 May 2012, Anton Haldin wrote:
Thank you very much guys Sébastien and Leander
It was very interesting case.
I thought if I see this lines in compute.log then sshkey injection was
successfully
Given functional metadata service,
ssh key injection from the host is not necessary for ubuntu images.
And I was sure I have few vms with metadata server access issue and
without ssh connection issue .
Ubuntu cloud images do not have any ssh HostKey generated inside them
(/etc/ssh/ssh_host_{ecdsa,dsa,rsa}_key). The keys are generated by
cloud-init after it finds a metadata service. Without a metadata service,
they do not get generated. ssh will drop your connections immediately
without HostKeys.
This is arguably a bug, and there is an open bug to have the keys
generated independent of ability to find a metadata service
(http://pad.lv/906669).
It looks like I need some additional tests and need more time for code
reading : - )
Fix the metadata issue, you're going to want it.
Alternatively, use configdrive
(http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/configdrive/README)
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Thank you Scott for your answer
Now I think I have full understanding of this case.
Without keys openssh server would reset ssh session immediately.
On Fri, May 25, 2012 at 6:01 PM, Scott Moser smo...@ubuntu.com wrote:
On Fri, 25 May 2012, Anton Haldin wrote:
Thank you very much guys Sébastien and Leander
It was very interesting case.
I thought if I see this lines in compute.log then sshkey injection was
successfully
Given functional metadata service,
ssh key injection from the host is not necessary for ubuntu images.
And I was sure I have few vms with metadata server access issue and
without ssh connection issue .
Ubuntu cloud images do not have any ssh HostKey generated inside them
(/etc/ssh/ssh_host_{ecdsa,dsa,rsa}_key). The keys are generated by
cloud-init after it finds a metadata service. Without a metadata service,
they do not get generated. ssh will drop your connections immediately
without HostKeys.
This is arguably a bug, and there is an open bug to have the keys
generated independent of ability to find a metadata service
(http://pad.lv/906669).
It looks like I need some additional tests and need more time for code
reading : - )
Fix the metadata issue, you're going to want it.
Alternatively, use configdrive
(
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/configdrive/README
)
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.comwrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.comwrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.comwrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
it can be an issue of openssh: one more link http://www.gossamer-threads.com/lists/openssh/dev/51483?do=post_view_threaded#51483 On Thu, May 24, 2012 at 5:48 PM, Anton Haldin ahal...@griddynamics.comwrote: what you can try to do: you can mount machine image and check /var/log/auth.log it can be kind of network issue for example like this one http://fixunix.com/ssh/74058-ssh-hang-after-ssh2_msg_kexinit-sent.html if so you can try to change net.ipv4.tcp_rmem nova-compute.log is looking fine. On Thu, May 24, 2012 at 5:30 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 2:27 PM, Anton Haldin ahal...@griddynamics.comwrote: I'm sorry Leander I did not note that you are using ubuntu and try to connect by using root account I thought it may be better to use ubuntu account. But in my machine when I was trying to use root account , ssh client told me about it. On Thu, May 24, 2012 at 5:19 PM, Anton Haldin ahal...@griddynamics.comwrote: I doubt you have desktop components on this host ( compute node) with GUI. in this case you can check that file injection of ssh_key was successfully in nova-compute.log On Thu, May 24, 2012 at 5:13 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I currently can't access the vnc console directly due to routing issues. The instances is running private ip's over on vlan and public ip over another vlan (the host machine only has 1 network interface). There is no routing information available to guide all traffic to the host machine, and the network administrator isn't around to set up the routing in our firewall at the moment. On Thu, May 24, 2012 at 2:04 PM, Anton Haldin ahal...@griddynamics.com wrote: it looks like OS was running successfully. if you have network access to this host ( compute node) you can to try use vnc client to connect to your instance. you can find port number from libvirt.xml: virsh dumpxml instance- On Thu, May 24, 2012 at 4:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.comwrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
I've formatted the host machine and reinstalled openstack, just in case. Now i am only getting connection refused. On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
It's not an open-ssh issue. Your virtual machine simply can't fetch the metadata, cloud-init can't to be more accurate. Without this your ssh key is not imported. This is why the machine is well running, you can ping it but you can't access it because the authorized_keys file on the vm is not fulfill. If you are only running a nova-compute node, installing nova-api-metadata will do the trick! Also verify those values in your nova.conf : - --vncserver_proxyclient_address=IP_CURRENT_NODE - --vncserver_listen=IP_CURRENT_NODE - --ec2_dmz_host=IP_CURRENT_NODE - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Let us know a little more about your setup :) Cheers! On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
On Thu, 24 May 2012, Leander Bessa Beernaert wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ the issue is that the instance cannot access the metadata service. The node is not routing traffic destined to 169.254.169.254 to an API server. This will not work until that is fixed. Cirros instances will boot, and let you log in, and verify/troubleshoot that. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Adding the following to my config file solved my problem!! Thanks!! - routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Regards, Leander On Thu, May 24, 2012 at 4:24 PM, Sébastien Han han.sebast...@gmail.comwrote: It's not an open-ssh issue. Your virtual machine simply can't fetch the metadata, cloud-init can't to be more accurate. Without this your ssh key is not imported. This is why the machine is well running, you can ping it but you can't access it because the authorized_keys file on the vm is not fulfill. If you are only running a nova-compute node, installing nova-api-metadata will do the trick! Also verify those values in your nova.conf : - --vncserver_proxyclient_address=IP_CURRENT_NODE - --vncserver_listen=IP_CURRENT_NODE - --ec2_dmz_host=IP_CURRENT_NODE - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Let us know a little more about your setup :) Cheers! On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Just a question i forgot, on a multi-host senario, the IP_CURRENT_NODE is the compute node's ip right? Currently i'm only running everything on a single host. On Thu, May 24, 2012 at 4:32 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Adding the following to my config file solved my problem!! Thanks!! - routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Regards, Leander On Thu, May 24, 2012 at 4:24 PM, Sébastien Han han.sebast...@gmail.comwrote: It's not an open-ssh issue. Your virtual machine simply can't fetch the metadata, cloud-init can't to be more accurate. Without this your ssh key is not imported. This is why the machine is well running, you can ping it but you can't access it because the authorized_keys file on the vm is not fulfill. If you are only running a nova-compute node, installing nova-api-metadata will do the trick! Also verify those values in your nova.conf : - --vncserver_proxyclient_address=IP_CURRENT_NODE - --vncserver_listen=IP_CURRENT_NODE - --ec2_dmz_host=IP_CURRENT_NODE - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Let us know a little more about your setup :) Cheers! On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Perfect! Yes in a multi-host scenario it's the IP address of the compute node itself :) Cheers! On Thu, May 24, 2012 at 5:34 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Just a question i forgot, on a multi-host senario, the IP_CURRENT_NODE is the compute node's ip right? Currently i'm only running everything on a single host. On Thu, May 24, 2012 at 4:32 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Adding the following to my config file solved my problem!! Thanks!! - routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Regards, Leander On Thu, May 24, 2012 at 4:24 PM, Sébastien Han han.sebast...@gmail.comwrote: It's not an open-ssh issue. Your virtual machine simply can't fetch the metadata, cloud-init can't to be more accurate. Without this your ssh key is not imported. This is why the machine is well running, you can ping it but you can't access it because the authorized_keys file on the vm is not fulfill. If you are only running a nova-compute node, installing nova-api-metadata will do the trick! Also verify those values in your nova.conf : - --vncserver_proxyclient_address=IP_CURRENT_NODE - --vncserver_listen=IP_CURRENT_NODE - --ec2_dmz_host=IP_CURRENT_NODE - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Let us know a little more about your setup :) Cheers! On Thu, May 24, 2012 at 4:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Maybe you missed the rules of security group? Rogério Gonçalves roge...@gmail.com Cel: (11) 8840-9790 On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've formatted the host machine and reinstalled openstack, just in case. Now i am only getting connection refused. On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.comwrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
First rule of security group. Do not talk about security group. j/k On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves roge...@gmail.comwrote: Maybe you missed the rules of security group? Rogério Gonçalves roge...@gmail.com Cel: (11) 8840-9790 On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've formatted the host machine and reinstalled openstack, just in case. Now i am only getting connection refused. On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
Why did you reinstall everything? There is no just in case, I mean you solved your issue, it was from your configuration not from openstack :) It's a routing issue, same as earlier. Check again those parameters, specially the first one: - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Still in all-in-one setup? Cheers :) On Thu, May 24, 2012 at 8:40 PM, Matt Joyce matt.jo...@cloudscaling.comwrote: First rule of security group. Do not talk about security group. j/k On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves roge...@gmail.comwrote: Maybe you missed the rules of security group? Rogério Gonçalves roge...@gmail.com Cel: (11) 8840-9790 On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've formatted the host machine and reinstalled openstack, just in case. Now i am only getting connection refused. On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Can't ssh into instance
I'm in no way saying that openstack is to blame for the current problem, but it occurred to me that my install could have script failed somewhere along the way without me knowing (i might have forgotten to mention that in the previous post :s). Adding those two lines solved my problem. I've already mentioned it earlier, perhaps the mail wasn't sent to the list. And yes, i'm still using a all-in-one setup for now. Thanks for the tip. On Thu, May 24, 2012 at 9:03 PM, Sébastien Han han.sebast...@gmail.comwrote: Why did you reinstall everything? There is no just in case, I mean you solved your issue, it was from your configuration not from openstack :) It's a routing issue, same as earlier. Check again those parameters, specially the first one: - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Still in all-in-one setup? Cheers :) On Thu, May 24, 2012 at 8:40 PM, Matt Joyce matt.jo...@cloudscaling.comwrote: First rule of security group. Do not talk about security group. j/k On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves roge...@gmail.comwrote: Maybe you missed the rules of security group? Rogério Gonçalves roge...@gmail.com Cel: (11) 8840-9790 On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've formatted the host machine and reinstalled openstack, just in case. Now i am only getting connection refused. On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing
Re: [Openstack] Can't ssh into instance
Ok ok, no offense in my previous emails :) Good to know that everything is working. Cheers. On Fri, May 25, 2012 at 1:00 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I'm in no way saying that openstack is to blame for the current problem, but it occurred to me that my install could have script failed somewhere along the way without me knowing (i might have forgotten to mention that in the previous post :s). Adding those two lines solved my problem. I've already mentioned it earlier, perhaps the mail wasn't sent to the list. And yes, i'm still using a all-in-one setup for now. Thanks for the tip. On Thu, May 24, 2012 at 9:03 PM, Sébastien Han han.sebast...@gmail.comwrote: Why did you reinstall everything? There is no just in case, I mean you solved your issue, it was from your configuration not from openstack :) It's a routing issue, same as earlier. Check again those parameters, specially the first one: - --routing_source_ip=IP_CURRENT_NODE - --my_ip=IP_CURRENT_NODE Still in all-in-one setup? Cheers :) On Thu, May 24, 2012 at 8:40 PM, Matt Joyce matt.jo...@cloudscaling.comwrote: First rule of security group. Do not talk about security group. j/k On Thu, May 24, 2012 at 9:35 AM, Rogerio Goncalves roge...@gmail.comwrote: Maybe you missed the rules of security group? Rogério Gonçalves roge...@gmail.com Cel: (11) 8840-9790 On Thu, May 24, 2012 at 12:12 PM, Leander Bessa Beernaert leande...@gmail.com wrote: I've formatted the host machine and reinstalled openstack, just in case. Now i am only getting connection refused. On Thu, May 24, 2012 at 3:01 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Compute log: Log: http://paste.openstack.org/show/18149/ I've tried bot root and ubuntu as account names (ssh -i key.pem root@10.1.2.3 and ssh -i key.pem ubuntu@10.1.2.3) and the result is still Read from socket failed: Connection reset by peer On Thu, May 24, 2012 at 1:57 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Complete log: http://paste.openstack.org/show/18144/ On Thu, May 24, 2012 at 1:49 PM, Anton Haldin ahal...@griddynamics.com wrote: you can try to look in console.log for this instance On Thu, May 24, 2012 at 4:41 PM, Leander Bessa Beernaert leande...@gmail.com wrote: No, at the moment the vnc console isn't working yet. I haven't gotten that far yet. On Thu, May 24, 2012 at 1:29 PM, Anton Haldin ahal...@griddynamics.com wrote: t can be an issue on OS side in instance ? do you have vnc access for this instance? On Thu, May 24, 2012 at 2:56 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I'm having trouble sshing into the created instances. At first i was getting the following error: ssh -i testkey.pem root@10.1.1.3 -v OpenSSH_5.9p1 Debian-5ubuntu1, 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 10.1.1.3 [10.1.1.3] port 22. debug1: Connection established. debug1: identity file testkey.pem type -1 debug1: identity file testkey.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1 debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer I then proceeded to reboot the machine and all it's services. However, now i can't even get that far. I'm alway faced with a connection refused. I've added the permissions for port 22 and icmp in the default security group and i'm also able to ping the instances. I'm using the openstack packages provided with ubuntu 12.04. Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to
