search

microsoft / live-share

Real-time collaborative development from the comfort of your favorite tools
http://aka.ms/vsls
Creative Commons Attribution 4.0 International
2.27k stars 248 forks source link

[VS Code] RPC connection closed. #1022

Closed steekam closed 6 years ago

steekam commented 6 years ago

Error:

RPC connection closed.

Linux Distro

Fedora 28

Steps to Reproduce:

  1. Click the shortcut share button
Version Data
extensionName VSLS
extensionVersion 0.3.709
protocolVersion 2.2
applicationName VSCode
applicationVersion 1.27.2
platformName Linux
platformVersion 4.18.7-200.fc28.x86_64
steekam commented 6 years ago

20180923_063805_15376846855630_VSCode.log 20180923_063815_Agent.log 20180923_064054_15376848548930_VSCode.log 20180923_064055_Agent.log 20180923_083220_15376915409550_VSCode.log 20180923_083223_Agent.log 20180923_105314_15376999941540_VSCode.log 20180923_105314_Agent.log 20180923_105400_15377000400810_VSCode.log 20180923_105401_Agent.log 20180924_060339_15377690197660_VSCode.log 20180924_060344_Agent.log 20180924_085211_15377791312410_VSCode.log 20180924_085216_Agent.log 20180924_085237_15377791578350_VSCode.log 20180924_085238_Agent.log

These are the logs attached with the problem. Kindly would you assist.

I have looked at the other open issues and tried the common fixes like checking my libssl versions. I have removed any extra versions, still no fix.

steekam commented 6 years ago

Update on the issue

I added proxy server settings which one of the log files had highlighted but then the error changed to connect ECONNREFUSED /tmp/CoreFxPipe_62dc931e9982409d900ddbaa98647988

The logs for this error

20180923_063805_15376846855630_VSCode.log 20180923_063815_Agent.log 20180923_064054_15376848548930_VSCode.log 20180923_064055_Agent.log 20180923_083220_15376915409550_VSCode.log 20180923_083223_Agent.log 20180923_105314_15376999941540_VSCode.log 20180923_105314_Agent.log 20180923_105400_15377000400810_VSCode.log 20180923_105401_Agent.log 20180924_060339_15377690197660_VSCode.log 20180924_060344_Agent.log 20180924_085211_15377791312410_VSCode.log 20180924_085216_Agent.log 20180924_085237_15377791578350_VSCode.log 20180924_085238_Agent.log 20180924_125818_15377938982060_VSCode.log 20180924_125821_Agent.log 20180924_134008_Agent.log 20180924_134527_15377967279670_VSCode.log 20180924_134528_Agent.log 20180924_134646_15377968064070_VSCode.log 20180924_134646_Agent.log 20180924_135845_15377975257720_VSCode.log 20180924_135846_Agent.log 20180924_140745_Agent.log 20180924_141226_Agent.log 20180924_165012_15378078123300_VSCode.log 20180924_165015_Agent.log

daytonellwanger commented 6 years ago

Looking at your logs, they all contain the error message Cannot get required symbol TLSv1_1_method from libssl, so it looks like this is still a libssl issue. What version of libssl do you have installed?

daytonellwanger commented 6 years ago

@Priya91

steekam commented 6 years ago

@daytonellwanger I am using Fedora 28 linux distro, so the libssl package is referred to as openssl. When I check openssl installed: sudo dnf list installed | grep openssl Output: compat-openssl10.x86_64 1:1.0.2o-1.fc28 @anaconda openssl.x86_64 1:1.1.0i-1.fc28 @updates openssl-lib-compat.x86_64 1:1.0.0i-1.fc28 @System
openssl-libs.x86_64 1:1.1.0i-1.fc28 @updates openssl-pkcs11.x86_64 0.4.8-2.fc28 @updates rubygem-openssl.x86_64 2.1.0-93.fc28 @updates xmlsec1-openssl.x86_64 1.2.25-4.fc28 @updates

I think the extension for a libssl library instead and I have no idea on how to fix that.

daytonellwanger commented 6 years ago

Looking at our install script, for Fedora we do yum install openssl-libs, so these should be all you need. I suspect your other openssl packages are interfering. Is it possible for you to safely remove all of your opensll packages, then try yum install openssl-libs? Or do you have other applications that depend on these packages?

daytonellwanger commented 6 years ago

You can check out the notes for libssl problems here: https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/linux#details-on-required-libraries

steekam commented 6 years ago

@daytonellwanger Let me try a reinstall of the package and get back to you.

daytonellwanger commented 6 years ago

@steekam thanks. I'd be somewhat careful though since we've had other customers report that modifying their openssl installations crippled their machine.

steekam commented 6 years ago

@daytonellwanger The package manager has protected them deletion anyway, let me heed to the warning. I have noticed something in one of the log files: dpkg --list libssl1.0.? | grep "^ii" dpkg-query: no packages found matching libssl1.0.?

Why is it using dpkg to check for packages yet the default fedora package manager is yum/dnf ? But I am sure I have the required packages. Thoughts..

Chuxel commented 6 years ago

@daytonellwanger @steekam That is a check fired to detect a problem unique to Debian and some Ubuntu based distributions. If the dpkg command is not found the output is ignored - which is obviously the case for Fedora. Unlike the Debian issue which occurred fairly frequently, this is the first time we've heard of a Fedora issue, so there's no similar check in place.

Symptomatically, this looks like these .NET Core raised issues:

The first issue indicated a non-base version of compat-openssl was present on the system which caused this error. I am noticing that that particular library is coming from anaconda in your dnf list installed output rather than system or update, so that could be what is causing the issue for similar reasons.

You could try installing from system or update: dnf --enablerepo=updates install compat-openssl10.x86_64

As Dayton mentioned, be sure to check what else is getting modified when you are tweaking system libraries like these.

steekam commented 6 years ago

@daytonellwanger @steekam That is a check fired to detect a problem unique to Debian and some Ubuntu based distributions. If the dpkg command is not found the output is ignored - which is obviously the case for Fedora. Unlike the Debian issue which occurred fairly frequently, this is the first time we've heard of a Fedora issue, so there's no similar check in place.

Symptomatically, this looks like these .NET Core raised issues:

The first issue indicated a non-base version of compat-openssl was present on the system which caused this error. I am noticing that that particular library is coming from anaconda in your dnf list installed output rather than system or update, so that could be what is causing the issue for similar reasons.

You could try installing from system or update: dnf --enablerepo=updates install compat-openssl10.x86_64

As Dayton mentioned, be sure to check what else is getting modified when you are tweaking system libraries like these.

Based on the dotnet/core-setup/#4460 resolve on the libssl issue, I was able to fix mine. I reinstalled the compat-openssl from the official repo and removed the openssl-lib-compat I reinstalled the vs-liveshare extension and it worked.

Thank you very much. You can go ahead and mark this as solved. I would have never have spotted the issue.

daytonellwanger commented 6 years ago

Great! Glad to hear. Thanks @Chuxel !