Forums

Resolved
0 votes
Hello,

During my latest update of one of my servers, I am having a dependency issue:

...
---> Package xorg-x11-server-common.x86_64 0:1.20.4-17.el7_9 will be an update
--> Running transaction check
---> Package brotli.x86_64 0:1.0.7-5.el7 will be installed
---> Package libuv.x86_64 1:1.43.0-2.el7 will be installed
---> Package openssl11-libs.x86_64 1:1.1.1k-2.el7 will be installed
---> Package v8.x86_64 1:3.14.5.10-25.el7 will be obsoleted
--> Processing Dependency: libv8.so.3()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-1062.18.1.el7 will be erased
---> Package v8.x86_64 1:3.14.5.10-25.el7 will be obsoleted
--> Processing Dependency: libv8.so.3()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
--> Finished Dependency Resolution
Error: Package: mongodb-server-2.6.12-6.el7.x86_64 (@clearos-epel)
Requires: libv8.so.3()(64bit)
Removing: 1:v8-3.14.5.10-25.el7.x86_64 (@clearos-epel)
libv8.so.3()(64bit)
Obsoleted By: 1:nodejs-libs-16.13.2-3.el7.x86_64 (clearos-epel)
~libv8.so.9()(64bit)


It appears that the package mongodb-server requires a library that is being removed/obsolete with the install of the package: nodejs-libs

I have had to exclude the nodejs-libs package to perform my update:
yum update --exclude=nodejs-libs
Sunday, February 20 2022, 08:38 PM
Share this post:

Accepted Answer

Tuesday, March 15 2022, 03:04 PM - #Permalink
Resolved
0 votes
I posted to the EPEL mailing list and got this reply:
MongoDB was retired from Fedora and epel7 a couple of years ago, due to the license issues.
Thus there is no longer a mongodb-server in epel7.
https://bugzilla.redhat.com/show_bug.cgi?id=1855725

Problem:
nodejs had a major update in epel7, and mongodb relies on the v8 in nodejs.
Why the major update?
v8 Security issues.
v8-3.14 (libv8.so.3) hasn't had any official security updates in 6 years.
v8 is the javascript engine for a browser, and as such, needs to be updated constantly because it touches so many things.
It was announced that it was being obsoleted by nodejs, but it was part of the nodejs announcement, so you might not have seen it. We apologize for this.
But in the end, it was no longer safe to be using the old nodejs and the old v8.

Solution:
At this point, we recommend you update your mongodb server from mongodb the company.
It is still free for a majority of use cases.
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-red-hat/

mongodb-server is probably still in our clearos-epel repo as we do not have a mechanism to clear out packages if they are removed from upstream.
The reply is currently minimized Show
Responses (3)
  • Accepted Answer

    Wednesday, March 16 2022, 02:06 AM - #Permalink
    Resolved
    0 votes
    Thanks Nick for inquiring.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, March 15 2022, 02:15 PM - #Permalink
    Resolved
    0 votes
    Hello Nick,

    Really really really nice to hear from you again. I hope all is well...

    I regards to your question: the server above is currently unavailable for me to do an update. Instead I ran a few cmds on a test vm. This is not an update but an install of mongodb-server showing similar issues with the same above 'nodejs-libs.x86_64' library. Note this time the library is not even installed ... that also can not be right?


    [root@services26 ~]# yum update

    ...

    kernel.x86_64 0:3.10.0-957.21.3.v7

    Installed:
    kernel.x86_64 0:3.10.0-1160.59.1.el7

    Updated:
    bind-export-libs.x86_64 32:9.11.4-26.P2.el7_9.9 bind-libs.x86_64 32:9.11.4-26.P2.el7_9.9
    bind-libs-lite.x86_64 32:9.11.4-26.P2.el7_9.9 bind-license.noarch 32:9.11.4-26.P2.el7_9.9
    bind-utils.x86_64 32:9.11.4-26.P2.el7_9.9 cyrus-sasl.x86_64 0:2.1.26-24.el7_9
    cyrus-sasl-lib.x86_64 0:2.1.26-24.el7_9 cyrus-sasl-plain.x86_64 0:2.1.26-24.el7_9
    docker-ce-cli.x86_64 1:20.10.13-3.el7 docker-scan-plugin.x86_64 0:0.17.0-3.el7
    kernel-headers.x86_64 0:3.10.0-1160.59.1.el7 kernel-tools.x86_64 0:3.10.0-1160.59.1.el7
    kernel-tools-libs.x86_64 0:3.10.0-1160.59.1.el7 mdadm.x86_64 0:4.1-9.el7_9
    polkit.x86_64 0:0.112-26.el7_9.1 python-perf.x86_64 0:3.10.0-1160.59.1.el7

    Complete!
    [root@services26 ~]#



    [root@services26 ~]# yum install mongodb-server
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Loading mirror speeds from cached hostfile
    * clearos: mirror2-newyork.clearos.com
    * clearos-centos: download3.clearsdn.com
    * clearos-centos-sclo-rh: download3.clearsdn.com
    * clearos-centos-updates: download3.clearsdn.com
    * clearos-contribs: mirror2-newyork.clearos.com
    * clearos-epel: download3.clearsdn.com
    * clearos-fast-updates: download3.clearsdn.com
    * clearos-infra: mirror2-newyork.clearos.com
    * clearos-paid: mirror2-newyork.clearos.com
    * clearos-updates: mirror2-newyork.clearos.com
    Resolving Dependencies
    --> Running transaction check
    ---> Package mongodb-server.x86_64 0:2.6.12-6.el7 will be installed
    --> Processing Dependency: v8 for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libyaml-cpp.so.0.5()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libv8.so.3()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    Package v8 is obsoleted by nodejs-libs, but obsoleting package does not provide for requirements
    --> Processing Dependency: libtcmalloc.so.4()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libstemmer.so.0()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libboost_thread-mt.so.1.53.0()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libboost_system-mt.so.1.53.0()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libboost_program_options-mt.so.1.53.0()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Processing Dependency: libboost_filesystem-mt.so.1.53.0()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Running transaction check
    ---> Package boost-filesystem.x86_64 0:1.53.0-28.el7 will be installed
    ---> Package boost-program-options.x86_64 0:1.53.0-28.el7 will be installed
    ---> Package boost-system.x86_64 0:1.53.0-28.el7 will be installed
    ---> Package boost-thread.x86_64 0:1.53.0-28.el7 will be installed
    ---> Package gperftools-libs.x86_64 0:2.6.1-1.el7 will be installed
    ---> Package libstemmer.x86_64 0:0-2.585svn.el7 will be installed
    ---> Package mongodb-server.x86_64 0:2.6.12-6.el7 will be installed
    --> Processing Dependency: libv8.so.3()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    Package v8 is obsoleted by nodejs-libs, but obsoleting package does not provide for requirements
    ---> Package nodejs-libs.x86_64 1:16.14.0-2.el7 will be installed
    --> Processing Dependency: libssl.so.1.1(OPENSSL_1_1_1)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libssl.so.1.1(OPENSSL_1_1_0)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libcrypto.so.1.1(OPENSSL_1_1_1e)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libcrypto.so.1.1(OPENSSL_1_1_1b)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libcrypto.so.1.1(OPENSSL_1_1_1)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libcrypto.so.1.1(OPENSSL_1_1_0g)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libcrypto.so.1.1(OPENSSL_1_1_0)(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libuv.so.1()(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libssl.so.1.1()(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libcrypto.so.1.1()(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libbrotlienc.so.1()(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    --> Processing Dependency: libbrotlidec.so.1()(64bit) for package: 1:nodejs-libs-16.14.0-2.el7.x86_64
    ---> Package yaml-cpp.x86_64 1:0.5.1-2.el7 will be installed
    --> Running transaction check
    ---> Package brotli.x86_64 0:1.0.7-5.el7 will be installed
    ---> Package libuv.x86_64 1:1.43.0-2.el7 will be installed
    ---> Package mongodb-server.x86_64 0:2.6.12-6.el7 will be installed
    --> Processing Dependency: libv8.so.3()(64bit) for package: mongodb-server-2.6.12-6.el7.x86_64
    Package v8 is obsoleted by nodejs-libs, but obsoleting package does not provide for requirements
    ---> Package openssl11-libs.x86_64 1:1.1.1k-2.el7 will be installed
    --> Finished Dependency Resolution
    Error: Package: mongodb-server-2.6.12-6.el7.x86_64 (clearos-epel)
    Requires: libv8.so.3()(64bit)
    Available: 1:v8-3.14.5.10-25.el7.x86_64 (clearos-epel)
    libv8.so.3()(64bit)
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va --nofiles --nodigest
    [root@services26 ~]#



    [root@services26 ~]# yum list nodejs-libs*
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Loading mirror speeds from cached hostfile
    * clearos: mirror2-newyork.clearos.com
    * clearos-centos: download3.clearsdn.com
    * clearos-centos-sclo-rh: download3.clearsdn.com
    * clearos-centos-updates: download3.clearsdn.com
    * clearos-contribs: mirror2-newyork.clearos.com
    * clearos-epel: download3.clearsdn.com
    * clearos-fast-updates: download3.clearsdn.com
    * clearos-infra: mirror2-newyork.clearos.com
    * clearos-paid: mirror2-newyork.clearos.com
    * clearos-updates: mirror2-newyork.clearos.com
    Available Packages
    nodejs-libs.x86_64 1:16.14.0-2.el7 clearos-epel
    [root@services26 ~]#
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, March 15 2022, 12:45 PM - #Permalink
    Resolved
    0 votes
    There was a major update to nodejs upstream with a risk of breakage. I've just pushed an update to Community which has a nodejs update. Please can you try updating again if you have ClearOS Community. If it does not fix it please post back and we may have to raise an issue with EPEL.
    The reply is currently minimized Show
Your Reply