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

Code-OSS Server Setup: Error server contents are corrupted #60

Closed
Qfl3x opened this issue Feb 8, 2023 · 9 comments
Closed

Code-OSS Server Setup: Error server contents are corrupted #60

Qfl3x opened this issue Feb 8, 2023 · 9 comments

Comments

@Qfl3x
Copy link

Qfl3x commented Feb 8, 2023

When setting up a new server, I get the following error:

[Trace  - 10:48:02.865] Server install command stdout:
Error server contents are corrupted
bd2d2de3e07576ad4646d204: start
exitCode==1==
listeningOn====
connectionToken====
logFile==/root/undefined/.129500ee4c8ab7263461ffe327268ba56b9f210d.log==
osReleaseId==ubuntu==
arch==x86_64==
platform==Linux==
tmpDir==/run/user/0==
bd2d2de3e07576ad4646d204: end

When I open up the executable at /root/undefined/.../openvscode-server, it works fine (or at least appears to do so).

What's weird is that the logFile path doesn't exist, the path that does exist looks like: /root/undefined/129500ee4c8ab7263461ffe327268ba56b9f210d/<Extracted Tar ball>

Code-OSS info:

  • Version: 1.74.2

Host info:

Thanks!

@jeanp413
Copy link
Owner

jeanp413 commented Feb 8, 2023

Related #57 (comment)

I guess I can detect if the server is openvscode-server and rename it in the install script, but yeah switching to vscodium is easier, not sure how popular is Code-OSS but in any case let me know and I can push a commit with the change I mentioned.

Is it possible for you to switch to vscodium?

@Qfl3x
Copy link
Author

Qfl3x commented Feb 8, 2023

My OS (Solus) only ships Code-OSS.

@jeanp413
Copy link
Owner

@Qfl3x please update to 0.0.27, added a new setting remote.SSH.experimental.serverBinaryName, you need to set to the binary name in this case openvscode-server

@Qfl3x
Copy link
Author

Qfl3x commented Feb 11, 2023

@jeanp413 I got a new problem:

[Trace  - 11:11:25.770] Server install command stdout:
Server script already installed in /root/undefined/bin/129500ee4c8ab7263461ffe327268ba56b9f210d/bin/openvscode-server
Server script is already running /root/undefined/bin/129500ee4c8ab7263461ffe327268ba56b9f210d/bin/openvscode-server
Error server token file not found /root/undefined/.129500ee4c8ab7263461ffe327268ba56b9f210d.token
46f120fbfcd968b50e2d1e38: start
exitCode==1==
listeningOn====
connectionToken====
logFile==/root/undefined/.129500ee4c8ab7263461ffe327268ba56b9f210d.log==
osReleaseId==ubuntu==
arch==x86_64==
platform==Linux==
tmpDir==/run/user/0==
46f120fbfcd968b50e2d1e38: end

The logFile doesn't exist. undefined only has bin as a subfolder.

(For anyone else reading, you have to rm -rf the previous folder ('undefined' here) for this to work up to this point)

EDIT: I touched the token file to see what would happen and I got the same error for the log file. touched that as well and got a Server did not start successfully

EDIT2: I killed every openvscode instance in the Server, and now the real bug has showed up (It was printed, but I thought it's nothing): Error: Connection error: Client refused: version mismatch, the token and log errors will disappear if I forcefully kill all openvscode instances after the extension downloads and installs the server. First install always fails with the token bug, subsequent server connections won't as long as I kill the instances. Terminal not working, and can't install any extension.

@Qfl3x
Copy link
Author

Qfl3x commented Feb 11, 2023

New Update: Works fine after I edit the commit in product.json (After downloading and initial "install").

Steps to work:

  1. Do all the edits on the extension config (experimental and custom download link)
  2. Connect to the server -> It crashes with version mismatch/token file not found
  3. Kill all instances of openvscode-server on the server
  4. Edit the product.json file on the server (undefined/bin/<commit>/product.json): Make commit equal to the local Code-OSS commit
  5. Connect to the Host
  6. Works!

@jeanp413
Copy link
Owner

jeanp413 commented Feb 11, 2023

What's the version and commit of your code-oss installation? I thought openvscode-server had the same commit as code-oss 🤔

From your logs you are using using 1.72.1 as I see the commit 129500ee4c8ab7263461ffe327268ba56b9f210d so openvscode-server should be the same version, could you share the complete logs to be sure you are downloading the correct version

@Qfl3x
Copy link
Author

Qfl3x commented Feb 11, 2023

The commit id that was on product.json before I edited it started with 3. So definitely different. I'll post my logs tomorrow as I'm setting up the VM at the moment. When I started the server in a browser it was version 1.74.2

(My Version is 1.74.2 not 1.72.1)

@jeanp413
Copy link
Owner

(My Version is 1.74.2 not 1.72.1)

That's odd 🤔, the extension is detecting 129500ee4c8ab7263461ffe327268ba56b9f210d which does it by reading the product.json of your code-oss, and last time I checked they were using the same commit as upstream https://github.com/microsoft/vscode/releases/tag/1.72.1

If you say you have 1.74.2 then can you check the commit field in product.json of your code-oss, it should be e8a3071ea4344d9d48ef8a4df2c097372b0c5161 https://github.com/microsoft/vscode/releases/tag/1.74.2

If the above is not the case then there's not much I can do sadly, probably it'll be easier to change the commit value in your code-oss installation rather than openvscode-server so you'll only need to do it again if you update code-oss

@Qfl3x
Copy link
Author

Qfl3x commented Feb 11, 2023

It wasn't the correct commit. I edited. I think the package maintainer needs to be notified.

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

No branches or pull requests

2 participants