Skip to main content

Mysql wont startup, WHM updated to 11.44 but left Mysql at 5.1

Just-hosted
I had a message yesterday saying an update was blocked since MySQL version was not supported (5.1) this morning the message is gone and whm is on version 11.44. I installed BetterLinux yesterday everything was running great till this morning, all my sites WordPress dashboards are screwed up. I uninstalled Bl and mysql refused to start back up. Since then I've had a ton of trouble. I did try to upgrade to 5.5 which I thought was successful but since realize that only 5.1 is installed. I tried easy Apache update witch seems to be stuck in a loop now or something... If i go to Change MySQL User Password in whm I'm seeing "MySQL is not installed " and MySQL Upgrade says "WARNING: A running easyapache process was detected. Please wait for easyapache to finish before attempting to upgrade MySQL. If you are certain that the easyapache is no longer running, you may restart the MySQL upgrade by clicking the following button." but clicking that button does nothing I also tried: /usr/local/cpanel/scripts/check_cpanel_rpms --fix MySQL51 /usr/local/cpanel/scripts/check_cpanel_rpms --fix /usr/local/cpanel/scripts/check_cpanel_rpms --fix MySQL55 none of them do anything I got some help from the BL guys but since it seems like an issue with WHM I have headed over here, hoping to get this fixed. I hope my mess makes sense and someone can help. Kind Regards Alex

Comments

2 comments

Date Votes
  • Just-hosted
    Ok finally came right with this, Thanks to James @Betterlinux for the help he provided. I ran /scripts/update_local_rpm_versions --edit target_settings.MySQL55 installed then /scripts/check_cpanel_rpms --fix MySQL55 Finally re ran the easyapache build and everything came back online :) very glad I got this sorted out Alex
    0
  • cPanelMichael
    Hello :) It's difficult to know for sure why the initial upgrade to MySQL 5.5 failed without access to the affected system. Note that rather than attempting multiple resolutions for an issue like this, it's typically better to review the error logs and submit a support ticket if you are not sure how to proceed. That being said, I am happy to see the issue has been resolved. Thank you for updating us with the outcome.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post