RE: SFTP client Expect 5.43 via PASE intermittently failing

Tim,

<If this message "ssh_exchange_identification: read: Connection reset by peer" is consistently the one that appears on failure then it occurs when the client makes a connection and tries to read the initial SSH banner>
Yes, this is consistent, occurs immediately.

I also found a 2nd spoolfile that is being created 1 second prior to the above failure.
This is the RPGLE program that is building the Expect script for the SFTP.

So the failure isn't the SFTP, but the building of the Expect script.
The SFTP can't initiate without a good, valid script.

My apologies to all,

send: spawn id exp3 not open
while executing
"send "yes\n"
(file "/home/SFTPXFER/TOA/toageneric.expect" line 18)

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tim Bronski
Sent: Wednesday, January 20, 2016 1:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: SFTP client Expect 5.43 via PASE intermittently failing

If this message "ssh_exchange_identification: read: Connection reset by peer" is consistently the one that appears on failure then it occurs when the client makes a connection and tries to read the initial SSH banner. The read fails. This indicates that a connection to the SSH server application has not been made or it is dropped immediately before any exchange occurs. I would suspect it is being dropped at the firewall but that's a WAG.

On 1/20/2016 4:34 PM, Charles Wilt wrote:

idk...98.8889% up time for a non-robust process seems pretty good.

By non-robust, I mean it doesn't apparently have any built in retries.

If the connection failure is during the handshake as the OP seems to
imply. Then as Scott pointed out the involvement of DNS over UDP;
then the non-robustness of UDP comes into play.

The app should be robust enough to try again.

Now if the reset is coming in the middle of the process, yeah maybe
something is funny.

Charles


On Wed, Jan 20, 2016 at 10:15 AM, Tim Bronski <tim.bronski@xxxxxxxxx> wrote:

I would be VERY unhappy with 40 connection failures in 60 days.
Something is wobbly there.


On 1/20/2016 2:53 PM, Charles Wilt wrote:

On Wed, Jan 20, 2016 at 4:58 AM, Tim Bronski <tim.bronski@xxxxxxxxx>
wrote:

X is the login grace time that's set in the server's sshd config.
The

default is 120 seconds. The login process should be sub second. 40
failures in 60 days is extraordinarily high.


​40 failures in 3600 attempts over 60 days doesn't seem to bad to me.

Just
over 1%...

Charles
​

--
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.