I had debugged and found that from devcloud unable to ssh to the router vm.
When it tries to execute the GetDomRVersionCmd its getting failing and router
vm is getting destroyed.
I had tried manually ssh to router vm am getting Permission denied (publickey)
I had tried changing the permission of my ssh folder and keys, still the same
issue.
-rw------- 1 root root 1674 Apr 1 15:38 id_rsa.cloud
-rw------- 1 root root 394 Apr 1 15:38 id_rsa.cloud.pub
-rw------- 1 root root 884 Apr 1 15:51 known_hosts
How to resolve this issue?
Here is the output of ssh with verbose mode. Am using devCloud with xenserver
ssh -i .ssh/id_rsa.cloud -p 3922 169.254.0.105
Permission denied (publickey).
root@devcloud:~# ssh -vvv -i .ssh/id_rsa.cloud -p 3922 169.254.0.105
OpenSSH_6.0p1 Debian-4, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 169.254.0.105 [169.254.0.105] port 3922.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug3: Incorrect RSA1 identifier
debug3: Could not load ".ssh/id_rsa.cloud" as a RSA1 public key
debug1: identity file .ssh/id_rsa.cloud type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file .ssh/id_rsa.cloud-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1
Debian-6+squeeze1
debug1: match: OpenSSH_5.5p1 Debian-6+squeeze1 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-4
debug2: fd 3 setting O_NONBLOCK
debug3: put_host_port: [169.254.0.105]:3922
debug3: load_hostkeys: loading entries for host "[169.254.0.105]:3922" from
file "/root/.ssh/known_hosts "
debug3: load_hostkeys: found key type RSA in file /root/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs:
ssh-rsa-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sh
a1
debug2: kex_parse_kexinit:
ssh-rsa-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-v01@open
ssh.com,ssh-dss-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-dss
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,z...@openssh.com,zlib
debug2: kex_parse_kexinit: none,z...@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.
com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.
com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 123/256
debug2: bits set: 512/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 58:de:8b:d7:2b:8e:01:2e:cd:f4:58:86:27:e4:94:39
debug3: put_host_port: [169.254.0.105]:3922
debug3: put_host_port: [169.254.0.105]:3922
debug3: load_hostkeys: loading entries for host "[169.254.0.105]:3922" from
file "/root/.ssh/known_hosts
"
debug3: load_hostkeys: found key type RSA in file /root/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for host "[169.254.0.105]:3922" from
file "/root/.ssh/known_hosts
"
debug3: load_hostkeys: found key type RSA in file /root/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug1: Host '[169.254.0.105]:3922' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug2: bits set: 510/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: .ssh/id_rsa.cloud (0xb89fff78)
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred
gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: .ssh/id_rsa.cloud
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).
> -----Original Message-----
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Saturday, March 30, 2013 2:07 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Unable to start domR(VR) in devcloud using laster 4.1/master.
>
> You should roll back your devcloud VM to the original and try again.
>
> On DevCloud2, I notice that sometimes the xapi0 bridge loses its ip address
> and
> hence loses the 169.254.0.0/16 route.
> You can work around this by
> ifconfig xapi0 (check for ipv4 address)
> ip route show (check for 169.254 route)
>
> If these are missing
>
> ifconfig xapi0 169.254.169.254 netmask 255.255.0.0 ip route show
>
>
> On 3/29/13 1:06 PM, "Marcus Sorensen" <shadow...@gmail.com> wrote:
>
> >Xen? KVM?
> >
> >Generally GetDomRVersionCmd failing is only a symptom, it usually means
> >that cloudstack was never able to communicate with the system vm. You
> >would need to look at whether the VM actually started on the host, and
> >some of the text around when the VM was deployed to get any meaningful
> >errors. Sometimes this happens when there are bugs around updating the
> >SSH keys, or if the filesystem is corrupt on the system vm.
> >
> >
> >On Fri, Mar 29, 2013 at 1:40 PM, Rajesh Battala
> ><rajesh.batt...@citrix.com> wrote:
> >> Hi All,
> >>
> >> VR is not getting started failing the instance creation. Anywork
> >>around for this issue?
> >>
> >> [network.router.VirtualNetworkApplianceManagerImpl]
> >>(Job-Executor-1:job-8) Unable to get the template/scripts version of
> >>router r-4-VM due to: getDomRVersionCmd failed INFO
> >>[cloud.vm.VirtualMachineManagerImpl] (Job-Executor-1:job-8) The guru
> >>did not like the answers so stopping VM[DomainRouter|r-4-VM] ERROR
> >>[cloud.vm.VirtualMachineManagerImpl] (Job-Executor-1:job-8) Failed to
> >>start instance VM[DomainRouter|r-4-VM]
> >> com.cloud.utils.exception.ExecutionException: Unable to start
> >>VM[DomainRouter|r-4-VM] due to error in finalizeStart, not retrying
> >> at
> >>com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineMan
> a
> >>ger
> >>Impl.java:808)
> >> at
> >>com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImp
> l
> >>.ja
> >>va:471)
> >> at
> >>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(Virt
> >>ual
> >>NetworkApplianceManagerImpl.java:2606)
> >> at
> >>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtu
> >>alR
> >>outer(VirtualNetworkApplianceManagerImpl.java:1815)
> >> at
> >>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRoute
> >>rs(
> >>VirtualNetworkApplianceManagerImpl.java:1915)
> >> at
> >>com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirt
> >>ual
> >>RouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1893)
> >> at
> >>com.cloud.network.element.VirtualRouterElement.prepare(VirtualRouterEl
> >>eme
> >>nt.java:208)
> >> at
> >>com.cloud.network.NetworkManagerImpl.prepareElement(NetworkManager
> Impl
> >>.ja
> >>va:1541)
> >> at
> >>com.cloud.network.NetworkManagerImpl.prepareNic(NetworkManagerImpl.
> jav
> >>a:1
> >>658)
> >> at
> >>com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.jav
> a:1
> >>599
> >>)
> >> at
> >>com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineMan
> a
> >>ger
> >>Impl.java:746)
> >> at
> >>com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImp
> l
> >>.ja
> >>va:471)
> >> at
> >>org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.depl
> >>oyV
> >>irtualMachine(VMEntityManagerImpl.java:212)
> >> at
> >>org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl
> >>.de
> >>ploy(VirtualMachineEntityImpl.java:209)
> >> at
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerIm
> pl.j
> >>ava
> >>:3860)
> >> at
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerIm
> pl.j
> >>ava
> >>:3458)
> >> at
> >>com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerIm
> pl.j
> >>ava
> >>:3444)
> >> at
> >>com.cloud.utils.component.ComponentInstantiationPostProcessor$Intercep
> >>tor
> >>Dispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> >> at
> >>org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(Deploy
> VM
> >>Cmd
> >>.java:379)
> >>
> >>
> >> Thanks
> >> Rajesh Battala
