vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Remote tunnel - "warn error access singleton, retrying: the process holding the singleton lock file"

Open j-silv-ti opened this issue 1 year ago • 3 comments

I ran into the same issue that was referenced here.

warn error access singleton, retrying: the process holding the singleton lock file (pid=PID_NUM) exited

Originally posted by @kissdan1 in https://github.com/microsoft/vscode-remote-release/issues/8973#issuecomment-1743712610

My fix was to delete the .vscode and .vscode-server folders.

rm -rf ~/.vscode ~/.vscode-server

Sorry if I shouldn't of created a new issue. Since the previous one was locked I couldn't comment on it.

j-silv-ti avatar Apr 22 '24 17:04 j-silv-ti

Does the tunnel start after you see that log message, or is it stuck in that state / in a loop?

connor4312 avatar Apr 24 '24 22:04 connor4312

Does the tunnel start after you see that log message, or is it stuck in that state / in a loop?

Stuck in that state, in a loop. That message keeps repeating over and over again.

j-silv-ti avatar Apr 24 '24 22:04 j-silv-ti

I ran into the same issue that was referenced here.

warn error access singleton, retrying: the process holding the singleton lock file (pid=PID_NUM) exited

Originally posted by @kissdan1 in #8973 (comment)

My fix was to delete the .vscode and .vscode-server folders.

rm -rf ~/.vscode ~/.vscode-server

Sorry if I shouldn't of created a new issue. Since the previous one was locked I couldn't comment on it.

note that you should back up your machine settings if deleting .vscode-server.

Not that I would forget to do that. No way.

jmorim avatar May 10 '24 00:05 jmorim

Actually, a much simpler solution is to delete the lock file that is located in the .vscode folder. This was mentioned in #2507.

rm ~/.vscode/cli/tunnel-stable.lock

j-silv-ti avatar May 28 '24 16:05 j-silv-ti