code-server: new install 500 error

500 VS Code failed to load. Above error is shown on fresh install on ubuntu18.04 .

warn discarding socket connection: vscode is not running

warn discarding socket connection: vscode is not running

(node:24) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [ChildProcess]. Use emitter.setMaxListeners() to increase limit

(Use node --trace-warnings ... to show where the warning was created)

(node:24) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [ChildProcess]. Use emitter.setMaxListeners() to increase limit

events.js:292

throw er; // Unhandled ‘error’ event

^

Error: This socket has been ended by the other party

at Socket.writeAfterFIN [as write] (net.js:453:14)

at h.write (/usr/lib/code-server/lib/vscode/out/vs/server/entry.js:169:115)

at g.write (/usr/lib/code-server/lib/vscode/out/vs/server/entry.js:170:363)

at g._writeNow (/usr/lib/code-server/lib/vscode/out/vs/server/entry.js:160:350)

at Immediate.<anonymous> (/usr/lib/code-server/lib/vscode/out/vs/server/entry.js:160:288)

at processImmediate (internal/timers.js:456:21)

Emitted ‘error’ event on Socket instance at:

at emitErrorNT (net.js:1340:8)

at processTicksAndRejections (internal/process/task_queues.js:84:21) {

code: ‘EPIPE’

}

error VS Code exited unexpectedly with code 1

warn discarding socket connection: vscode is not running

warn discarding socket connection: vscode is not running

warn discarding socket connection: vscode is not running

warn discarding socket connection: vscode is not running

warn discarding socket connection: vscode is not running

warn discarding socket connection: vscode is not running

  • Web Browser: chrome

  • Local OS: ubuntu18.04

  • Remote OS: macos

  • code-server --version: 3.4.1

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 17 (7 by maintainers)

Most upvoted comments

We have a bug where the stdout is not being logged so I think gathering the install logs and stdout separately will be helpful. For example:

yarn global add code-server --verbose > install.log 2>&1
code-server > run.log 2>&1

Then browse to the code-server page to trigger the 500 and submit the install.log and run.log files.