The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Installer Failing on Clean AWS CentOS Server

Discussion in 'General Discussion' started by WillW, Nov 6, 2014.

  1. WillW

    WillW Registered

    Joined:
    Nov 6, 2014
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hi,
    By way of
    Code:
    wget -N http://httpupdate.cPanel.net/latest
    and
    sh latest
    I attempted the installation of cPanel with WHM. It failed. The last of the failure messages included:

    Code:
    [20141106.123146] file /usr/lib64/libmysqlclient_r.so.16.0.0 from install of compat-MySQL51-shared-5.1.73-4.cp1136.x86_64 conflicts with file from package Percona-Server-shared-compat-5.5.31-rel30.3.520.rhel6.x86_64
    [20141106.123146] file /usr/lib64/libmysqlclient.so.15.0.0 from install of compat-MySQL50-shared-5.0.96-4.cp1136.x86_64 conflicts with file from package Percona-Server-shared-compat-5.5.31-rel30.3.520.rhel6.x86_64
    [20141106.123146] file /usr/lib64/libmysqlclient_r.so.15.0.0 from install of compat-MySQL50-shared-5.0.96-4.cp1136.x86_64 conflicts with file from package Percona-Server-shared-compat-5.5.31-rel30.3.520.rhel6.x86_64
    [20141106.123146] file /usr/lib64/libmysqlclient.so.18.0.0 from install of MySQL55-shared-5.5.40-1.cp1136.x86_64 conflicts with file from package Percona-Server-shared-55-5.5.30-rel30.1.465.rhel6.x86_64
    [20141106.123146] file /usr/lib64/libmysqlclient_r.so.18 from install of MySQL55-shared-5.5.40-1.cp1136.x86_64 conflicts with file from package Percona-Server-shared-55-5.5.30-rel30.1.465.rhel6.x86_64
    [20141106.123146] file /usr/lib64/libmysqlclient_r.so.18.0.0 from install of MySQL55-shared-5.5.40-1.cp1136.x86_64 conflicts with file from package Percona-Server-shared-55-5.5.30-rel30.1.465.rhel6.x86_64
    [20141106.123146] see http://go.cpanel.net/rpmcheckfailed for more information
    [20141106.123146] The Administrator will be notified to review this output when this script completes
    [20141106.123146] E Detected events which require user notification during updatenow. Will send iContact the log
    info [updatenow] upcp Notification => root@ip-10-0-0-253 via EMAIL [level => 1]
    Cpanel::iContact: icontact /usr/sbin/sendmail is not executable by 0
    [20141106.123146] Removing staged files and directories for binaries/linux-c6-x86_64, cpanel
    [20141106.123147] Removing staged files and directories for x3
    [20141106.123148] Removing staged files and directories for x3mail
    Can't exec "/usr/local/cpanel/scripts/cpanel_initial_install": No such file or directory at /home/cPanelInstall/selfgz30181/install line 146.
    2014-11-06 12:31:48 148 (FATAL): Failure to exec /usr/local/cpanel/scripts/cpanel_initial_install
    Removing /root/installer.lock
    The first instance I tried this on, I had already installed MySQL, emacs and wget, along with SSH credentials for two users When it failed. I removed the installation of it and attempted the second installation by the above methods. It failed again. I terminated the instance and created a new one, installed emacs SSH credentials for two users and wget. It failed again. This is a trial installation.
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    675
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    It does not appear to be a fresh installation of CentOS if Percona is already installed on your system. You can find the software requirements for new installations of cPanel/WHM at:

    cPanel Installations - Software Requirements

    Thank you.
     
  3. WillW

    WillW Registered

    Joined:
    Nov 6, 2014
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Indeed, it was not. I had to switch the AMI that I was using. Hopefully I won't make too many of these mistakes.
     
Loading...

Share This Page