Easyapache4 flag error
I give it an update and the problem is not solved, so I connect via ssh to try to fix the problem and type the following commands.
[root@servidor rpm-gpg]# yum clean all
119 files removed
[root@servidor rpm-gpg]# yum makecache
EA4 ( EasyApache 4 ) 1.4 MB/s | 3.5 MB 00:02
cPanel Addons Production Feed 17 kB/s | 10 kB 00:00
cPanel Plugins project 389 kB/s | 390 kB 00:01
MariaDB103 850 kB/s | 527 kB 00:00
AlmaLinux 8 - BaseOS 5.3 MB/s | 5.2 MB 00:00
AlmaLinux 8 - AppStream 11 MB/s | 12 MB 00:01
AlmaLinux 8 - Extras 45 kB/s | 20 kB 00:00
AlmaLinux 8 - PowerTools 4.6 MB/s | 3.1 MB 00:00
Imunify360 - Gradual Rollout Slot 5 238 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 236 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 7 239 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 8 238 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 1 234 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 2 236 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 3 229 B/s | 257 B 00:01
Imunify360 - Gradual Rollout Slot 4 219 B/s | 257 B 00:01
EL-8 - Imunify360 1.5 MB/s | 5.3 MB 00:03
Imunify360 ea-php Hardened repository for CentOS 8 - x86_64 1.2 MB/s | 2.6 MB 00:02
kernelcare 6.8 kB/s | 8.0 kB 00:01
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 1.8 kB/s | 659 B 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 1.6 MB/s | 1.7 kB 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 2.6 kB/s | 659 B 00:00
Error: Failed to download metadata for repo 'pgdg-common': repomd.xml GPG signature verification error: Bad GPG signature
Install the repository RPM: dnf install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-8-x86_64/pgdg-redhat-repo-latest.noarch.rpm
I already tried to add the key and this continues to work in the same way, any idea how I can solve this problem, thanks.
-
The PostgreSQL RPM repository updated its GPG security keys on the 3rd of January this year which may be the cause of your issues. According to https://yum.postgresql.org/news/pgdg-rpm-repo-gpg-key-update/ to fix this on a RockyLinux 8 machine, try running:
dnf --disablerepo=* -y install https://download.postgresql.org/pub/repos/yum/reporpms/EL-8-aarch64/pgdg-redhat-repo-latest.noarch.rpm
(which is very nearly what you had).
If you've tried that, please let us know!
0 -
I keep getting the same error, as a comment my operating system is Almalinux 8.
Imunify360 ea-php Hardened repository for CentOS 8 - x86_64 1.3 MB/s | 2.6 MB 00:02
kernelcare 7.3 kB/s | 8.0 kB 00:01
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 2.2 kB/s | 659 B 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 1.6 MB/s | 1.7 kB 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 2.7 kB/s | 659 B 00:00
Error: Failed to download metadata for repo 'pgdg-common': repomd.xml GPG signature verification error: Bad GPG signature
[root@servidor ~]#0 -
Hmm, I've just tried an install of PostgreSQL on my AlmaLinux 8.9 server (surprised I didn't already have it installed) and I couldn't see it using the pgdg-common repo: did you initially install PostgreSQL via the instructions on https://docs.cpanel.net/knowledge-base/sql/install-or-update-postgresql-on-your-cpanel-server/ (i.e. using /usr/local/cpanel/scripts/installpostgres ) or did you install it "manually"?
I'm going to assume you installed it manually and that:
yum list postgresql-server
returns (in the right side column) the repository "pgdg-common" instead of @appstream (as it is on my install).
Can you try
grep gpgkey /etc/yum.repos.d/pgdg-redhat-all.repo
You should get lines back saying:
file:///etc/pki/rpm-gpg/PGDG-RPM-GPG-KEY-AARCH64-RHEL
That confirms the repository is pointing at the correct GPG key. Now try:
md5sum /etc/pki/rpm-gpg/PGDG-RPM-GPG-KEY-AARCH64-RHEL
is the hash at the start 30100de7982a148ab49e2e7a7d710ad2 ? If not, you'll need to download the key from https://download.postgresql.org/pub/repos/yum/keys/ and manually overwrite that file
0 -
I don't have that key, Is there a way to have the cpanel officials, I honestly don't remember if it was me who installed them manually.
[root@servidor ~]# yum list postgresql-server
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 731 B/s | 659 B 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 1.6 MB/s | 1.7 kB 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86_64 756 B/s | 659 B 00:00
Error: Failed to download metadata for repo 'pgdg-common': repomd.xml GPG signature verification error: Bad GPG signature
[root@servidor ~]# grep gpgkey /etc/yum.repos.d/pgdg-redhat-all.repo
#gpgkey=https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG-13
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-PGDG0 -
Can you post the output of the following command?
cat /etc/redhat-release
0 -
root@servidor ~]# cat /etc/redhat-release
AlmaLinux release 8.9 (Midnight Oncilla)0 -
That's interesting - does this command show any output?
grep -Ri rocky /etc/yum.repos.d/
If so, you'll likely need to disable those repositories on your machine as you're using AlmaLinux and not RockyLinux.
0 -
I have obtained the following results, please help me deactivate those repositories and only keep the official cpanel ones, thank you.
[root@servidor ~]# grep -Ri rocky /etc/yum.repos.d/
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG Red Hat Enterprise Linux / Rocky / AlmaLinux repositories. #
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG Red Hat Enterprise Linux / Rocky stable common repository for all PostgreSQL versions
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL common RPMs for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL Supplementary ucommon RPMs for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=Extra packages to support some RPMs in the PostgreSQL RPM repo for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG Red Hat Enterprise Linux / Rocky stable repositories:
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 16 for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 15 for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 14 for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 13 for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG RHEL / Rocky Updates Testing common repositories.
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL common testing RPMs for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG RHEL / Rocky Updates Testing repositories. (These packages should not be used in production)
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 17 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 16 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 15 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 14 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 13 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG Red Hat Enterprise Linux / Rocky SRPM testing common repository
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:# PGDG RHEL / Rocky testing common SRPM repository for all PostgreSQL versions
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL common testing SRPMs for RHEL / Rocky / AlmaLinux $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 17 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 16 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 16 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 15 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 15 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 14 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 14 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 13 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 13 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source updates testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Source update testing
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 16 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 15 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 14 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 13 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 17 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 16 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 14 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 13 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo.rpmnew:name=PostgreSQL 12 for RHEL / Rocky / AlmaLinux $releasever - $basearch - Debuginfo
/etc/yum.repos.d/pgdg-redhat-all.repo:# PGDG Red Hat Enterprise Linux / Rocky repositories #
/etc/yum.repos.d/pgdg-redhat-all.repo:# PGDG Red Hat Enterprise Linux / Rocky stable common repository for all PostgreSQL versions
/etc/yum.repos.d/pgdg-redhat-all.repo:name=PostgreSQL common RPMs for RHEL / Rocky $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo:name=PostgreSQL Supplementary ucommon RPMs for RHEL / Rocky $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo:name=Extra packages to support some RPMs in the PostgreSQL RPM repo RHEL / Rocky $releasever - $basearch
/etc/yum.repos.d/pgdg-redhat-all.repo:# PGDG Red Hat Enterprise Linux / Rocky stable repositories:0 -
So the good news is that it looks like it's just that one repository. Do you know if you are using PostGreSQL on your machine? I would recommend doing the following:
-confirm you are not using PostGreSQL on your system
-uninstall PostGreSQL
-disable the repo with the following details: https://support.cpanel.net/hc/en-us/articles/360054840794-How-do-I-enable-or-disable-a-repositoryIf you need to reinstall PostGreSQL you can run /usr/local/cpanel/scripts/installpostgres to install the cPanel-supported version.
0 -
If PostGreSQL is currently being used in two domains, any recommendations? What to do in these cases, thank you.
0 -
What is the output of this?
psql -V
0 -
root@servidor ~]# psql -V
psql: /lib64/libpq.so.5: no version information available (required by psql)
psql (PostgreSQL) 9.6.22
[root@servidor ~]#0 -
Thanks for the information. I have confirmed that removing the software does not touch any of the data inside /var/lib/pgsql. However, you should have a backup of your data before making any changes to the server.
I would remove the *non-cpanel* PostGreSQL packages from the machine. You can find those by running this command:
rpm -qa | grep -i postgres
and then use the following command to remove those packages. This is one example, although yours will be named slightly differently:
yum remove postgresql-server
yum remove postgresql-9.6.22-1.module_el8.4.0+2479+beebcf7e.x86_64*Do not* remove the cpanel-postgresql packages from the machine.
After that is done, you can disable the repository using the details here:
https://support.cpanel.net/hc/en-us/articles/360054840794-How-do-I-enable-or-disable-a-repository
and then install the supported version of PostGreSQL with this command:
/scripts/installpostgres
At this point I would expect the server to have the proper version of PostGreSQL installed and future Yum updates to work properly on the system.
0 -
Hello, first of all, thank you very much for helping me with this case that I could not solve. Today, after some time, I am back after recovering from an illness. I did everything you told me to do and when I try to install Postgres, I receive the following error.
[root@servidor ~]# /scripts/installpostgres
This script installs PostgreSQL 9.2.x or later.
If your system runs an older version of PostgreSQL, you must
dump your databases to a file, and then restore them after
installation.
PostgreSQL 9.2.x is NOT backwards compatible.
If no PostgreSQL databases exist on your system, run the
following command to force the creation of a PostgreSQL 9.2.x -style
setup:
mv /var/lib/pgsql /var/lib/pgsql.old
systemctl restart postgresql
Do not run this command if databases exist that you wish to keep!
Are you certain that you wish to proceed? [y/(n)]:y
info [installpostgres] Installing Postgres...
PostgreSQL common RPMs for RHEL / Rocky 8 - x86 568 B/s | 659 B 00:01
PostgreSQL common RPMs for RHEL / Rocky 8 - x86 600 kB/s | 1.7 kB 00:00
PostgreSQL common RPMs for RHEL / Rocky 8 - x86 695 B/s | 659 B 00:00
Error: Failed to download metadata for repo 'pgdg-common': repomd.xml GPG signature verification error: Bad GPG signature
(XID a3egj5) “/usr/bin/yum” informó el código de error “1” cuando finalizó:
“/usr/bin/yum” reported error code “1” when it ended:
info [installpostgres] Updating postgresql configuration now...
Failed to locate postgresql CLI application
info [installpostgres] Attempting to restart postgresql...
The PostgreSQL installation failed!0 -
I'm sorry to hear about the illness and I hope you're feeling better now!
It looks like there are still repositories on the system that shouldn't be there. Can you remove or disable the "pgdg-common" repository and then see if you still have the same error?
Here are the repositories I see on a fresh cPanel install on RockyLinux 8:
-rw-r--r-- 1 root root 257 Jul 29 17:03 cPAddons.repo
-rw------- 1 root root 241 Aug 12 14:03 cpanel-plugins.repo
-rw-r--r-- 1 root root 232 May 4 2023 EA4.repo
-rw-r--r-- 1 root root 1680 Jun 27 19:06 epel-modular.repo
-rw-r--r-- 1 root root 1332 Jun 27 19:06 epel.repo
-rw-r--r-- 1 root root 1779 Jun 27 19:06 epel-testing-modular.repo
-rw-r--r-- 1 root root 1431 Jun 27 19:06 epel-testing.repo
-rw-r--r-- 1 root root 238 Jul 29 17:04 imunify360.repo
-rw-r--r-- 1 root root 254 Jul 29 17:04 imunify360-testing.repo
-rw-r--r-- 1 root root 2168 Jun 24 07:03 imunify-new-rollout.repo
-rw-r--r-- 1 root root 2170 Jun 24 07:03 imunify-rollout.repo
-rw-r--r-- 1 root root 2325 Oct 24 2023 mysql-community-debuginfo.repo
-rw-r--r-- 1 root root 2402 Oct 24 2023 mysql-community.repo
-rw-r--r-- 1 root root 2492 Oct 24 2023 mysql-community-source.repo
-rw-r--r--. 1 root root 710 Jun 7 13:40 Rocky-AppStream.repo
-rw-r--r--. 1 root root 695 Jun 7 13:40 Rocky-BaseOS.repo
-rw-r--r--. 1 root root 1773 Jun 7 13:40 Rocky-Debuginfo.repo
-rw-r--r--. 1 root root 360 Jun 7 13:40 Rocky-Devel.repo
-rw-r--r--. 1 root root 695 Jun 7 13:40 Rocky-Extras.repo
-rw-r--r--. 1 root root 731 Jun 7 13:40 Rocky-HighAvailability.repo
-rw-r--r--. 1 root root 680 Jun 7 13:40 Rocky-Media.repo
-rw-r--r--. 1 root root 680 Jun 7 13:40 Rocky-NFV.repo
-rw-r--r--. 1 root root 690 Jun 7 13:40 Rocky-Plus.repo
-rw-r--r--. 1 root root 715 Jul 29 16:59 Rocky-PowerTools.repo
-rw-r--r--. 1 root root 746 Jun 7 13:40 Rocky-ResilientStorage.repo
-rw-r--r--. 1 root root 681 Jun 7 13:40 Rocky-RT.repo
-rw-r--r--. 1 root root 2335 Jun 7 13:40 Rocky-Sources.repo
-rw-r--r-- 1 root root 304 Jul 29 17:04 wp-toolkit-cpanel.repo0 -
Ok, I have disabled "pgdg-common" but when I run the script again it presents a new error, my question is if I skip it could it cause a bigger problem? Thank you very much for the help.
[root@servidor ~]# /scripts/installpostgres
This script installs PostgreSQL 9.2.x or later.
If your system runs an older version of PostgreSQL, you must
dump your databases to a file, and then restore them after
installation.
PostgreSQL 9.2.x is NOT backwards compatible.
If no PostgreSQL databases exist on your system, run the
following command to force the creation of a PostgreSQL 9.2.x -style
setup:
mv /var/lib/pgsql /var/lib/pgsql.old
systemctl restart postgresql
Do not run this command if databases exist that you wish to keep!
Are you certain that you wish to proceed? [y/(n)]:y
info [installpostgres] Installing Postgres...
Last metadata expiration check: 0:02:01 ago on Mon Aug 12 08:51:35 2024.
Package libpq5-16.0-42PGDG.rhel8.x86_64 is already installed.
Error:
Problem: package libpq-devel-13.11-1.el8.alma.1.x86_64 from appstream requires libpq(x86-64) = 13.11-1.el8.alma.1, but none of the providers can be installed
- installed package libpq5-16.0-42PGDG.rhel8.x86_64 obsoletes libpq provided by libpq-13.11-1.el8.alma.1.x86_64 from appstream
- cannot install the best candidate for the job
- problem with installed package libpq5-16.0-42PGDG.rhel8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
(XID v5ct2d) “/usr/bin/yum” informó el código de error “1” cuando finalizó:
“/usr/bin/yum” reported error code “1” when it ended:
info [installpostgres] Updating postgresql configuration now...
Failed to locate postgresql CLI application
info [installpostgres] Attempting to restart postgresql...
The PostgreSQL installation failed!0 -
Can you remove that package from the server and try the install again?
0 -
If you allow me to remove it, I only see that it is affecting several applications, especially JetApps. That application is for making backups.
At night I will try to remove it after the scheduled backup is done.[root@servidor ~]# sudo yum remove libpq5-16.0-42PGDG.rhel8.x86_64
Dependencies resolved.
============================================================================================================================================================
Package Architecture Version Repository Size
============================================================================================================================================================
Removing:
libpq5 x86_64 16.0-42PGDG.rhel8 @pgdg-common 1.0 M
Removing dependent packages:
ea-php74-php-pgsql x86_64 1:7.4.33-6.el8.cloudlinux.1 @imunify360-ea-php-hardened 194 k
ea-php80-php-pgsql x86_64 1:8.0.30-1.el8.cloudlinux @imunify360-ea-php-hardened 250 k
ea-php81-php-pgsql x86_64 1:8.1.25-1.el8.cloudlinux @imunify360-ea-php-hardened 258 k
ea-php82-php-pgsql x86_64 1:8.2.12-1.el8.cloudlinux @imunify360-ea-php-hardened 258 k
jetbackup5-cpanel x86_64 5.2.11-2 @jetapps-stable 378 k
wp-toolkit-cpanel x86_64 6.2.11-7710 @wp-toolkit-cpanel 124 M
Removing unused dependencies:
ea-php74-libc-client x86_64 1:2007f-28.el8.cloudlinux @imunify360-ea-php-hardened 1.7 M
jetbackup5-base x86_64 5.2.11-2 @jetapps-stable 24 M
jetguzzle-php x86_64 6.3.3.3-2 @jetapps 429 k
jetindex x86_64 1.1.1-1 @jetapps-stable 5.3 M
jetmongod x86_64 4.4.0.1-7 @jetapps 179 M
jetphp73 x86_64 7.3.26.4-3 @jetapps 10 M
jetphp73-curl x86_64 7.3.26.4-3 @jetapps 536 k
jetphp73-fileinfo x86_64 7.3.26.4-3 @jetapps 5.9 M
jetphp73-ftp x86_64 7.3.26.4-3 @jetapps 257 k
jetphp73-hash x86_64 7.3.26.4-3 @jetapps 1.1 M
jetphp73-inotify x86_64 7.3.26.4-3 @jetapps 64 k
jetphp73-ioncube x86_64 7.3.26.4-3 @jetapps 1.3 M
jetphp73-jetentities x86_64 7.3.26.1-10 @jetapps-stable 109 k
jetphp73-jetindex x86_64 7.3.26.14-1 @jetapps-stable 1.0 M
jetphp73-json x86_64 7.3.26.4-3 @jetapps 330 k
jetphp73-mbstring x86_64 7.3.26.4-3 @jetapps 2.2 M
jetphp73-mongodb x86_64 7.3.26.4-3 @jetapps 7.4 M
jetphp73-mysqli x86_64 7.3.26.4-3 @jetapps 916 k
jetphp73-mysqlnd x86_64 7.3.26.4-3 @jetapps 1.8 M
jetphp73-openssl x86_64 7.3.26.4-3 @jetapps 693 k
jetphp73-pcntl x86_64 7.3.26.4-3 @jetapps 132 k
jetphp73-pgsql x86_64 7.3.26.4-3 @jetapps 683 k
jetphp73-posix x86_64 7.3.26.4-3 @jetapps 184 k
jetphp73-psr x86_64 7.3.26.4-3 @jetapps 417 k
jetphp73-session x86_64 7.3.26.4-3 @jetapps 560 k
jetphp73-simplexml x86_64 7.3.26.4-3 @jetapps 321 k
jetphp73-sockets x86_64 7.3.26.4-3 @jetapps 488 k
jetphp73-yaml x86_64 7.3.26.4-3 @jetapps 316 k
jetphp73-zip x86_64 7.3.26.4-3 @jetapps 1.0 M
jetphp73-zlib x86_64 7.3.26.4-3 @jetapps 251 k
jetrsync x86_64 3.2.7.0-101 @jetapps 580 k
libaps x86_64 1.0.10-1centos.8.220111.1225 @wp-toolkit-thirdparties 4.7 M
libc-client x86_64 2007f-24.el8 @epel 1.5 M
plesk-libboost-1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 1.3 k
plesk-libboost-date-time1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 6.0 k
plesk-libboost-filesystem1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 127 k
plesk-libboost-program-options1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 372 k
plesk-libboost-regex1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 937 k
plesk-libboost-serialization1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 280 k
plesk-libboost-system1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 6.0 k
plesk-libboost-thread1.74 x86_64 1.74.0.1-1centos.8.211202.1439 @wp-toolkit-thirdparties 135 k
plesk-libpoco-1.9.0 x86_64 1.9.0-1centos.8.220117.1118 @wp-toolkit-thirdparties 5.1 M
plesk-lmlib x86_64 0.2.5-1centos.8.220111.1225 @wp-toolkit-thirdparties 1.7 M
plesk-platform-runtime x86_64 1.0.2-1centos.8.220111.1225 @wp-toolkit-thirdparties 55 k
plesk-rdbmspp x86_64 2.0.2-1centos.8.220111.1225 @wp-toolkit-thirdparties 710 k
sw-engine x86_64 3.41.1-1centos.8.220111.1225 @wp-toolkit-thirdparties 41 M
xmlrpc-c x86_64 1.51.0-8.el8 @baseos 593 kTransaction Summary
============================================================================================================================================================
Remove 54 Packages0 -
Can you submit a ticket so this can be investigated directly on the system?
0
Please sign in to leave a comment.
Comments
19 comments