After resize Droplet Maria DB stopped on Ubuntu16 Nginx

March 12, 2018 492 views
Nginx Redis WordPress Ubuntu 16.04
aargenis
By:
aargenis

Hi After resizing my droplet to 4gb Ram and 2 CPU Maria DB does not start

Got this message

sudo service mysql start

Job for mariadb.service failed because a timeout was exceeded. See "systemctl status mariadb.service" and "journalctl -xe" for details.

systemctl status mariadb.service

mariadb.service - MariaDB 10.2.13 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: failed (Result: timeout) since Mon 2018-03-12 00:29:30 UTC; 1min 7s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 2223 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 2068 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status
  Process: 2062 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 2056 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 2223 (code=exited, status=0/SUCCESS)

Mar 12 00:29:29 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:29 140371577255680 [Note] InnoDB: FTS optimize thread exiting.
Mar 12 00:29:29 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:29 140372484671232 [Note] InnoDB: Starting shutdown...
Mar 12 00:29:29 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:29 140371266889472 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
Mar 12 00:29:29 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:29 140371266889472 [Note] InnoDB: Buffer pool(s) dump completed at 180312  0:29:29
Mar 12 00:29:30 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:30 140372484671232 [Note] InnoDB: Shutdown completed; log sequence number 21026778
Mar 12 00:29:30 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:30 140372484671232 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Mar 12 00:29:30 lemp-s-1vcpu-1gb-fra1-01 mysqld[2223]: 2018-03-12  0:29:30 140372484671232 [Note] /usr/sbin/mysqld: Shutdown complete
Mar 12 00:29:30 lemp-s-1vcpu-1gb-fra1-01 systemd[1]: Failed to start MariaDB 10.2.13 database server.
Mar 12 00:29:30 lemp-s-1vcpu-1gb-fra1-01 systemd[1]: mariadb.service: Unit entered failed state.
Mar 12 00:29:30 lemp-s-1vcpu-1gb-fra1-01 systemd[1]: mariadb.service: Failed with result 'timeout'

Any Idea?

1 comment
  • Mohsen47 March 12, 2018

    @aargenis

    The output you provided is not enough to help you.

    You need to provide the last few lines of MariaDB error log which can be found here /var/log/mysqld.log if you cannot find it execute this query to get its path

    MariaDB> SHOW VARIABLES LIKE 'log_error';

    I believe it is a memory issue, how much memory did you have before?

Log In to Comment
Be the first one to answer this question.

Related Questions