Results 1 to 5 of 5

Thread: Clean install DirectAdmin and MySQL 5.7 issues...

  1. #1
    Join Date
    Jul 2015
    Posts
    18

    Question Clean install DirectAdmin and MySQL 5.7 issues...

    Hi all,

    Well I tried to setup a new server today with DirectAdmin PHP 7.2 and MySQL 5.7 (based on CentOS 7.x).
    For some reason it's installing MySQL 5.7, but it refuses to start.

    So maybe I did something wrong; did a new install, but this time with MySQL 5.6 and installed perfectly and everything working (also CentOS 7.x).
    Then I tried to upgrade MySQL to 5.7 as advertised here: https://www.prado.lt/directadmin-ann...port-mysql-5-7

    Followed everything correctly (except for the backups, because it's a fresh install anyways). But same result, after the upgrade MySQL won't start. No matter what.
    I also tried deleting /etc/my.cnf and tried restarting. Exactly the same result.

    Starting mysqld (via systemctl): Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
    [FAILED]

    The "systemctl status mysqld.service" gives me this:
    * mysqld.service - MySQL Server
    Loaded: loaded (/etc/systemd/system/mysqld.service; enabled; vendor preset: disabled)
    Active: failed (Result: start-limit) since Thu 2018-06-14 22:22:02 CEST; 30s ago
    Docs: man:mysqld(8)
    http://dev.mysql.com/doc/refman/en/using-systemd.html
    Process: 7122 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=203/EXEC)
    Main PID: 419 (code=exited, status=0/SUCCESS)

    Jun 14 22:22:02 host systemd[1]: Unit mysqld.service entered failed state.
    Jun 14 22:22:02 host systemd[1]: mysqld.service failed.
    Jun 14 22:22:02 host systemd[1]: mysqld.service holdoff time over, scheduling restart.
    Jun 14 22:22:02 host systemd[1]: start request repeated too quickly for mysqld.service
    Jun 14 22:22:02 host systemd[1]: Failed to start MySQL Server.
    Jun 14 22:22:02 host systemd[1]: Unit mysqld.service entered failed state.
    Jun 14 22:22:02 host systemd[1]: mysqld.service failed.
    Jun 14 22:22:06 host systemd[1]: start request repeated too quickly for mysqld.service
    Jun 14 22:22:06 host systemd[1]: Failed to start MySQL Server.
    Jun 14 22:22:06 host systemd[1]: mysqld.service failed.


    The output of "journalctl -xe" is (partially):

    -- Unit mysqld.service has begun starting up.
    Jun 14 22:23:02 host systemd[7226]: Failed at step EXEC spawning /usr/bin/mysqld_pre_systemd: No such file or directory
    -- Subject: Process /usr/bin/mysqld_pre_systemd could not be executed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman.../systemd-devel
    --
    -- The process /usr/bin/mysqld_pre_systemd could not be executed and failed.
    --
    -- The error number returned by this process is 2.
    Jun 14 22:23:02 host systemd[1]: mysqld.service: control process exited, code=exited status=203
    Jun 14 22:23:02 host systemd[1]: Failed to start MySQL Server.
    -- Subject: Unit mysqld.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman.../systemd-devel
    --
    -- Unit mysqld.service has failed.


    And the output, if useful, for "service mysqld status" is the following:

    PHP Code:
    Jun 14 22:17:02 host systemdStarting MySQL Server...
    Jun 14 22:17:02 host systemdFailed at step EXEC spawning /usr/bin/mysqld_pre_systemdNo such file or directory
    Jun 14 22
    :17:02 host systemdmysqld.servicecontrol process exitedcode=exited status=203
    Jun 14 22
    :17:02 host systemdFailed to start MySQL Server.
    Jun 14 22:17:02 host systemdUnit mysqld.service entered failed state.
    Jun 14 22:17:02 host systemdmysqld.service failed.
    Jun 14 22:17:02 host systemdmysqld.service holdoff time overscheduling restart.
    Jun 14 22:17:02 host systemdStarting MySQL Server...
    Jun 14 22:17:02 host systemdFailed at step EXEC spawning /usr/bin/mysqld_pre_systemdNo such file or directory
    Jun 14 22
    :17:02 host systemdmysqld.servicecontrol process exitedcode=exited status=203
    Jun 14 22
    :17:02 host systemdFailed to start MySQL Server.
    Jun 14 22:17:02 host systemdUnit mysqld.service entered failed state.
    Jun 14 22:17:02 host systemdmysqld.service failed.
    Jun 14 22:17:03 host systemdmysqld.service holdoff time overscheduling restart.
    Jun 14 22:17:03 host systemdstart request repeated too quickly for mysqld.service
    Jun 14 22
    :17:03 host systemdFailed to start MySQL Server.
    Jun 14 22:17:03 host systemdUnit mysqld.service entered failed state.
    Jun 14 22:17:03 host systemdmysqld.service failed.
    Jun 14 22:17:06 host systemdstart request repeated too quickly for mysqld.service
    Jun 14 22
    :17:06 host systemdFailed to start MySQL Server.
    Jun 14 22:17:06 host systemdmysqld.service failed.
    Jun 14 22:17:11 host systemdRemoved slice User Slice of root.
    Jun 14 22:17:11 host systemdStopping User Slice of root

    I have no clue what's wrong here. The exact same thing happens with a clean install with MySQL 5.7 and doing an upgrade of a clean install with MySQL 5.6 to MySQL 5.7.
    If I use MySQL 5.6 for a clean install everything works...

    Any advice or ideas? I am pretty clueless here.

    Thanks in advance.

    Regards

  2. #2
    Join Date
    Aug 2006
    Location
    LT, EU
    Posts
    7,099
    Please let us know the output of:
    Code:
    /usr/local/directadmin/directadmin o
    Martynas Bendorius
    MB Martynas IT. Professional server management company. Official DirectAdmin, CloudLinux, LiteSpeed and Comodo partners.

  3. #3
    Join Date
    Jul 2015
    Posts
    18
    Quote Originally Posted by smtalk View Post
    Please let us know the output of:
    Code:
    /usr/local/directadmin/directadmin o
    First off; thanks for helping!

    Now this is really weird, look at this:

    PHP Code:
    [root@host /]# /usr/local/directadmin/directadmin o
    Compiled on 'CentOS 6.0 64-Bit'
    Compile timeMar 14 2018 at 20:27:20
    Compiled with IPv6 
    While:
    PHP Code:
    [root@host /]# cat /etc/*-release
    CentOS Linux release 7.5.1804 (Core)
    NAME="CentOS Linux"
    VERSION="7 (Core)"
    ID="centos"
    ID_LIKE="rhel fedora"
    VERSION_ID="7"
    PRETTY_NAME="CentOS Linux 7 (Core)"
    ANSI_COLOR="0;31"
    CPE_NAME="cpe:/o:centos:centos:7"
    HOME_URL="https://www.centos.org/"
    BUG_REPORT_URL="https://bugs.centos.org/"

    CENTOS_MANTISBT_PROJECT="CentOS-7"
    CENTOS_MANTISBT_PROJECT_VERSION="7"
    REDHAT_SUPPORT_PRODUCT="centos"
    REDHAT_SUPPORT_PRODUCT_VERSION="7"

    CentOS Linux release 7.5.1804 (Core)
    CentOS Linux release 7.5.1804 (Core)
    [
    root@host /]
    Very strange?!

  4. #4
    Join Date
    Feb 2005
    Posts
    182
    Make sure your license is configured for CentOS7 in the directadmin clients panel and reinstall directadmin.

  5. #5
    Join Date
    Jul 2015
    Posts
    18
    Quote Originally Posted by ViAdCk View Post
    Make sure your license is configured for CentOS7 in the directadmin clients panel and reinstall directadmin.
    Man... I feel like a complete idiot. It was an used license for a different server and indeed CentOS 6.x, however I *thought* I changed it yesterday.
    But apparently it still showed CentOS 6.x in the client panel...

    I really, really feel stupid... :S

    Thanks for pointing it out. I am redoing the setup now. But I guess it will work correctly now.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •