Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The process tried to write to a nonexistent pipe #2292

Closed
MingweiSamuel opened this issue Feb 4, 2020 · 3 comments
Closed

The process tried to write to a nonexistent pipe #2292

MingweiSamuel opened this issue Feb 4, 2020 · 3 comments

Comments

@MingweiSamuel
Copy link

@MingweiSamuel MingweiSamuel commented Feb 4, 2020

  • VSCode Version: 1.41.1 (26076a4de974)
  • Local OS Version: Windows 10 Pro 1903
  • Remote OS Version: Ubuntu 18.04 (Also seemed to fail on 16.04)
  • Remote Extension/Connection Type: SSH (from git)

Steps to Reproduce:

  1. Remote-SSH: Connect to Host...
  2. Select "rusty.us-central1-a.pickbanwin" (or other)
  3. Could not establish a connection to "rusty.us-central1-a.pickbanwin". The process tried to write to a nonexistent pipe.

Does this issue occur when you try this locally?: ??
Does this issue occur when you try this locally and all extensions are disabled?: ??

Visual Studio SSH Log:

[16:19:09.207] remote-ssh@0.48.0
[16:19:09.207] win32 x64
[16:19:09.210] SSH Resolver called for "ssh-remote+rusty.us-central1-a.pickbanwin", attempt 1
[16:19:09.211] SSH Resolver called for host: rusty.us-central1-a.pickbanwin
[16:19:09.211] Setting up SSH remote "rusty.us-central1-a.pickbanwin"
[16:19:09.294] Using commit id "26076a4de974ead31f97692a0d32f90d735645c0" and quality "stable" for server
[16:19:09.299] Testing ssh with ssh -V
[16:19:09.419] ssh exited with code: 0
[16:19:09.419] Got stderr from ssh: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[16:19:09.430] Using SSH config file "C:\Users\Mingw\.ssh\config"
[16:19:09.430] Running script with connection command: ssh -T -D 50291 -F C:\Users\Mingw\.ssh\config rusty.us-central1-a.pickbanwin bash
[16:19:09.435] Install and start server if needed
[16:19:09.444] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[16:19:09.642] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> �]0;C:\WINDOWS\System32\cmd.exe�
[16:19:09.643] Got some output, clearing connection timeout
[16:19:09.674] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
[16:19:10.269] > mingw@104.198.238.242: Permission denied (publickey).
> 
[16:19:10.279] > The process tried to write to a nonexistent pipe.
> 
[16:19:10.608] "install" terminal command done
[16:19:10.608] Install terminal quit with output: The process tried to write to a nonexistent pipe.
[16:19:10.608] Received install output: The process tried to write to a nonexistent pipe.
[16:19:10.610] Resolver error: The process tried to write to a nonexistent pipe
[16:19:10.621] ------




Running SSH directly works fine:

