After updating to MySQL 5.6, check_cpanel_rpms is warning about altered 5.1 RPM content
I used the WHM panel to upgrade from MySQL 5.0 to 5.6 earlier this week. The site has been functioning fine. Last night I got an email from the cPanel for the site with contents:
Running check_cpanel_rpms on the server shows a little more information:
The --fix option on that script is a little scary is so much as there's not a lot of details about what "fixing" entails. Is it going to take down my database and do the upgrade again? Will it roll it back to 5.1? The --help output doesn't list a --dry-run option or equivalent that would let you understand what would happen without actually *doing* it. What can I expect from --fix here? Is there a way to repair this warning that won't require an outage from my database?
Problems were detected with cPanel-provided files which are RPM controlled.
If you did not make these changes intentionally, you can correct them by running:
> /usr/local/cpanel/scripts/check_cpanel_rpms --fix
The following RPMs are found to be altered from their original install state:
compat-MySQL51-shared,5.1.73,4.cp1136,/usr/lib64/libmysqlclient.so.16.0.0
Running check_cpanel_rpms on the server shows a little more information:
> /usr/local/cpanel/scripts/check_cpanel_rpms --list-only
prelink: /usr/lib64/libmysqlclient.so.16.0.0: at least one of file's dependencies has changed since prelinking
[20141025.211122]
[20141025.211122] Problems were detected with cPanel-provided files which are RPM controlled.
[20141025.211122] If you did not make these changes intentionally, you can correct them by running:
[20141025.211122]
[20141025.211122] > /usr/local/cpanel/scripts/check_cpanel_rpms --fix
[20141025.211122]
[20141025.211122] The following files were found to be altered from their original RPM:
[20141025.211122] compat-MySQL51-shared,5.1.73,4.cp1136
[20141025.211122]
The --fix option on that script is a little scary is so much as there's not a lot of details about what "fixing" entails. Is it going to take down my database and do the upgrade again? Will it roll it back to 5.1? The --help output doesn't list a --dry-run option or equivalent that would let you understand what would happen without actually *doing* it. What can I expect from --fix here? Is there a way to repair this warning that won't require an outage from my database?
Please sign in to leave a comment.
Comments
0 comments