Pccc

Registered
Jan 31, 2023
3
1
3
Virginia
cPanel Access Level
DataCenter Provider
Recently we received a warning about a php81 altered package on a cPanel server running CentOS 7.9.
The error is:

Packages​
Status​
Additional Information​
cpanel-php81,8.1.16,1.cp110~el7-/usr/local/cpanel/3rdparty/php/81/lib/php/.filemap BrokenS.5....T.

Running "/usr/local/cpanel/scripts/check_cpanel_pkgs --fix" fixes the issue but we have no idea why this happened and what are the information in "additional information" column.
Any idea about what happened ?
 
Last edited by a moderator:

clehnert

Registered
Dec 12, 2022
1
0
0
NJ
cPanel Access Level
Root Administrator
I see the same warning but when trying to run the `--fix` command I see:
`Unable to load files in directory: /var/cpanel/rpm.versions.d at /usr/local/cpanel/Cpanel/RPM/Versions/Directory.pm line 198.`
 

Huusoku

Active Member
Dec 24, 2008
32
0
131
Hello cPRex,

Server info: CentOS 7.9.2009, cPanel 110.0.3, logged in as Root.

Thank you for the support. We've had the same exact error as Pccc for about 2 wks now, and today I decided to address it.

When I run, "/usr/local/cpanel/scripts/check_cpanel_pkgs --fix" via command prompt (Windows 10/PuTTY), ....it does nothing? Carriage moves to a new blank line and nothing happens. So after a minute I used Ctrl+Z to stop the command, tried again, and let it sit for one hour and there is still no response, just a new blank line after the line of the command with nothing happening. Restarted PuTTY, logged back in as root, tried again, and still nothing, just a blank new line in PuTTY with what looks like no response from the server.

I then changed dir to /usr/local/cpanel/scripts/, and tried running, "check_cpanel_pkgs --fix" and I get, "-bash: check_cpanel_pkgs: command not found", but when I list files, "check_cpanel_pkgs" is listed as a file in this folder.

Any idea? Thanks!!
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
16,505
2,605
363
cPanel Access Level
Root Administrator
@clehnert - I'm not entirely sure why that would be happening. If you don't see anything else in the cPanel error logs when you run that command (/usr/local/cpanel/logs/error_log) I would recommend forcing a full server update with the "/scripts/upcp --force" command to see if that helps with the issue.

@Huusoku - getting the blank line is normal, but I wouldn't expect that it would sit there for that long. It might be best to create a ticket on that issue so we can take a look. Your behavior in the /scripts/ directory is normal as you need to call the full path to an executable since that directory isn't in any user's $PATH.