Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error spawning child process ENOENT

See original GitHub issue

code-server version: 1.621
OS Version: Docker 18.09.04 build d14af54266 on Digital Ocean Ubuntu 18.04 1Gb ram

Description

After installing the Rust (rls) extension and opening a rust source file the rustup process fails to spawn as a child process. I believe this can occur in other cases when trying to spawn a child process but this is the easiest one to reproduce.

[Error - 15:49:11] Starting client failed
Error: spawn rustup ENOENT
	at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
	at onErrorNT (internal/child_process.js:362:16)
	at _combinedTickCallback (internal/process/next_tick.js:139:11)
	at process._tickCallback (internal/process/next_tick.js:181:9)

Steps to Reproduce

Launch code-server inside Docker using the following command (same as in the readme): docker run -it -p 127.0.0.1:8443:8443 -v "${PWD}:/home/coder/project" codercom/code-server:1.621 --allow-http --no-auth.
Search for “rust” in the Extensions pane, and install the Rust (rls) extension.
Create a new file in your project titled hello.rs.
Open the newly created rust source file.
You will see error notifications and when looking at the Output window you will be able to see the error message.

Issue Analytics

State:
Created 4 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

mdeabreucommented, Apr 19, 2019

Interesting, I’ll try running VSCode natively on an Ubuntu machine with the rust plugin and see if I run into the same issue.

Yes, without the "-l" argument for internal shells they don’t act like “logged in” shells and so the path isn’t updated by the profile script. In that case the cargo bin directory is not in the path.

(Apologies for formatting, on mobile)

0reactions

qwertycodycommented, Sep 22, 2020

Reporting back on this issue because this thread helped me, here is what fixed my issues on RHEL…

yum install rust rustc rls

Top Results From Across the Web

How do I debug "Error: spawn ENOENT" on node.js?

Spawn may emit the ENOENT error if the filename command (i.e, 'some-command') does not exist in at least one of the directories defined...

spawn node ENOENT" when using child_process in Node.js

The reason the spawn was broken in the first place was because we were overriding the child process' environment variables in options.env which ......

[Solved-5 Solutions] Error spawn enoent on node.js - Wikitechy

Spawn may emit the ENOENT error if the filename command (i.e, 'some-command') does not exist in at least one of the directories defined...

Error: spawn ps ENOENT · Issue #132 - GitHub

After tests complete, I get Error: spawn ps ENOENT , and exits with code ... _handle.onexit (internal/child_process.js:232:19) at onErrorNT ...

Error spawn ENOENT on node js | Edureka Community

Hii team, When I get the following error: events.js:72 throw er; // Unhandled ' ... at Process.ChildProcess.