From: Germain Le Chapelain <german@lanvaux.fr>
To: cygwin@cygwin.com, "René Berber" <rene.berber@gmail.com>
Subject: Re: AutoSSH problem
Date: Sun, 03 Jun 2018 02:34:00 -0000 [thread overview]
Message-ID: <41cd0c5f-4819-0c14-dde5-a1bea7a1030a@lanvaux.fr> (raw)
In-Reply-To: <1527971948.18809.ezmlm@cygwin.com>
On 06/01/18 23:03, René Berber wrote:
> The behavior looks normal.
>
> Quoting from the autossh man page:
>
> "Startup behaviour
>
> If the ssh session fails with an exit status of 1 on the very first try,
> autossh
>
> 1.' will assume that there is some problem with syntax or the connection
> setup, and will exit rather than retrying;
>
> 2.' There is a "starting gate" time. If the first ssh process fails
> within the first few seconds of being started, autossh assumes that it
> never made it "out of the starting gate", and exits. This is to handle
> initial failed authentication, connection, etc. This time is 30 seconds
> by default, and can be adjusted (see the AUTOSSH_GATETIME environment
> variable below). If AUTOSSH_GATETIME is set to 0, then both behaviours
> are disabled: there is no "starting gate", and autossh will restart even
> if ssh fails on the first run with an exit status of 1. The "starting
> gate" time is also set to 0 when the -f flag to autossh is used. "
Thank you for highlighting this point, René.
You are right: it "looks" normal, from far :)
However, looking closer to the log, you should see (or not, looking back
at it it's not obvious) that I halted the connection the server about
three minutes in:
> 2018/06/01 13:17:41 autossh[20680]: set alarm for 600 secs
> Connection to lanvaux.fr closed by remote host.
> 2018/06/01 13:20:52 autossh[20680]: check on child 4988
So something still doesn't line up. :/
I may try my dumpo-magic (I think it's actually called "DebugDiag",
https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/)
But as said earlier it's probably going to poop (no pun intended) about
AutoSSH being a cygwin program.
I will take a read on how debugging goes on Cygwin, or look at AutoSSH
1.4e (and how to get it.)
Kindest regards,
Thank you for your answer!
--
Germain Le Chapelain
Lanvaux Computer Games Limited
http://lanvaux.fr
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2018-06-03 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1527971948.18809.ezmlm@cygwin.com>
2018-06-03 2:34 ` Germain Le Chapelain [this message]
[not found] <1527847720.60014.ezmlm@cygwin.com>
2018-06-01 22:32 ` Germain Le Chapelain
2018-06-01 23:03 ` René Berber
2018-05-31 12:16 Germain Le Chapelain
2018-06-01 5:44 ` Andrew Schulman
2018-06-04 15:38 ` Greg Freemyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41cd0c5f-4819-0c14-dde5-a1bea7a1030a@lanvaux.fr \
--to=german@lanvaux.fr \
--cc=cygwin@cygwin.com \
--cc=rene.berber@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).