Learn about Centmin Mod LEMP Stack today
Register Now

[Solved] MariaDB MariaDB failed to restart at first install

Discussion in 'Bug Reports' started by pamamolf, Dec 3, 2019.

  1. pamamolf

    pamamolf Premium Member Premium Member

    4,070
    427
    83
    May 31, 2014
    Ratings:
    +832
    Local Time:
    4:57 AM
    Nginx-1.25.x
    MariaDB 10.3.x
    Please fill in any relevant information that applies to you:
    • CentOS Version: CentOS 7 64bit
    • Centmin Mod Version Installed: 123.09beta01
    Hello

    Just got a test server from Hetzner a simple vps and i install Centminmod using:


    Code:
    yum -y update; curl -O https://centminmod.com/betainstaller73.sh && chmod 0700 betainstaller73.sh && bash betainstaller73.sh
    At the end of installation i got this:
    Code:
    **********************************************************************
    * Starting Services...
    **********************************************************************
    Starting nginx (via systemctl):  [  OK  ]
    Starting mysql (via systemctl):  Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.servic                                                                                     e" and "journalctl -xe" for details.
    [FAILED]
    MariaDB failed to start...

    So i run:
    Code:
    journalctl -xe
    and i got this:

    Code:
    Dec 03 13:25:54 server.mydomain.com systemd[1]: mariadb.service start operation timed out. Terminating.
    Dec 03 13:25:54 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:56 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:56 server.mydomain.com systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:58 server.mydomain.com kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=96:00:00:38:3f:73:d2:74:7f:6e:37:e3:08:00 SRC=191.37.229.70 DST=78.46.239.163 LEN=44 TOS=0x00 PREC=0x00 TTL=42 ID=41593 PROTO=TCP SPT=36149
    Dec 03 13:25:58 server.mydomain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Dec 03 13:25:58 server.mydomain.com systemd[1]: Failed to start MariaDB 10.3.20 database server.
    -- Subject: Unit mariadb.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit mariadb.service has failed.
    --
    -- The result is failed.
    Dec 03 13:25:58 server.mydomain.com systemd[1]: Unit mariadb.service entered failed state.
    Dec 03 13:25:58 server.mydomain.com systemd[1]: mariadb.service failed.
    Dec 03 13:25:58 server.mydomain.com polkitd[572]: Unregistered Authentication Agent for unix-process:16981:303831 (system bus name :1.191, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconn
    Dec 03 13:25:58 server.mydomain.com polkitd[572]: Registered Authentication Agent for unix-process:17309:313272 (system bus name :1.196 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/Auth
    Dec 03 13:25:58 server.mydomain.com systemd[1]: Starting ConfigServer Firewall & Security - csf...
    And then i run this:
    Code:
    systemctl status mariadb.service
    and i got this:
    Code:
    mariadb.service - MariaDB 10.3.20 database server
       Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/mariadb.service.d
               └─migrated-from-my.cnf-settings.conf, openfileslimit.conf, protecthome.conf
       Active: failed (Result: exit-code) since Tue 2019-12-03 13:25:58 UTC; 10min ago
         Docs: man:mysqld(8)
               https://mariadb.com/kb/en/library/systemd/
     Main PID: 17258 (code=exited, status=1/FAILURE)
       Status: "MariaDB server is down"
    
    Dec 03 13:25:55 server.supereventforall.info systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.supereventforall.info systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.supereventforall.info systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:55 server.supereventforall.info systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:56 server.supereventforall.info systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:56 server.supereventforall.info systemd[1]: Got notification message from PID 31311, but reception only permitted for main PID 17258
    Dec 03 13:25:58 server.supereventforall.info systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
    Dec 03 13:25:58 server.supereventforall.info systemd[1]: Failed to start MariaDB 10.3.20 database server.
    Dec 03 13:25:58 server.supereventforall.info systemd[1]: Unit mariadb.service entered failed state.
    Dec 03 13:25:58 server.supereventforall.info systemd[1]: mariadb.service failed.
    Something seems to be wrong related to PID of it ....

    After that starting it using mysqlstart was ok.

    Thanks
     
  2. eva2000

    eva2000 Administrator Staff Member

    53,614
    12,139
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,683
    Local Time:
    11:57 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
  3. pamamolf

    pamamolf Premium Member Premium Member

    4,070
    427
    83
    May 31, 2014
    Ratings:
    +832
    Local Time:
    4:57 AM
    Nginx-1.25.x
    MariaDB 10.3.x
    I am uploading the file here as it is a bit big...

    Thanks
     
  4. eva2000

    eva2000 Administrator Staff Member

    53,614
    12,139
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,683
    Local Time:
    11:57 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    The log wasn't sanitised, so best to do fresh CentOS 7 + Centmin Mod install to have regenerated your logins etc after this.

    Install log looks fine though other than mariadb mysql server not starting on 1st start up

    What version of CentOS did you start on before running centmin mod install with the yum update ? CentOS 7.7 or earlier ? like CentOS 7.0 was installed on server, then you updated to CentOS 7.7 with yum update + centmin mod install command without rebooting server for updates between CentOS 7.0 and CentOS 7.7 update ?
     
  5. eva2000

    eva2000 Administrator Staff Member

    53,614
    12,139
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,683
    Local Time:
    11:57 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Services using the "Type=Notify" and "NotifyAccess=All" settings are vulnerable to being inadvertently shut down by other services - Red Hat Customer Portal

    Might need to add a delay for MariaDB service startup for the 1st time
     
  6. pamamolf

    pamamolf Premium Member Premium Member

    4,070
    427
    83
    May 31, 2014
    Ratings:
    +832
    Local Time:
    4:57 AM
    Nginx-1.25.x
    MariaDB 10.3.x
    No problem :)

    Don't remember to be honest as it is a test server and i format it every x hours :)

    You know...
     
  7. eva2000

    eva2000 Administrator Staff Member

    53,614
    12,139
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,683
    Local Time:
    11:57 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    FYI, I'd updated 123.09beta01 with a fix for this for Centmin Mod initial installs by raising the max PID limits to prevent PID reuse.
     
  8. eva2000

    eva2000 Administrator Staff Member

    53,614
    12,139
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,683
    Local Time:
    11:57 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    interesting I am now getting this as well on mariadb first restart after initial install
    Code (Text):
    Dec 08 06:15:31 centos-2cpu-4gb-us-sjo1 systemd[1]: Got notification message from PID 17561, but reception only permitted for main PID 62529
    Dec 08 06:15:31 centos-2cpu-4gb-us-sjo1 systemd[1]: Got notification message from PID 17561, but reception only permitted for main PID 62529
    Dec 08 06:15:31 centos-2cpu-4gb-us-sjo1 systemd[1]: Got notification message from PID 17561, but reception only permitted for main PID 62529
    Dec 08 06:15:31 centos-2cpu-4gb-us-sjo1 systemd[1]: Got notification message from PID 17561, but reception only permitted for main PID 62529
    Dec 08 06:15:31 centos-2cpu-4gb-us-sjo1 systemd[1]: Got notification message from PID 17561, but reception only permitted for main PID 62529
    Dec 08 06:15:31 centos-2cpu-4gb-us-sjo1 systemd[1]: Got notification message from PID 17561, but reception only permitted for main PID 62529
    
     
  9. eva2000

    eva2000 Administrator Staff Member

    53,614
    12,139
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,683
    Local Time:
    11:57 AM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Believe I fixed this in latest 123.09beta01 update and it shaves ~100 seconds of that mariadb service restart stall too on initial install's final mariadb service start in CentOS 7 :D
     
  10. EckyBrazzz

    EckyBrazzz Active Member

    916
    189
    43
    Mar 28, 2018
    >>>>Click here<<<< i'm nearby......
    Ratings:
    +362
    Local Time:
    10:57 PM
    Latest
    Latest
    Just see this now, had the same issue when setting up a new server. (same date). Manual startup did the trick.