Error: Package: alt-php74-imunify-mbstring - Oniguruma

[SweptSquash]

Hi,

I went to perform a System Update and ran into the following error, I did a quick search on the forums and google but didn't come across anyone having a similar issue. Any assistance would be greatly appericated Thanks

“yum” reported error code “1” when it ended:  w/ yum -y --exclude=kernel-*
Loaded plugins: fastestmirror, universal-hooks, versionlock
Loading mirror speeds from cached hostfile
 * EA4: 91.197.228.252
 * cpanel-addons-production-feed: 91.197.228.252
 * cpanel-plugins: 91.197.228.252
 * base: mirror.cc.columbia.edu
 * epel: d2lzkl7pfhq30w.cloudfront.net
 * extras: mirror.rackspace.com
 * updates: mirrors.rit.edu
Excluding 1 update due to versionlock (use "yum versionlock status" to show it)
Resolving Dependencies
--> Running transaction check
---> Package oniguruma.x86_64 0:5.9.5-3.el7 will be updated
--> Processing Dependency: libonig.so.2()(64bit) for package: alt-php74-imunify-mbstring-7.4.4-3.1.el7.x86_64
---> Package oniguruma.x86_64 0:6.8.2-1.el7 will be an update
--> Finished Dependency Resolution
<span class='text-danger'>Error: Package: alt-php74-imunify-mbstring-7.4.4-3.1.el7.x86_64 (@imunify360)</span>
           Requires: libonig.so.2()(64bit)
           Removing: oniguruma-5.9.5-3.el7.x86_64 (@epel)
               libonig.so.2()(64bit)
           Updated By: oniguruma-6.8.2-1.el7.x86_64 (epel)
              ~libonig.so.5()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Often errors like this can be resolved by running `yum makecache`

 

[Nirjonadda]

Getting error from yum update. Please let me know that how can fix this issue?

[[email protected] ~]# yum update
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
 * EA4: 91.197.228.252
 * EA4-experimental: 91.197.228.252
 * cpanel-addons-production-feed: 91.197.228.252
 * cpanel-plugins: 91.197.228.252
 * base: centos.mirror.triple-it.nl
 * epel: mirrors.ukfast.co.uk
 * extras: mirror.hostnet.nl
 * remi-safe: mirrors.ukfast.co.uk
 * updates: mirror.mijn.host
Resolving Dependencies
--> Running transaction check
---> Package elasticsearch.x86_64 0:7.7.1-1 will be updated
---> Package elasticsearch.x86_64 0:7.8.0-1 will be an update
---> Package librsync.x86_64 0:2.3.0-1.el7 will be updated
---> Package librsync.x86_64 0:2.3.1-1.el7 will be an update
---> Package librsync-devel.x86_64 0:2.3.0-1.el7 will be updated
---> Package librsync-devel.x86_64 0:2.3.1-1.el7 will be an update
---> Package oniguruma.x86_64 0:5.9.5-3.el7 will be updated
--> Processing Dependency: libonig.so.2()(64bit) for package: alt-php74-imunify-mbstring-7.4.6-2.el7.x86_64
---> Package oniguruma.x86_64 0:6.8.2-1.el7 will be an update
--> Finished Dependency Resolution
Error: Package: alt-php74-imunify-mbstring-7.4.6-2.el7.x86_64 (@imunify360)
           Requires: libonig.so.2()(64bit)
           Removing: oniguruma-5.9.5-3.el7.x86_64 (@epel)
               libonig.so.2()(64bit)
           Updated By: oniguruma-6.8.2-1.el7.x86_64 (epel)
              ~libonig.so.5()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
[[email protected] ~]#

 

[lestat69]

System update process has started.

“yum” reported error code “1” when it ended: w/ yum -y
Loaded plugins: universal-hooks
Resolving Dependencies
--> Running transaction check
---> Package oniguruma.x86_64 0:5.9.5-3.el7 will be updated
--> Processing Dependency: libonig.so.2()(64bit) for package: alt-php74-imunify-mbstring-7.4.6-2.el7.x86_64
---> Package oniguruma.x86_64 0:6.8.2-1.el7 will be an update
--> Finished Dependency Resolution
<span class='text-danger'>Error: Package: alt-php74-imunify-mbstring-7.4.6-2.el7.x86_64 (@imunify360)</span>
Requires: libonig.so.2()(64bit)
Removing: oniguruma-5.9.5-3.el7.x86_64 (@epel)
libonig.so.2()(64bit)
Updated By: oniguruma-6.8.2-1.el7.x86_64 (epel)
~libonig.so.5()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Often errors like this can be resolved by running `yum makecache`

System update process has finished.

 

[nullmem]

I am having same problem.

Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
 * EA4: 70.87.220.252
 * cpanel-addons-production-feed: 70.87.220.252
 * cpanel-plugins: 70.87.220.252
 * base: mirrors.radwebhosting.com
 * epel: mirror.dal.nexril.net
 * extras: www.gtlib.gatech.edu
 * updates: repos.hou.layerhost.com
Resolving Dependencies
--> Running transaction check
---> Package oniguruma.x86_64 0:5.9.5-3.el7 will be updated
--> Processing Dependency: libonig.so.2()(64bit) for package: alt-php74-imunify-mbstring-7.4.4-3.1.el7.x86_64
---> Package oniguruma.x86_64 0:6.8.2-1.el7 will be an update
--> Finished Dependency Resolution
Error: Package: alt-php74-imunify-mbstring-7.4.4-3.1.el7.x86_64 (@imunify360)
           Requires: libonig.so.2()(64bit)
           Removing: oniguruma-5.9.5-3.el7.x86_64 (@epel)
               libonig.so.2()(64bit)
           Updated By: oniguruma-6.8.2-1.el7.x86_64 (epel)
              ~libonig.so.5()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

 

