rserver-launcher error when choosing R 4.0.2 session

Rstudio server Pro installed on RHEL7
I have 3 parallel R installs: MRO 3.5.3, R 3.6.2, and R 4.0.2 latest
I'm using the /etc/rstudio/r-versions file to define versions available in the IDE

In short, I just installed R 4.0.2 (built from source as ./configure --prefix=/usr/lib64/R/4.0.2 --enable-R-shlib) and verified I can launch an R 4.0.2 session from a bash shell. After adding an entry to r-versions and restarting the server, I visit the server login page and launch a session which still works fine under the default (3.5.3) install. When I attempt to switch the R version over to 4.0.2 I get some reticulating splines followed by a "RStudio Initialization Error" popup informing "Error occurred during transmission."

When I check rstudio-server status i see the following message:

ERROR rserver-launcher: /usr/lib/rstudio-server/bin/rsession: /usr/lib64/anaconda3/lib/libuuid.so.1: no version information available (required by /usr/lib/rstudio-server/bin/rsession)|||; LOGGED FROM: void rstudio::server::ProcessMonitor::onProcessStderr(rstudio::server::ProcessMonitor::Process, const string&) /var/lib/jenkins/workspace/IDE/pro-pipeline/v1.2-patch/src/cpp/server/ServerProcessMonitor.cpp:209

Could use help on solving this - suspect something to do with my $PATH?

Hi @barr.michaelj,

One thing to suggest here -- we have precompiled R binaries -- available to the public: https://docs.rstudio.com/resources/install-r/. We've found these can really help to make parallel installs of R easier on the pro products. I think the first thing I'd try, just to make your life easier, would be to download and install the 4.0.2 R binary.

One other question -- are you using anaconda on the system for managing R dependencies? It looks like the R session starting is getting diverted into anaconda.

Thank you for the tip. I removed the previous install and installed from the precompiled binary. I updated r-versions to point to the /opt/R/4.0.2 path of new install.

This is from /var/lib/rstudio-server/monitor/log/rstudio-server.log

30 Jul 2020 06:23:27 [rserver] ERROR rserver-launcher: /usr/lib/rstudio-server/bin/rsession: /usr/lib64/anaconda3/lib/libuuid.so.1: no version information available (required by /usr/lib/rstudio-server/bin/rsession)|||; LOGGED FROM: void rstudio::server::ProcessMonitor::onProcessStderr(rstudio::server::ProcessMonitor::Process, const string&) /var/lib/jenkins/workspace/IDE/pro-pipeline/v1.2-patch/src/cpp/server/ServerProcessMonitor.cpp:209

(base) [root@hsbeu1-u00001 etc]# rstudio-server verify-installation
Checking Job Launcher configuration...
Job Launcher integration not configured
/usr/lib/rstudio-server/bin/rsession: /usr/lib64/anaconda3/lib/libuuid.so.1: no version information available (required by /usr/lib/rstudio-server/bin/rsession)

I am not using anaconda for managing R. Only for a python distr. Let me see how I can fix the $PATH..

(base) [root@hsbeu1-u00001 etc]# locate libuuid.so.1
/root/anaconda3/lib/libuuid.so.1
/root/anaconda3/lib/libuuid.so.1.0.0
/root/anaconda3/pkgs/libuuid-1.0.3-h1bed415_2/lib/libuuid.so.1
/root/anaconda3/pkgs/libuuid-1.0.3-h1bed415_2/lib/libuuid.so.1.0.0
/usr/bin/anaconda3/lib/libuuid.so.1
/usr/bin/anaconda3/lib/libuuid.so.1.0.0
/usr/bin/anaconda3/pkgs/libuuid-1.0.3-h1bed415_2/lib/libuuid.so.1
/usr/bin/anaconda3/pkgs/libuuid-1.0.3-h1bed415_2/lib/libuuid.so.1.0.0
/usr/lib64/libuuid.so.1
/usr/lib64/libuuid.so.1.3.0
/usr/lib64/anaconda3/lib/libuuid.so.1
/usr/lib64/anaconda3/lib/libuuid.so.1.0.0
/usr/lib64/anaconda3/pkgs/libuuid-1.0.3-h1bed415_2/lib/libuuid.so.1
/usr/lib64/anaconda3/pkgs/libuuid-1.0.3-h1bed415_2/lib/libuuid.so.1.0.0

(base) [root@hsbeu1-u00001 etc]# ldd /usr/lib/rstudio-server/bin/rsession
linux-vdso.so.1 => (0x00007ffefcde3000)
libdl.so.2 => /usr/lib64/libdl.so.2 (0x00007f06bad70000)
libR.so => not found
libpthread.so.0 => /usr/lib64/libpthread.so.0 (0x00007f06bab54000)
libutil.so.1 => /usr/lib64/libutil.so.1 (0x00007f06ba951000)
libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f06ba74c000)
librt.so.1 => /usr/lib64/librt.so.1 (0x00007f06ba544000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00007f06ba32e000)
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f06ba0bc000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007f06b9c59000)
libpam.so.0 => /usr/lib64/libpam.so.0 (0x00007f06b9a4a000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f06b97fa000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f06b95f8000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f06b92e2000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f06b8fdb000)
libm.so.6 => /usr/lib64/libm.so.6 (0x00007f06b8cd9000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f06b8ac3000)
libc.so.6 => /usr/lib64/libc.so.6 (0x00007f06b86f5000)
/lib64/ld-linux-x86-64.so.2 (0x00007f06bc0cc000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007f06b84a8000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007f06b81bf000)
libcom_err.so.2 => /usr/lib64/libcom_err.so.2 (0x00007f06b7fbb000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007f06b7d88000)
libaudit.so.1 => /usr/lib64/libaudit.so.1 (0x00007f06b7b5f000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f06b78fd000)
libffi.so.6 => /usr/lib64/libffi.so.6 (0x00007f06b76f5000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f06b74e5000)
libkeyutils.so.1 => /usr/lib64/libkeyutils.so.1 (0x00007f06b72e1000)
libresolv.so.2 => /usr/lib64/libresolv.so.2 (0x00007f06b70c7000)
libcap-ng.so.0 => /usr/lib64/libcap-ng.so.0 (0x00007f06b6ec1000)
libselinux.so.1 => /usr/lib64/libselinux.so.1 (0x00007f06b6c9a000)

Hi @barr.michaelj,

Have you filed a support ticket on this issue? Since you're using RStudio Server Pro, you have access to our premium support and they can provide in-depth help.

Please come back and share the solution when you've got one for everyone's benefit!