After RHEL patching one of the Applications refuses to execute

Hi there
Please can someone share some light on an issue
we did a round of RHEL patching last week and it seems that we have an error on one of our applications .

2022/02/22 09:38:30.896675854 Warning: Error in dyn.load: unable to load shared object '/opt/rstudio-connect/mnt/packrat/3.6.3/v2/library/V8/701fb45cca2b0ce3f0659ff7365ddd38/V8/libs/V8.so':
2022/02/22 09:38:30.896731015 libv8.so.3: cannot open shared object file: No such file or directory

RHEL version : Red Hat Enterprise Linux Server release 7.9 (Maipo)
R version :slight_smile: > version
_
platform x86_64-pc-linux-gnu
arch x86_64
os linux-gnu
system x86_64, linux-gnu
status
major 3
minor 6.3
year 2020
month 02
day 29
svn rev 77875
language R
version.string R version 3.6.3 (2020-02-29)
nickname Holding the Windsock

It seems that v8 is obsoleted by nodejs-libs which only provides /usr/lib64/libv8.so.9

You now have the following options

  • downgrade to the previous package (probably not an option)
  • rebuild the Connect cache (cf. Delete package from Connect's global cache - #2 by slopp and the wider issue there). Depending on the scale of your Connect installation this could take some time
  • you also could try a bit of a hack by symlinking libv8.so.9 to libv8.so.3 via
ln -s /usr/lib64/libv8.so.9 /usr/lib64/libv8.so.3
rm /etc/ld.so.cache 
ldconfig

This is possibly the quickest solution but it may lead to other errors (incompatibilities in API/ABI). The latter two commands are rebuilding the linker cache.

I would suggest to start with the symlink. If that works, fine. If not, remove the symlink via rm /usr/lib64/libv8.so.3 and rebuild the Connect package cache.