<div dir="ltr">Ok - I have created a new issue -- <a href="https://github.com/mobile-shell/mosh/issues/705">https://github.com/mobile-shell/mosh/issues/705</a> -- with the information you asked for. When I was typing, I think I was just typing garbage, but I have also tried systematically typing the alphabet and it doesn't seem like a particular character is the culprit. <div><br></div><div>Thanks,</div><div>Dan<br><div><br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 26, 2015 at 3:34 PM john hood <<a href="mailto:cgull@glup.org">cgull@glup.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Oh, Cygwin, that beloved reliable Unix
emulation.<br>
<br>
There is a problem in the trace, I see mosh-client reading both
the network socket and terminal input after select() returns 0 fds
ready...and this is mysterious.<br>
<br>
I think the behavior with script may be about the type of terminal
Mosh is running on in Cygwin, rather than character encoding.
IIRC Cygwin handles ptys and "real" terminals differently (and I
think a Cygwin command invoked in a Windows console is a third
variant)<br>
<br>
We need more info. Please open an issue at
<a href="https://github.com/mobile-shell/mosh/issues/new" target="_blank">https://github.com/mobile-shell/mosh/issues/new</a> with this info:<br>
<br>
OSes and versions on both client and server<br>
mosh version on both client and server<br>
Where did you get the client mosh from? The Cygwin installer or a
local build?<br>
What are you using for the Cygwin terminal? Are you invoking Mosh
from a Unix or Windows shell prompt?<br>
What, if any, is the message mosh-client prints on exit? (A
screenshot of the terminal window would be nice, if possible.)<br>
In the trace you've given, you appear to be typing at Mosh when
the session closes. What were you typing?<br>
<br>
regards,<br>
<br>
--jh</div></div><div bgcolor="#FFFFFF" text="#000000"><div><br>
<br>
On 12/26/15 1:59 PM, Dan Schwartz wrote:<br>
</div></div><div bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
<div dir="ltr">
<div style="font-size:13px;line-height:19.5px">Thanks John -</div>
<div style="font-size:13px;line-height:19.5px">I tried these
with the following outcomes:</div>
<div style="font-size:13px;line-height:19.5px"><br>
</div>
<span style="font-size:13px;line-height:19.5px">* --no-init did
not provide any additional information</span>
<div style="font-size:13px;line-height:19.5px">* Interestingly,
when I run mosh under script, I do not reproduce the problem.
The mosh-client does not exit. I can use this as a workaround
for now I guess. Maybe this points in the direction of a
character encoding issue?</div>
<div style="font-size:13px;line-height:19.5px">* I have attached
the strace output from my system. I'm running this in cygwin
on a machine that is running Windows 10.1. I can't say that
I'm immediately able to glean anything from this output.</div>
<div style="font-size:13px;line-height:19.5px"><br>
</div>
<div style="font-size:13px;line-height:19.5px">Thanks,<br>
Dan</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Dec 25, 2015 at 10:45 PM john hood <<a href="mailto:cgull@glup.org" target="_blank"></a><a href="mailto:cgull@glup.org" target="_blank">cgull@glup.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On
12/24/15 8:06 AM, Dan Schwartz wrote:<br>
> Hi mosh community -<br>
><br>
> I'm trying to get set up with mosh, and I'm having an
issue that the<br>
> mosh-client is exiting unexpectedly (at least I think
it is the<br>
> mosh-client that causes this). I am able to establish a
connection<br>
> between the client and server - the server is receiving
packets, and I<br>
> can even run 'ls' and get back directory contents if I
am fast<br>
> enough...and then the client exits (regardless of what
I type, the<br>
> client seems to exit after between 30s and 1 minute).
The server side<br>
> debug info is pasted below. I see a 'received state -1'
which seems<br>
> suspicious, but I'm not sure what this means or how to
debug what's<br>
> happening.<br>
><br>
> Any help would be appreciated.<br>
><br>
> Thanks,<br>
> Dan<br>
><br>
> Here is the server side debug info:<br>
><br>
> [24498] Sent [26=>29] id 29, frag 0 ack=24,
throwaway=26, len=54,<br>
> frame rate=31.25, timeout=102, srtt=62.7<br>
> [24532] Sent [26=>30] id 30, frag 0 ack=24,
throwaway=26, len=48,<br>
> frame rate=31.25, timeout=102, srtt=62.7<br>
> [24565] Received state -1 [coming from 24, ack 29]<br>
> [24565] Sent [29=>30] id 31, frag 0 ack=-1,
throwaway=29, len=43,<br>
> frame rate=31.25, timeout=97, srtt=63.3<br>
><br>
> [mosh-server is exiting.]<br>
Yes, state -1 is a request for shutdown. So your client is
terminating<br>
in a somewhat-orderly way. The question is, why is it doing
this<br>
without any action from you or the server?<br>
<br>
Things to try:<br>
<br>
* Start mosh with the --no-init option. Sometimes errors
are written<br>
just before the screen is cleared on exit. This option
disables that<br>
screen clearing.<br>
* If that fails, use the script command to get a typescript
of your session.<br>
* If neither of these produce anything useful, please try
using your OS<br>
system-call tracer (truss, ktrace, dtrace) to capture a
record of what<br>
mosh-client is actually doing.<br>
<br>
Please open an issue on Github with anything you find, it's
the best way<br>
to handle problems like this.<br>
<br>
regards,<br>
<br>
--jh<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</div></blockquote></div></div></div></div>