Opened 3 weeks ago

Last modified 3 weeks ago

#59469 assigned defect

mosh @1.3.2: mosh-server crashing

Reported by: letaage Owned by: quentinmit (Quentin Smith)
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: mountainlion Cc:
Port: mosh

Description

Hello,

I have been using mosh for a while on a Mac mini running OS X 10.8.5. I installed mosh using macports and usually connect via my Android mobile phone using JuiceSSH. Other than the occasional Mac firewall issue it has worked well.

But recently mosh stopped working, I think it coincided with a recent upgrade of macports or perhaps perl but I am not sure. I am not really a software person so bear with me!

The fault manifests itself with the following error message:

Nothing received from the server on UDP port 60003

I have tried debugging the problem following the advice on the mosh website. The error message normally indicates problem connecting to the port used by mosh-server. I have disabled the firewall on my server and the problem persists. I have even tried connecting on the local host without luck and manually connecting - nothing is working.

I have uninstalled mosh, run port clean mosh -all, and reinstalled mosh but it didn't fix the problem.

I finally discovered that mosh-server is actually crashing soon after launching so I tracked down the crash log (see attached file) and would appreciate if I can get some help working out what is causing the problem.

Here's the version of Xcode installed on my machine:

slim:~ tom$ /usr/bin/xcodebuild -version
Xcode 5.1.1
Build version 5B1008

I left a bug report at the mosh GitHub site but haven't had a response yet, so trying another channel.

Cheers, Tom

Attachments (1)

mosh-server_2019-10-22-231533_slim.crash.log (9.1 KB) - added by letaage 3 weeks ago.
mosh-server crash log

Download all attachments as: .zip

Change History (4)

Changed 3 weeks ago by letaage

mosh-server crash log

comment:1 Changed 3 weeks ago by jmroot (Joshua Root)

Cc: quentin@… removed
Keywords: mountainlion added; Snowleopard removed
Owner: set to quentinmit
Status: newassigned

comment:2 Changed 3 weeks ago by quentinmit (Quentin Smith)

Unfortunately, your crash log does not actually include the mosh-server log. The traceback indicates that mosh is intentionally aborting after writing a log message about why it aborted. :)

To capture mosh's debug output, please run in one terminal:

$ mosh-server new -vvv


MOSH CONNECT 60004 yZKRNQIJBEeDxRrNZuXo5Q

mosh-server (mosh 1.3.2) [build mosh 1.3.2]
Copyright 2012 Keith Winstein <mosh-devel@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 = 88991]
$ 

Even though it returns to your prompt, mosh will continue printing its log. Then to attach to the session, in another terminal, run

MOSH_KEY=yZKRNQIJBEeDxRrNZuXo5Q mosh-client 127.0.0.1 60004

Obviously you'll need to replace the key and port with whatever your mosh-server printed out. This should either get you a working mosh connection, or hopefully a crash with useful debug information in the first window.

comment:3 Changed 3 weeks ago by letaage

Hi,

I tried as you suggested and got the following message in the first window:

slim:~ tom$ mosh-server new -vvv


MOSH CONNECT 60005 wsoiqkdc4QYadlVmiAPOHw

mosh-server (mosh 1.3.2) [build mosh 1.3.2]
Copyright 2012 Keith Winstein <mosh-devel@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 = 17516]
slim:~ tom$ Server now attached to client at 127.0.0.1:62581
[libprotobuf FATAL google/protobuf/parse_context.cc:159] CHECK failed: ptr >= limit_end_: 
libc++abi.dylib: terminate called throwing an exception

slim:~ tom$ 

Not much of an error message, but does that help at all?

Let me know if there is anything else you need to know or want me to try.

Cheers, Tom

Note: See TracTickets for help on using tickets.