Nodejs OPENSSH - 错误：在 TCP.onStreamRead 读取 ECONNRESET

Question

在一个 node.js 脚本中，我使用 openssh 从一台 Windows 服务器执行 dos 命令到另一台远程 Windows 服务器。远程服务器已运行 openssh 服务器，我已在 ssh shell 中对其进行了测试，

ssh Administrator@hostname

但是当我从 node.js 尝试时，这不起作用。这是我正在使用的代码，

var SSH = require('simple-ssh');
var command = 'dir /b' //or dir 
ssh = new SSH({
            host: 'XXX.XXX.XX.XXX',
            user: 'Administrator',
            pass: 'password'
        });

ssh.exec(command, {
    out: function(stdout) {
        console.log(stdout);
    }
}).start(); 

ssh.on('error', function(err) {
            console.log('In Start, something went wrong.');
            console.log(err);           
            ssh.end();
        });

上面的脚本抛出错误，

In Start, something went wrong.
{ Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
  errno: 'ECONNRESET',
  code: 'ECONNRESET',
  syscall: 'read',
  level: 'client-socket' }

请注意，当我将“ls”作为命令时，这会给出输出，以及相同的错误消息。最终，我想在远程 Windows 服务器上执行一个带有一些输入参数的 bat 文件。我不知道这个错误以及如何处理它。

我在 windows 10 VM 上安装了 openssh，如下 url， http://linuxbsdos.com/2015/07/30/how-to-install-openssh-on-windows-10/

这里是我的windows虚拟机，C:\Program Files\OpenSSH\etc\sshd_config文件内容，

#   $OpenBSD: sshd_config,v 1.101 2017/03/14 07:19:07 djm Exp $
# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/bin:/usr/sbin:/sbin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh_host_rsa_key
#HostKey /etc/ssh_host_dsa_key
#HostKey /etc/ssh_host_ecdsa_key
#HostKey /etc/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# Logging
#SyslogFacility AUTH
#LogLevel INFO
LogLevel DEBUG3

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin prohibit-password
PermitRootLogin yes
StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile  .ssh/authorized_keys

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCreds yes

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of 'PermitRootLogin without-password'.
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM no

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /var/run/sshd.pid
MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none   

# default banner path
Banner /etc/banner.txt

# override default of no subsystems
Subsystem   sftp    /usr/sbin/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#   X11Forwarding no
#   AllowTcpForwarding no
#   PermitTTY no
#   ForceCommand cvs server

谢谢

Answer 1

解决了半天，经常为这些ssh到远程服务器而苦苦挣扎，ssh-node包中的ssh.compose()无法关闭连接，发现远程windows ssh服务器仍然生成许多名为sshd的进程并没有被关闭，在ssh.compose之后，node.js会抛出错误Error: read ECONNRESET at TCP.onStreamRead，无法被代码捕获。我找到了很多参考，可能是TCP连接仍在工作中，尚未关闭。所以我尝试参考ssh-node代码并使用

ssh.connection.destroy()

指向ssh2包中的Client.prototype.destroy方法，所以Error: read ECONNRESET at TCP.onStreamRead的错误会消失，连接会完全关闭。

Answer 2

经过一番努力，我发现openssh只能执行远程服务器的“C:\Program Files\OpenSSH\bin”中存在的命令。命令“dir”失败，因为它不在 bin 文件夹中，但适用于“ls”命令。当我们将所需的 bat 文件放入 openssh/bin 文件夹时，它就可以工作。我曾尝试放置一个虚拟 bat 文件，

@echo off
"C:\Program Files\utility\run.bat" "variable1" "variable2"
exit /b

我们可以在ssh命令中调用这个bat文件

var SSH = require('simple-ssh');
var command = 'dummy.bat'  
ssh = new SSH({
            host: 'XXX.XXX.XX.XXX',
            user: 'Administrator',
            pass: 'password'
        });

ssh.exec(command, {
    out: function(stdout) {
        console.log(stdout);
    }
}).start(); 

ssh.on('error', function(err) {
            console.log('In Start, something went wrong.');
            console.log(err);           
            ssh.end();
        });

虽然它会引发 ECONNRESET 错误，但会执行所需的 bat 文件。

我不确定这是否可以通过任何其他设置更改来实现。这只是解决问题的一种解决方法。

谢谢

Answer 3

嗯，默认情况下 ssh2 将每分钟发送一个应用程序级别的 ping/keepalive 数据包。这当然可以调整。 配置 openssh 服务器。 ClientAlive* 是服务器设置，ServerAlive* 是客户端设置。

https://www.simplified.guide/ssh/disable-timeout