Closed renyhp closed 2 years ago
You could try running this command manually to see whether it is always able to actually start, or produces some extra useful output.
> Starting server with command... /afs/domain.tld/user/r/remoteuser/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/server.sh --start-server --host=127.0.0.1 --enable-remote-auto-shutdown --port=0 &> "/afs/domain.tld/user/r/remoteuser/.vscode-server/.83bd43bc519d15e50c4272c6cf5c1479df196a4d.log" < /dev/null
The command is extremely slow. After about 5 minutes, it gave this output:
*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*
Extension host agent listening on 35010
[10:36:27] Extension host agent started.
And that's when I started my client and it actually got connected.
Now, to be fair, this machine + filesystem has I/O speed that varies a lot (sometimes, even a command like ls
can require several seconds to execute).
I will make now a wild guess and say that vscode is using a timeout to tell whether the server started successfully, and this does require some I/O operations. If that's the case, is it possible to disable the timeout?
@roblourens
You could try running this command manually to see whether it is always able to actually start, or produces some extra useful output.
> Starting server with command... /afs/domain.tld/user/r/remoteuser/.vscode-server/bin/83bd43bc519d15e50c4272c6cf5c1479df196a4d/server.sh --start-server --host=127.0.0.1 --enable-remote-auto-shutdown --port=0 &> "/afs/domain.tld/user/r/remoteuser/.vscode-server/.83bd43bc519d15e50c4272c6cf5c1479df196a4d.log" < /dev/null
The equivalent of this from my logs keeps spinning endlessly when I try running it manually on the remote. The remote is not slow in any way I know of.
Now, to be fair, this machine + filesystem has I/O speed that varies a lot (sometimes, even a command like ls can require several seconds to execute).
Wow, I can imagine that causing serious issues in starting the server.
@munael that command will write output to a logfile, not produce stdout. Are you looking at the log file? Or what do you see if you start without the redirection to the file?
Now, to be fair, this machine + filesystem has I/O speed that varies a lot (sometimes, even a command like ls can require several seconds to execute).
Wow, I can imagine that causing serious issues in starting the server.
Is there anything that can be done to make it work? Even if it works slowly, I would be happy to just make it start and use VSCode as a remote text editor and terminal, rather than getting this error message.
Any news about this? It looks like it's flagged as needs-more-info, is there any more info I can provide?
@renyhp so when you are able to connect, it works well and is stable? Honestly I would assume that with what you said above, the connection would not be stable.
But if it works fine, maybe we can make the timeout configurable.
No, in fact it is not always very stable. But at least I have something to work with.
Given this
Now, to be fair, this machine + filesystem has I/O speed that varies a lot (sometimes, even a command like ls can require several seconds to execute).
and the server taking 5 minutes to start, I don't think there is much I can do to improve this situation, sorry.
Steps to Reproduce:
machine.domain.tld
Could not establish connection to "machine.domain.tld": The VS Code Server failed to start.
Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: --
This is annoying because it will happen totally randomly. Sometimes this will happen, sometimes it won't. I can click Retry or try to kill the VSCode server, but then it's random whether that will work or not. Sometimes it will need lots of attempts to get the connection working. The only thing that is guaranteed to work is to remove
~/.vscode-server
, which is very annoying to do because it will take ages to reinstall.Also, maybe worth mentioning, this are the logs when I try to kill the remote server:
Are they suggesting the
kill
command does not go through?