Mingw@DESKTOP-ATA708C MINGW64 ~
$ ssh rusty.us-central1-a.pickbanwin -v
OpenSSH_8.1p1, OpenSSL 1.1.1d  10 Sep 2019
debug1: Reading configuration data /c/Users/Mingw/.ssh/config
debug1: /c/Users/Mingw/.ssh/config line 35: Applying options for rusty.us-central1-a.pickbanwin
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to rusty.us-central1-a.pickbanwin [104.198.238.242] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\Mingw\\.ssh\\google_compute_engine type 0
debug1: identity file C:\\Users\\Mingw\\.ssh\\google_compute_engine-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to 104.198.238.242:22 as 'Mingw'
debug1: using hostkeyalias: compute.3071513492723804736
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:EW289KddhmVBpDUhsaSl+xrIbrycZEOdvJZH/45HeFM
debug1: using hostkeyalias: compute.3071513492723804736
debug1: Host 'compute.3071513492723804736' is known and matches the ECDSA host key.
debug1: Found key in C:\\Users\\Mingw\\.ssh\\google_compute_known_hosts:1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: C:\\Users\\Mingw\\.ssh\\google_compute_engine RSA SHA256:JBDnFQ6/Wekgjhpw7nKB2DV5CenRttD2vcNKGEuR04k explicit
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\Mingw\\.ssh\\google_compute_engine RSA SHA256:JBDnFQ6/Wekgjhpw7nKB2DV5CenRttD2vcNKGEuR04k explicit
debug1: Server accepts key: C:\\Users\\Mingw\\.ssh\\google_compute_engine RSA SHA256:JBDnFQ6/Wekgjhpw7nKB2DV5CenRttD2vcNKGEuR04k explicit
debug1: Authentication succeeded (publickey).
Authenticated to 104.198.238.242 ([104.198.238.242]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-1029-gcp x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Tue Feb  4 00:22:06 UTC 2020

  System load:  0.04               Processes:           93
  Usage of /:   19.9% of 19.21GB   Users logged in:     0
  Memory usage: 6%                 IP address for ens4: 10.128.0.5
  Swap usage:   0%

 * Overheard at KubeCon: "microk8s.status just blew my mind".

     https://microk8s.io/docs/commands#microk8s.status

6 packages can be updated.
0 updates are security updates.


Last login: Tue Feb  4 00:21:54 2020 from 136.152.143.81
Mingw@rusty:~$ debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
logout
debug1: channel 0: free: client-session, nchannels 1
Connection to 104.198.238.242 closed.
Transferred: sent 3116, received 4084 bytes, in 3.6 seconds
Bytes per second: sent 860.1, received 1127.3
debug1: Exit status 0
@MingweiSamuel

This comment has been minimized.

Copy link
Author

@MingweiSamuel MingweiSamuel commented Feb 4, 2020

Remote-SSH Nightly also doesnt work:

[16:35:11.223] Log Level: 3
[16:35:11.226] remote-ssh-nightly@2019.12.44160
[16:35:11.226] win32 x64
[16:35:11.231] SSH Resolver called for "ssh-remote+rusty.us-central1-a.pickbanwin", attempt 1
[16:35:11.232] SSH Resolver called for host: rusty.us-central1-a.pickbanwin
[16:35:11.232] Setting up SSH remote "rusty.us-central1-a.pickbanwin"
[16:35:11.314] Using commit id "26076a4de974ead31f97692a0d32f90d735645c0" and quality "stable" for server
[16:35:11.324] Testing ssh with ssh -V
[16:35:11.457] ssh exited with code: 0
[16:35:11.457] Got stderr from ssh: OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[16:35:11.466] Running script with connection command: ssh -T -D 50703 rusty.us-central1-a.pickbanwin bash
[16:35:11.469] Install and start server if needed
[16:35:11.478] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[16:35:11.766] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> �]0;C:\WINDOWS\System32\cmd.exe�
[16:35:11.767] Got some output, clearing connection timeout
[16:35:11.796] > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
[16:35:12.421] > mingw@104.198.238.242: Permission denied (publickey).
> 
[16:35:12.430] > The process tried to write to a nonexistent pipe.
> 
[16:35:12.787] "install" terminal command done
[16:35:12.788] Install terminal quit with output: The process tried to write to a nonexistent pipe.
[16:35:12.788] Received install output: The process tried to write to a nonexistent pipe.
[16:35:12.790] Resolver error: The process tried to write to a nonexistent pipe
[16:35:12.799] ------





@roblourens

This comment has been minimized.

Copy link
Member

@roblourens roblourens commented Feb 4, 2020

This is the real error:

Permission denied (publickey).

Does your ssh config point at the key? Or since it looks like you are using mingw ssh instead of windows' ssh, what if you point remote.SSH.path at that ssh binary?

@MingweiSamuel

This comment has been minimized.

Copy link
Author

@MingweiSamuel MingweiSamuel commented Feb 4, 2020

Fantastic, thanks. Setting remote.SSH.path to c:\Program Files\Git\usr\bin\ssh.exe worked. (I assume it was finding C:\Windows\System32\OpenSSH\ssh.exe before)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.