Re: Mosh log

289 views
Skip to first unread message

Dean Beeler

unread,
Dec 27, 2012, 4:43:33 PM12/27/12
to is...@googlegroups.com
Have you checked the firewall to make sure UDP is let in and out through the chosen ports (in this case, 60005)?

Dean

On Saturday, December 22, 2012 11:05:15 AM UTC-8, Michael Hogle wrote:
I am having problems connecting with mosh to my Linux server. I have no issues when connecting from anywhere else not using iSSH. Can someone look at this log and tell me if I have things misconfigured? This is pretty frustrating as I have a friend that successfully connects to mosh on this server using iSSH.


2012-12-22 18:49:14 +0000 x.xx.xx: Looking up host "x.xx.xx"
2012-12-22 18:49:15 +0000 x.xx.xx: Connecting to 209.xxx.xx.xx port xxx
2012-12-22 18:49:17 +0000 x.xx.xx: Server version: SSH-2.0-OpenSSH_5.3
2012-12-22 18:49:17 +0000 x.xx.xx: We claim version: SSH-2.0-PuTTY_Local:_Nov_20_2012_01:31:33
2012-12-22 18:49:17 +0000 x.xx.xx: Using SSH protocol version 2
2012-12-22 18:49:17 +0000 x.xx.xx: Doing Diffie-Hellman group exchange
2012-12-22 18:49:17 +0000 x.xx.xx: Doing Diffie-Hellman key exchange with hash SHA-256
2012-12-22 18:49:20 +0000 x.xx.xx: Host key fingerprint is:
2012-12-22 18:49:20 +0000 x.xx.xx: ssh-rsa 2048 37:38:33:e6:98:12:23:f5:b6:47:91:d1:f4:28:25:b6
2012-12-22 18:49:20 +0000 w.in.gs: Initialised AES-256 SDCTR client->server encryption
2012-12-22 18:49:20 +0000 x.xx.xx: Initialised HMAC-SHA1 client->server MAC algorithm
2012-12-22 18:49:20 +0000 x.xx.xx: Initialised AES-256 SDCTR server->client encryption
2012-12-22 18:49:20 +0000 x.xx.xx: Initialised HMAC-SHA1 server->client MAC algorithm
2012-12-22 18:49:20 +0000 x.xx.xx: Pageant is running. Requesting keys.
2012-12-22 18:49:20 +0000 x.xx.xx: Pageant has 0 SSH-2 keys
2012-12-22 18:49:27 +0000 x.xx.xx: Sent password
2012-12-22 18:49:27 +0000 x.xx.xx: Access granted
2012-12-22 18:49:27 +0000 x.xx.xx: Opened channel for session
2012-12-22 18:49:27 +0000 x.xx.xx: Requesting X11 forwarding
2012-12-22 18:49:27 +0000 x.xx.xx: Remote debug message: No xauth program; cannot forward with spoofing.
2012-12-22 18:49:27 +0000 x.xx.xx: X11 forwarding refused
2012-12-22 18:49:27 +0000 x.xx.xx: Requesting OpenSSH-style agent forwarding
2012-12-22 18:49:27 +0000 x.xx.xx: Agent forwarding enabled
2012-12-22 18:49:28 +0000 x.xx.xx: Allocated pty (ospeed 38400bps, ispeed 38400bps)
2012-12-22 18:49:28 +0000 x.xx.xx: Started a shell/command
2012-12-22 18:49:28 +0000 x.xx.xx: mosh:
MOSH CONNECT 60005 <KEY>

2012-12-22 18:49:28 +0000 x.xx.xx: mosh: Starting  session to 209.xxx.xx.xx:60005
2012-12-22 18:49:28 +0000 x.xx.xx: mosh: Mosh-spawning ssh line reported:
mosh-server (mosh 1.2.3)
Copyright 2012 Keith Winstein <mosh-...@mit.edu>
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

[mosh-server detached, pid = 2603]

2012-12-22 18:49:28 +0000 x.xx.xx: Server sent command exit status 0
2012-12-22 18:49:28 +0000 x.xx.xx: Disconnected: All channels closed

It looks like it connects successfully, but I see nothing on the screen. After a minute or 2 the mosh-server process dies.

I'm at a loss.

Dean Beeler

unread,
Dec 29, 2012, 3:32:24 AM12/29/12
to iSSH/iX11
The final posts on this thread should set you straight:
https://groups.google.com/group/issh/browse_thread/thread/dc8d45644ac814a5

Dean

