Crash on Debian 8
See original GitHub issuecode-server
version: 1.31.1-100- OS Version: debian 8
$ uname -a
Linux iZ28iwnpx2bZ 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux
$ cat /etc/debian_version
8.11
Steps to Reproduce
error message:
$ ./code-server -d /home/zoe/codes/vscode-workdir -h 127.0.0.1 -p 60443 --allow-http
INFO code-server v1.31.1-100
INFO Additional documentation: http://github.com/codercom/code-server
INFO Initializing {"data-dir":"/home/zoe/codes/vscode-workdir","working-dir":"/home/zoe/codes/vscode-workdir/code-server-1.31.1-100-linux-x64","log-dir":"/home/zoe/codes/vscode-workdir/logs/20190307051426515"}
INFO Starting shared process [1/5]...
INFO Starting webserver... {"host":"127.0.0.1","port":60443}
WARN No certificate specified. This could be insecure.
WARN Documentation on securing your setup: https://coder.com/docs
INFO
INFO Password: e9eb8d0a4d8c913247d49cc0
INFO
INFO Started (click the link below to open):
INFO http://localhost:60443/
INFO
INFO Connected to shared process
ERROR SHARED stderr {"data":"Uncaught Exception: Error: ENOENT: no such file or directory, open '/home/zoe/codes/vscode-workdir/Backups/workspaces.json'\n\nError: ENOENT: no such file or directory, open '/home/zoe/codes/vscode-workdir/Backups/workspaces.json'\n at Timeout.eval [as _onTimeout] (eval at exports.requireModule (/home/zoe/codes/vscode-workdir/code-server-1.31.1-100-linux-x64/code-server:468:27371), <anonymous>:71445:31)\n at ontimeout (timers.js:475:11)\n at tryOnTimeout (timers.js:310:5)\n at Timer.listOnTimeout (timers.js:270:5)\n"}
INFO WebSocket opened / {"client":1,"ip":"127.0.0.1"}
INFO Created data directory
internal/child_process.js:323
throw errnoException(err, 'spawn');
^
Error: spawn ENOMEM
at _errnoException (util.js:1024:11)
at ChildProcess.spawn (internal/child_process.js:323:11)
at Object.exports.spawn [as _spawn] (child_process.js:502:9)
at t.async (/home/zoe/codes/vscode-workdir/code-server-1.31.1-100-linux-x64/code-server:716:35021)
at e.exports (/home/zoe/codes/vscode-workdir/code-server-1.31.1-100-linux-x64/code-server:716:34522)
at e (/home/zoe/codes/vscode-workdir/code-server-1.31.1-100-linux-x64/code-server:716:33324)
at Timeout.c [as _onTimeout] (/home/zoe/codes/vscode-workdir/code-server-1.31.1-100-linux-x64/code-server:716:33617)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:8
- Comments:27 (10 by maintainers)
Top Results From Across the Web
crash(8) — crash — Debian unstable - Debian Manpages
Crash is a tool for interactively analyzing the state of the Linux system while it is running, or after a kernel crash has...
Read more >How to on enable kernel crash dump on Debian Linux - nixCraft
Describes how to install, set up and enable Linux kernel crash dump on Debian Linux version 9/10/11 using ... Est. reading time, 8...
Read more >Debian 8 crashes once every few days - Unix Stack Exchange
I'm running Debian 8 on Linode 32 GB and once every few days the system crashes. ... Here are the graphs of Linode...
Read more >Brave crashes on Debian 8 (installed with aptitude as ... - GitHub
Brave crashes on Debian 8 (installed with aptitude as per instruction) #6930 ... I'm on 3.16.0-4 (Jessie default) and get similar issues.
Read more >Crash in gss_get_mic in mech_eap on Debian 8
Copied from email I sent to the Moonshot list] : Hi, all, I'm seeing a weird crash in gss-server on Debian 8. After...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve got it working now by creating
Backups/workspaces.json
manually in the workdir directory with the following content:And then creating the folder
{workdir}/User/workspaceStorage
.@NiklasMerz you can export
LOG_LEVEL
todebug
and it’ll provide verbose output.