[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] ssh between DomUs in Xen3.2


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "David Grundy" <grundy@xxxxxxx>
  • Date: Fri, 13 Jun 2008 11:02:20 -0700 (PDT)
  • Delivery-date: Fri, 13 Jun 2008 11:02:56 -0700
  • Importance: Normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello Waldirio:

Thanks for you advice.  I was not aware of strace.  I followed you advice
and posted the output at http://pastebin.com/m1eec8e45.  The output is a
little cryptic for me so any assistance would be greatly appreciated.

Cheers,

David


>    Hello David
>
>  Try check with command below
>
> # strace ssh 192.168.17.200
>
> If need help to debug a trace, create a output file and post in
> http://pastebin.com/ for example, later send here.
>
> Good Luck
> Waldirio
>
> 2008/6/12 David Grundy <grundy@xxxxxxx>:
>
>>
>> Hello All:
>>
>> I am working with a small cluster running Xen3.2 on Scientific Linux 5
>> on
>> the worker nodes.  I have been trying to mess around with some different
>> network configurations and have stumbled upon something that seems very
>> strange to me.  My DomUs can connect with the Dom0 and external network
>> (ping,ssh,etc), I can connect with the DomUs from the head node and Dom0
>> (ping,ssh,etc) and I can ping the DomUs from one another BUT when I try
>> to
>> ssh from one DomU to another it just hangs.
>>
>>
>> [root@localhost ~]# ssh -vvv 192.168.17.200
>> OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
>> debug1: Reading configuration data /etc/ssh/ssh_config
>> debug1: Applying options for *
>> debug2: ssh_connect: needpriv 0
>> debug1: Connecting to 192.168.17.200 [192.168.17.200] port 22.
>> debug1: Connection established.
>> debug1: permanently_set_uid: 0/0
>> debug1: identity file /root/.ssh/identity type -1
>> debug3: Not a RSA1 key file /root/.ssh/id_rsa.
>> debug2: key_type_from_name: unknown key type '-----BEGIN'
>> debug3: key_read: missing keytype
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug3: key_read: missing whitespace
>> debug2: key_type_from_name: unknown key type '-----END'
>> debug3: key_read: missing keytype
>> debug1: identity file /root/.ssh/id_rsa type 1
>> debug1: identity file /root/.ssh/id_dsa type -1
>>
>> And here it just hangs...
>>
>> In the /var/log/secure file on the vm I am trying to connect to the
>> following line shows up after I <ctrl> c the ssh command:
>>
>> Jun 12 14:13:03 localhost sshd[2478]: Did not receive identification
>> string
>> from ::ffff:192.168.17.201
>>
>> I have located the following post that was never responded to.  I am not
>> sure if this is the same problem.
>>
>> http://lists.xensource.com/archives/html/xen-users/2008-01/msg00951.html
>>
>> I have not modified the xend-config.sxp file so I am using all the
>> default
>> scripts.  I have tried this on Xen3.1.0 and I am finding the same
>> problem.
>>
>> Any help would be greatly appreciated.
>>
>> David
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
>>
>
>
>
> --
> ______________
> Atenciosamente
> Waldirio
> msn: wmp@xxxxxxxxxxxxx
> Site: www.waldirio.com.br
> Blog: blog.waldirio.com.br
> PGP: www.waldirio.com.br/public.html
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users





_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.