• Server Admin Help — MySQL Installation/Removal Error + PHP Error

    Adelaid Member
    Quick Facts:
    Server: CentOS 6 64 bit
    PHP: 5.4.4
    MySQL: mysql-connector-odbc-5.1.5r1144-7.el6.x86_64
    mysql-libs-5.5.44-1.el6.remi.x86_64
    php-mysql-5.4.42-1.el6.remi.x86_64
    compat-mysql51-5.1.54-1.el6.remi.x86_64 
    

    I am in need of some assistance with my server. I attempted to install PHP 5.4.4 (upgrading from PHP 5.3) on my CentOS 6 64bit server, and it ended up corrupting the mysql.sock.

    Well, after looking up help for that, the most common solution was to uninstall and then reinstall MySQL.

    I did that.. or rather, I attempted to. I wound up uninstalling MySQL using

    yum remove mysql

    After that, I ran

    yum install mysql

    The first error I got was resolved, that being an incorrect epel for my server, and now I am presented with this when I run the above code:

    [root@u16585982 ~]# yum install mysql
    Loaded plugins: fastestmirror
    Setting up Install Process
    Determining fastest mirrors
    epel/metalink                                            |  11 kB     00:00
     * epel: mirror.steadfast.net
     * rpmforge: mirror.team-cymru.org
    base                                                     | 3.7 kB     00:00
    base/primary_db                                          | 4.6 MB     00:00
    epel                                                     | 4.4 kB     00:00
    epel/primary_db                                          | 6.6 MB     00:00
    extras                                                   | 3.4 kB     00:00
    extras/primary_db                                        |  31 kB     00:00
    rpmforge                                                 | 1.9 kB     00:00
    rpmforge/primary_db                                      | 2.7 MB     00:00
    updates                                                  | 3.4 kB     00:00
    updates/primary_db                                       | 3.9 MB     00:00
    Resolving Dependencies
    --> Running transaction check
    ---> Package mysql.x86_64 0:5.1.73-5.el6_6 will be installed
    --> Processing Dependency: mysql-libs = 5.1.73-5.el6_6 for package: mysql-5.1.73-5.el6_6.x86_64
    --> Running transaction check
    ---> Package mysql-libs.i686 0:5.1.73-5.el6_6 will be installed
    --> Finished Dependency Resolution
    Error:  Multilib version problems found. This often means that the root
           cause is something else and multilib version checking is just
           pointing out that there is a problem. Eg.:
    
             1. You have an upgrade for mysql-libs which is missing some
                dependency that another package requires. Yum is trying to
                solve this by installing an older version of mysql-libs of the
                different architecture. If you exclude the bad architecture
                yum will tell you what the root cause is (which package
                requires what). You can try redoing the upgrade with
                --exclude mysql-libs.otherarch ... this should give you an error
                message showing the root cause of the problem.
    
             2. You have multiple architectures of mysql-libs installed, but
                yum can only see an upgrade for one of those arcitectures.
                If you don't want/need both architectures anymore then you
                can remove the one with the missing update and everything
                will work.
    
             3. You have duplicate versions of mysql-libs installed already.
                You can use "yum check" to get yum show these errors.
    
           ...you can also use --setopt=protected_multilib=false to remove
           this checking, however this is almost never the correct thing to
           do as something else is very likely to go wrong (often causing
           much more problems).
    
           Protected multilib versions: mysql-libs-5.1.73-5.el6_6.i686 != mysql-libs-5.5.44-1.el6.remi.x86_64 
    

    After that, I looked up what I could do to make this work, it said remove one, so I tried. The result was this:

    [root@u16585982 ~]# yum remove mysql-libs-5.1.73-5.e16_6.i686
    Loaded plugins: fastestmirror
    Setting up Remove Process
    No Match for argument: mysql-libs-5.1.73-5.e16_6.i686
    Loading mirror speeds from cached hostfile
     * epel: mirror.steadfast.net
     * rpmforge: mirror.team-cymru.org
    No Packages marked for removal
    

    When I run

    rpm -qa | grep mysql

    The result is:

    mysql-connector-odbc-5.1.5r1144-7.el6.x86_64
    mysql-libs-5.5.44-1.el6.remi.x86_64
    php-mysql-5.4.42-1.el6.remi.x86_64
    compat-mysql51-5.1.54-1.el6.remi.x86_64 
  • WinMan Member
    Protected multilib versions: mysql-libs-5.1.73-5.el6_6.i686 != mysql-libs-5.5.44-1.el6.remi.x86_64

    You have a typo – you’ve got e16 instead of el6:

    [root@u16585982 ~]# yum remove mysql-libs-5.1.73-5.e16_6.i686

    I’m more familiar with pacman and apt. I hope that it’s only the typo

    Also, does rpm -qa return the version installed on your machine, or the remote version? Maybe it’s a conflict between a 32bit and 64bit version? It would make sense that the 64bit version of mysql would rather want to include its x86_64 libs than the i686 libs.

  • Gallard Member

    This can have two solutions:
    1)They messed the package tree and in some days it will be fixed
    2)You are building a 64bit version on a 32bit library.

    The 1) auto resolves, for the 2) you have to deep reinstall mysql. You have to install it together with all its dependencies choosing the correct architecture and eliminating all the duplicated architecture files. The last part is what you were doing.

  • WinMan Member

    I wound up reimaging this whole server and thankfully my scrambled attempt at gathering my mysql databases was successful in helping me restore all of my sites.

    I was able to get further in getting this MySQL thing thanks to you guys. Unfortunately it couldn’t go much further, when I uninstalled the MySQL, I noticed that it uninstalled a good deal of my Plesk stuff as well.

    Thank you both though for your assistance. I wound up upgrading (great for me really) to CentOS 7 64bit (plesk 12). Now I can have my PHP 5.4.4 and eat it too ;D

    Also it turns out that CentOS 6 just was not meant for PHP 5.4.x to run on it for some sad reason (tried on a fresh image and still no dice with it).

    Things to know before ruining your server amirite?

Viewing 3 reply threads
  • You must be logged in to reply to this topic.
en_USEnglish