[lestat69]

Same problem here


System update process has started.

“yum” reported error code “1” when it ended: w/ yum -y
Loaded plugins: universal-hooks
Resolving Dependencies
--> Running transaction check
---> Package oniguruma.x86_64 0:5.9.5-3.el7 will be updated
--> Processing Dependency: libonig.so.2()(64bit) for package: alt-php74-imunify-mbstring-7.4.6-2.el7.x86_64
---> Package oniguruma.x86_64 0:6.8.2-1.el7 will be an update
--> Finished Dependency Resolution
<span class='text-danger'>Error: Package: alt-php74-imunify-mbstring-7.4.6-2.el7.x86_64 (@imunify360)</span>
Requires: libonig.so.2()(64bit)
Removing: oniguruma-5.9.5-3.el7.x86_64 (@epel)
libonig.so.2()(64bit)
Updated By: oniguruma-6.8.2-1.el7.x86_64 (epel)
~libonig.so.5()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Often errors like this can be resolved by running `yum makecache`

System update process has finished.

 

[nullmem]

Often errors like this can be resolved by running `yum makecache`

Was the first thing I tried. doesn't work.

 

[lestat69]

Was the first thing I tried. doesn't work.

Didn't work for me either!

 

[tesae]

Same issue here.
Excluding the package with --exclude=oniguruma seems to run but I don't know if anything will break.

ex: yum update --downloadonly --exclude=oniguruma

 

[JonathanJ]

Same issue, same attempt at resolution, same result.

Disabling epel let's me yum update, but if I re-enable epel, same problem, tracking down the package specifically, but we're getting a security update alert for it.

So it is oniguruma that is being reported by "yum --security check-update":

1 package(s) needed for security, out of 1 available

oniguruma.x86_64                                                                 6.8.2-1.el7                                                                 epel

And of course if you hide that update by disabling epel the packages needed for security disappears

 

[nullmem]

This didn't work

yum clean expire-cache; yum update

This also did not work

yum remove imunify-antivirus
rm -rf /etc/sysconfig/imunify360
rm /etc/yum.repos.d/imunify360*
curl https://repo.imunify360.cloudlinux.com/defence360/imav-deploy.sh | bash

Not sure why it's trying to install an alt-php package on a non Coudlinux machine, but these types of bugs from Cloudlinux/Imunify are pretty common. I think someone is drinking too much vodka when deploying package updates.

 

[cosmomedia]

The issue is with third party repo EPEL on CloudLinux:
oniguruma-6.8.2-1.el7.x86_64 (epel)

yum-config-manager --disable epel
yum clean all
yum makecache
yum reinstall oniguruma
yum update

Worked…

(oniguruma.x86_64 -- 5.9.5-3.el7 -- @cloudlinux-imunify360)

 

[cPanelLauren]

We discussed issues with oniguruma at length here as well: PHP 7.4 Issues/Updates

In this case, though, the unsupported 3rd party repository EPEL has a conflict with the packages provided by the supported CloudLinux EasyApache repository.

 

[BillyS]

I'm pretty sure if you elected to install Imunify, this will happen. I was sick of getting warnings in CSF concerning the php.ini file used by this program, so when I saw it broke the yum update for easyapache, I unistalled it using the information found here:

ImunifyAV for cPanel and DirectAdmin

::: tip Note This ImunifyAV documentation is applicable for cPanel and DirectAdmin control panels only. :::

docs.imunifyav.com

wget https://repo.imunify360.cloudlinux.com/defence360/imav-deploy.sh
bash imav-deploy.sh --uninstall

All problems solved.

 

[kdean]

edit /etc/yum.repos.d/epel.repo

Add in the [epel] section:

exclude=oniguruma*

Error no longer appears

Further if you want the current installed oniguruma to reflect that it's from the imunify360 repo instead of the epel repo, after adding the above you can do:

yum reinstall oniguruma

Then a "yum list oniguruma" will now show:

oniguruma.x86_64 5.9.5-3.el7 @imunify360

 

[nullmem]

In this case, though, the unsupported 3rd party repository EPEL has a conflict with the packages provided by the supported CloudLinux EasyApache repository.

So cPanel's official response is epel is unsupported. Why do I continue to give you so much money every month for such a useless response

 

[wbmichael]

The issue is with third party repo EPEL on CloudLinux:
oniguruma-6.8.2-1.el7.x86_64 (epel)

Epel doesn´t matter.... as long as you have imunify installed, updates do not work. I needed to remove imunify360 (or imunify-av) completely, then updating with
yum update -y
then remove oniguruma and reinstall imunify. (If you don´t remove oniguruma you can´t install imunify360)

Really annoying bug in cloudlinux/imunify repo.

 

[CloudLinux Skhristich]

Hello,
As workaround:
You can completely disable the epel repository or you can try adding the oniguruma package to the exceptions for EPEL. To exclude a package from EPEL repo, add the following line:

exclude=oniguruma

To the section [epel] in file /etc/yum.repos.d/epel.repo. It will look like:

[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch&infra=$infra&content=$contentdir
failovermethod=priority
enabled = 1
gpgcheck=1
exclude=oniguruma
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

With this fix, you will exclude the conflicting package from EPEL repo and can try to keep the repository turned on.
Thank you

 

[RufusLive]

My server provider switched to a different control panel because of the pricing, but I stayed with cPanel, and pay the extra money for the cPanel licence through here so I could get the support but the support ticket system is not working and there is no response for a solution on here.