Discover Centmin Mod today
Register Now

MariaDB mysql no longer started.

Discussion in 'Nginx, PHP-FPM & MariaDB MySQL' started by Max, Jul 3, 2023.

  1. Max

    Max Member

    115
    5
    18
    Feb 17, 2018
    Ratings:
    +9
    Local Time:
    10:17 AM
    Please fill in any relevant information that applies to you:
    • CentOS 7.9.2009 64
    • Centmin Mod Version Installed: i.e. 123.08stable or 123.09beta01
    • Nginx Version Installed: 1.25.1
    • PHP Version Installed: 8.1
    • MariaDB MySQL Version Installed: 10.3
    • Persistent Config:
      Code:
      CF_DNSAPI_GLOBAL='y'
      CF_Token="YkOCiGpdhMU0kUKXg2sUrLwvYgP1aWR6rZppT60X"
      CF_Account_ID="5ac05b7a32f948c9517a6388fc9737d0"
      NGINX_SSLCACHE_ALLOWOVERRIDE='y'
      NGINX_STAPLE_CACHE_OVERRIDE='y'
      NGINX_STAPLE_CACHE_TTL='86400'
      SET_DEFAULT_MYSQLCHARSET='utf8mb4'
      AUTOHARDTUNE_NGINXBACKLOG='y'
      ZSTD_LOGROTATE_NGINX='y'
      ZSTD_LOGROTATE_PHPFPM='y'
      LETSENCRYPT_DETECT='y'
      ACME_DEFAULT_CA='zerossl'
      DUALCERTS='y'
      SELFSIGNEDSSL_ECDSA='y'
      NGINX_LIBBROTLI='y'
      NGXDYNAMIC_BROTLI='y'
      PHP_PGO_ALWAYS='y'
      PHP_PGO='y'
      PHP_BROTLI='y'
      PHP_LZFOUR='y'
      PHP_LZF='y'
      PHP_ZSTD='y'
      PHPFINFO='y'
      WPCLI_CE_QUERYSTRING_INCLUDED='y'
      MARCH_TARGETNATIVE='n'
      
      The disk was full due to backups. Now mysql no longer started.
    • Error when establishing a database connection
    • Code:
      sudo systemctl restart mysql.service
      Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
      [17:01][root@happy.mojobox.org ~]# systemctl status mariadb.service
      ● mariadb.service - MariaDB 10.3.39 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, notifyaccess.conf, openfileslimit.conf, protecthome.conf
         Active: failed (Result: exit-code) since So 2023-07-02 17:01:19 UTC; 12s ago
           Docs: man:mysqld(8)
                 https://mariadb.com/kb/en/library/systemd/
        Process: 8182 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
        Process: 7918 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
        Process: 7916 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
       Main PID: 8182 (code=exited, status=1/FAILURE)
         Status: "MariaDB server is down"
      
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Buffer pool(s) load completed at 230702 17:01:17
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] Plugin 'FEEDBACK' is disabled.
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [ERROR] Aborting
      Jul 02 17:01:19 happy.mojobox.org mysqld[8182]: Warning: Memory not freed: 405264952
      Jul 02 17:01:19 happy.mojobox.org systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
      Jul 02 17:01:19 happy.mojobox.org systemd[1]: Failed to start MariaDB 10.3.39 database server.
      Jul 02 17:01:19 happy.mojobox.org systemd[1]: Unit mariadb.service entered failed state.
      Jul 02 17:01:19 happy.mojobox.org systemd[1]: mariadb.service failed.
      
    • Code:
      ol/mail/root.
      [17:01][root@happy.mojobox.org ~]# journalctl -xe
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Uses event mutexes
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Number of pools: 1
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Using SSE2 crc32 instructions
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Completed initialization of buffer pool
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Waiting for purge to start
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: 10.3.39 started; log sequence number 1923305139; transaction id 2225561
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] InnoDB: Buffer pool(s) load completed at 230702 17:01:17
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [Note] Plugin 'FEEDBACK' is disabled.
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
      Jul 02 17:01:17 happy.mojobox.org mysqld[8182]: 2023-07-02 17:01:17 0 [ERROR] Aborting
      Jul 02 17:01:19 happy.mojobox.org mysqld[8182]: Warning: Memory not freed: 405264952
      Jul 02 17:01:19 happy.mojobox.org systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
      Jul 02 17:01:19 happy.mojobox.org systemd[1]: Failed to start MariaDB 10.3.39 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.
      --
      
    how can i fix this error?


    thanks
     
  2. eva2000

    eva2000 Administrator Staff Member

    52,786
    12,080
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,607
    Local Time:
    7:17 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Did you clear up disk used space? To be safe you probably want to backup your databases by shutting down MariaDB MySQL first and making a physical copy of your MySQL data directory /var/lib/mysql but be mindful of disk usage for copy. Then if you might want to hire a professional to look into the extend of data corruption that may have occurred due to running out of disk space as MySQL logs excerpt you provided might not show the whole picture.

    The excerpt you provided shows Aria table corruption which you had a similar issue before a few years ago so check https://community.centminmod.com/threads/mysql-not-start.17542/#post-74217 just for that issue. Again from info provided, we do not know the extent of damage or corruption if any.
     
  3. Max

    Max Member

    115
    5
    18
    Feb 17, 2018
    Ratings:
    +9
    Local Time:
    10:17 AM
    yes my stupidity not to use the search.


    rm -rf /var/lib/mysql/aria_log_control /var/lib/mysql/aria_log_control.orig

    and works

    close