On Dec 28, 1:48 pm, Zane Revai <z...@revai.org> wrote:
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: Looking up host "192.168.0.x"
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: Connecting to 192.168.0.x port 22
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: Server version: SSH-2.0-OpenSSH_5.9
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: We claim version: SSH-2.0-PuTTY_Local:_Nov_20_2012_01:31:33
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: Using SSH protocol version 2
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: Doing Diffie-Hellman group exchange
> 2012-12-28 21:15:16 +0000 Zane's Mac Mini: Doing Diffie-Hellman key exchange with hash SHA-256
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Host key fingerprint is:
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: ssh-rsa 2048
> Removed
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Initialised AES-256 SDCTR client->server encryption
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Initialised HMAC-SHA1 client->server MAC algorithm
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Initialised AES-256 SDCTR server->client encryption
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Initialised HMAC-SHA1 server->client MAC algorithm
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Pageant is running. Requesting keys.
> 2012-12-28 21:15:19 +0000 Zane's Mac Mini: Pageant has 0 SSH-2 keys
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Access granted
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Opened channel for session
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Requesting X11 forwarding
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: X11 forwarding refused
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Requesting OpenSSH-style agent forwarding
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Agent forwarding enabled
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Allocated pty (ospeed 38400bps, ispeed 38400bps)
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Started a shell/command
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Mosh reported: mosh-server needs a UTF-8 native locale to run.
>
> Unfortunately, the local environment ([no charset variables]) specifies
> the character set "US-ASCII",
>
> The client-supplied environment ([no charset variables]) specifies
> the character set "US-ASCII".
>
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Mosh reported: LANG=
> LC_COLLATE="C"
> LC_CTYPE="C"
> LC_MESSAGES="C"
> LC_MONETARY="C"
>
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Mosh reported: LC_NUMERIC="C"
> LC_TIME="C"
> LC_ALL=
>
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Server sent command exit status 1
> 2012-12-28 21:15:20 +0000 Zane's Mac Mini: Disconnected: All channels closed
>
> That is what happens connecting to my Mac Mini running OS X v10.8.2. I installed mosh v1.2.3 via MacPorts and have done everything I can to get my Mac to use en_US.UTF-8 but even though its all set properly I get the above errors. I also get several dialogs all talking about locale is wrong and its using US-ASCII. I'll attach the pics from my iPhone as soon as I can!!
> Any thoughts???
>
> Here's the locale settings on same Mac with mosh off in iSSH:
>
> ZMini:~ zane$ locale
> LANG="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_CTYPE="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_ALL="en_US.UTF-8"
> ZMini:~ zane$

Michael Hogle

unread,
Dec 29, 2012, 4:59:20 PM12/29/12
to is...@googlegroups.com
There is no firewall on my local network. It works with any non-iSSH mosh client.

Niklas Ögren

unread,
Dec 30, 2012, 3:35:51 AM12/30/12
to is...@googlegroups.com
Yes, but as we have already discussed and solved this, more than once, please go ahead and read and try the last posts in that thread Dean posted:

"LANG=en_US.UTF-8 mosh-server" is one of a couple of possible solutions to your problem.

/n
> --
> You received this message because you are subscribed to the Google Groups "iSSH/iX11" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/issh/-/xwvhuNo-j6MJ.
> To post to this group, send email to is...@googlegroups.com.
> To unsubscribe from this group, send email to issh+uns...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/issh?hl=en.

Michael Hogle

unread,
Dec 30, 2012, 11:56:08 AM12/30/12
to is...@googlegroups.com
Thanks for your words of wisdom Niklas. 

Actually I've already tried the suggestions in that post before I created my own post, because after trying all these little fixes I am still not able to get mosh to work successfully. My bad, I thought this was a support forum, I must have gotten lost at the ego forum instead.

It sucks when you spend $10+ on an app, and then still get attitude when trying to get any support for it. Wow.

Phil Jones

unread,
Dec 30, 2012, 12:03:02 PM12/30/12
to is...@googlegroups.com
Michael,

To be fair to Niklas, your reply said that you didn't have a firewall on your local network - it made no mention of trying the other suggestions in the thread that Dean linked.

There is no need for your vitriolic post.

Take care, and I hope you get your problem resolved.

Thanks,

Phil

To view this discussion on the web visit https://groups.google.com/d/msg/issh/-/2gaPlLOLwyYJ.

Michael Hogle

unread,
Dec 30, 2012, 12:33:10 PM12/30/12
to is...@googlegroups.com
Niklas,

Actually I was having problems connecting to another FreeBSD server as well. The post Dean linked to did help me resolve my connection issues connecting directly to that machine. However, that did not fix my issue connecting to the machine I posted in my original post. For now I'll say this resolves my issue because I only needed mosh to work on one of these machines. I can use direct ssh from one to the other for now.

Thanks for all your help. If I was snooty I apologize. 

~Michael

Niklas Ögren

unread,
Dec 30, 2012, 12:51:23 PM12/30/12
to is...@googlegroups.com, is...@googlegroups.com
Sorry if you feel that way. Perhaps it's due to the fact that English is not my native language. But I had the exact same problem as you, and solved it with the nice help from Dean when we finally understood what was wrong. The way the mosh protocol works put more requirements on the surrounding things, and the environment that is created by the mosh-server needs the utf-8 setting correctly. The way I first solved it was by putting in the necessary settings in the .bashrc file. It was not enough to put it in the bash profile file, because it was sourced too late. 

All your answers are already in the forums, and google should perhaps pick it up for you. Might also be documented on Dean's help pages. 

I think Dean has made an excellent job, and that iSSH is worth the money. 

/n

To view this discussion on the web visit https://groups.google.com/d/msg/issh/-/2gaPlLOLwyYJ.

Niklas Ögren

unread,
Dec 30, 2012, 1:24:20 PM12/30/12
to is...@googlegroups.com
Michael,

No worries. Hopefully google indexed some more details around the problem by now.. and perhaps it will solve the problem for your other box as well.

/n
> To view this discussion on the web visit https://groups.google.com/d/msg/issh/-/EFa7LKpyZvYJ.

Zane Revai

unread,
Jan 4, 2013, 11:18:58 AM1/4/13
to is...@googlegroups.com
Thanks a bunch. The Path setting worked for me. Perhaps add it to the in app help or the iSSH FAQ??

I was able to connect after entering the following into the Path configuration box for my current connection in iSSH:

LANG=en_US.UTF-8 mosh-server

Reply all
Reply to author
Forward
0 new messages