-
Notifications
You must be signed in to change notification settings - Fork 5.9k
ENOENT: no such file or directory, open '/root/.code-server/Backups/workspaces.json' #121
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
Comments
me too |
1 similar comment
me too |
I also found this while running on Google cloud |
Please avoid |
I'm getting the very same error in the beginning. Later, when I navigate to the code-server's address in my browser, login with the generated password and mess around in vscode it suddenly crashes.
Traceback:
|
I get same error at tecent clould centos 7.4 64 ,Docker version 18.09.3, build 774a1f4 Thanks~ |
+1 |
I get same error in Ubuntu 16.04 on AWS clouds ubuntu@ip-172-31-25-334:~/coder$ sudo ./code-server -p 80 |
Debian 9 64 bit (fresh installation)
|
I can confirm this happens in Container Linux/CoreOS stable as well, running on Digital Ocean (as well as Debian 9.7 as other have reported). |
I got same error in Ubuntu 16.04 on aliyun cloud root@xxx:~/workdir# docker run -t -p 127.0.0.1:8443:8443 -v "${PWD}:/root/project" codercom/code-server --allow-http --no-auth
INFO code-server development
INFO Additional documentation: http://github.com/codercom/code-server
INFO Initializing {"data-dir":"/root/.local/share/code-server","working-dir":"/root/project","log-dir":"/root/.cache/code-server/logs/20190311023801696"}
INFO Starting shared process [1/5]...
INFO Starting webserver... {"host":"0.0.0.0","port":8443}
WARN No certificate specified. This could be insecure.
WARN Documentation on securing your setup: https://coder.com/docs
WARN Launched without authentication.
INFO
INFO Started (click the link below to open):
INFO http://localhost:8443/
INFO
INFO Connected to shared process
ERROR SHARED stderr {"data":"Uncaught Exception: Error: ENOENT: no such file or directory, open '/root/.local/share/code-server/Backups/workspaces.json'\n\nError: ENOENT: no such file or directory, open '/root/.local/share/code-server/Backups/workspaces.json'\n at Timeout.setTimeout [as _onTimeout] (eval at exports.requireModule (/usr/local/bin/code-server:468:27625), <anonymous>:67388:31)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)\n"} |
Same error on Ubuntu 18.04 Digital Ocean standard vps while just trying to run binary version.
|
Same error on Ubuntu 16.04 and no file from data directory can be seen in vs code's explorer |
Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-1030-azure x86_64) Windows Azure Virtual Machine ERROR SHARED stderr {"data":"Uncaught Exception: Error: ENOENT: no such file or directory, open '/home/<user>/.code-server/Backups/workspaces.json'\n\nError: ENOENT: no such file or directory, open '/home/<user>/.code-server/Backups/workspaces.json'\n at Timeout.eval [as _onTimeout] (eval at exports.requireModule (/home/<user>/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":"<hoster_ip>"}
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/<user>/code-server-1.31.1-100-linux-x64/code-server:716:35021)
at e.exports (/home/<user>/code-server-1.31.1-100-linux-x64/code-server:716:34522)
at e (/home/<user>/code-server-1.31.1-100-linux-x64/code-server:716:33324)
at Timeout.c [as _onTimeout] (/home/<user>/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) |
I managed to make it work with specifying
But I still see the same error in the console. |
@xuemind seems like your error is caused because the VM ran out of memory. You might need to add a gb or two of swap so the binary is able to boot properly without running our of memory. I was able to get it running on a GCP micro instance with 600mb of memory like this |
Same here on Ubuntu 18.10 server via the binary. However by specifying |
@ndom91 what does your workspaces.json file look like? I'm having trouble finding an example and am receiving a |
I get this error when i try to run the binary on Ubuntu Server 18.04: INFO code-server v1.0.0
I also tried version 1.31.0-100 with same results. When i try to run the docker, it also gives me the same error. |
I just created an empty one, i.e. EDIT: I just looked at it, now that I've run this once or twice, and its still empty haha |
@ndom91 I tried creating the Backups folder with an empty workspace.json but now i get this: I guess i need a proper workspaces.json? What version are you using? Does anyone know whats in that file? Even better, does anyone have a default one that they can share? |
After creating a workspaces.json in the desired directory and filling it with the content {
"folders": [
{
"path": "/home/<username_redacted>/code-server/workspace/folders"
}
]
} I get a new error:
|
it is working now with latest docker image. Thanks! |
Not working for me. I'm running using the Docker oneliner behind an nginx reverse proxy. All I get is a black screen.
In the browser console, I get this:
Pulled the |
Same issue with the latest docker on centos7. Any workaround? |
Check if the port 8443 is allowed in ufw rules |
For anyone who might be interested. here is the ID of the image I pulled.
|
I have instance with Ubuntu 18.04 (LTS), installed the latest as of today Coder release which is
And everything is working except that same error, and I'm guessing that's why my integrated terminal is black and cannot see anything? |
This error doesn't actually cause any issues. I would suspect the black terminal is caused by something else |
@coadler for example? It was that why just after fresh machine install and fresh code-server startup. No settings changes or anything. Any ideas to debug it? |
Aaaaah, heck. Forget it, just realized to try to disable the Brave's Shields blocker :D Sometimes blocks too much, sometimes not enough. |
This issue is closed, is not a bug of code-server? I noticed that the code-server running normally, should I just ignore this error for now? |
@liupengf12 yes. edit: Or at least you can add the file with this content {
"rootURIWorkspaces": [],
"folderURIWorkspaces": [],
"emptyWorkspaceInfos": [],
"emptyWorkspaces": []
} It's a default one. |
@ndom91 hello, i tried your method but then i got the following error
|
I'm having the same issue here. I tried to launch it in DigitalOcean container, |
it cannot be just empty file. try to put the contents that from my previous comment. |
@yusef-ho try running |
@tunnckoCore it's not an empty and it is as your comment of content.
|
Just wanted to note that it is working for me on a fresh install via the binary now as well. Without any fooling around with folders or arguments. |
This is the error I am currently getting on google cloud platform, with both Ubuntu 16 and 18 |
@okabamac what version/release of the binary are you running? |
@multishifties 1.691-vsc1.33.0 |
@multishifties I also tried with 1.691-vsc1.33.0 released 14 hours ago and I am having the unexpected end of json input error |
1.691-vsc1.33.0 |
I pushed a commit which should resolve the JSON message, but it doesn't cause any issues so you can safely ignore it until the next release. |
@code-asher OK that will be amazing |
code-server
version: v1.31.1-100Steps to Reproduce
The text was updated successfully, but these errors were encountered: