Related

Product Now Available: Managed MySQL Databases Product
install mysql 3.24 on ubuntu 16.04 Question Question
Automatically restart MySQL on Ubuntu 16.04.x - If statement may be wrong? Question Question

Question

MySQL stopped and it can't be restart

Posted April 25, 2017 187.6k views
MySQLUbuntu 16.04

Hi there,

I have a big issue on my droplet.

Today, after pull from my git repo, I install a php extension (imagick).

After that, mysql began to start/stop frequenty, and now I am not able to restart it.

If i try:

sudo service mysql restart

It says me 

Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.

Log of journalctl -xe says:

-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has failed.
-- 
-- The result is failed.
Apr 25 10:41:38 wordpress-512mb-ams3-01 systemd[1]: mysql.service: Unit entered failed state.
Apr 25 10:41:38 wordpress-512mb-ams3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 25 10:41:38 wordpress-512mb-ams3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Apr 25 10:41:38 wordpress-512mb-ams3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has finished shutting down.
Apr 25 10:41:38 wordpress-512mb-ams3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mysql.service has begun starting up.
Apr 25 10:41:38 wordpress-512mb-ams3-01 audit[3864]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/3864/status" pid=3864 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112
Apr 25 10:41:38 wordpress-512mb-ams3-01 kernel: audit: type=1400 audit(1493116898.796:1567): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/3864/status" pid=3864 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112
Apr 25 10:41:38 wordpress-512mb-ams3-01 audit[3864]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=3864 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=0
Apr 25 10:41:38 wordpress-512mb-ams3-01 audit[3864]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/3864/status" pid=3864 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112
Apr 25 10:41:38 wordpress-512mb-ams3-01 kernel: audit: type=1400 audit(1493116898.812:1568): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=3864 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=0
Apr 25 10:41:38 wordpress-512mb-ams3-01 kernel: audit: type=1400 audit(1493116898.812:1569): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/3864/status" pid=3864 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=112 ouid=112
Apr 25 10:41:39 wordpress-512mb-ams3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE

And finally, /var/log/mysql/error.log says:

2017-04-25T10:45:43.868541Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-04-25T10:45:43.868576Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-04-25T10:45:43.868596Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-04-25T10:45:43.868615Z 0 [ERROR] Failed to initialize plugins.
2017-04-25T10:45:43.868629Z 0 [ERROR] Aborting

2017-04-25T10:45:43.868673Z 0 [Note] Binlog end
2017-04-25T10:45:43.868837Z 0 [Note] Shutting down plugin 'CSV'
2017-04-25T10:45:43.869563Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

Any help would be appreciated, thank you in advance.

Add a comment
gianmarcotoscano
By:
gianmarcotoscano
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
12 answers
kylegerm87 December 20, 2018

Guys, what the hell…

  1. One-click MySQL install.
  2. Connect from remote serve; You know, the only thing a database does in this configuration…
  3. 3hrs, 5 third party blog tutorials, 10 StackOverflow questions later…
  4. Now I’m here. With a useless database instance, no intelligible errors and nowhere left to turn

This very un-DigitalOcean like. Kind of unreal

Reply Report
tastardotlstudio April 10, 2019

I am also facing the same problem. I do not understand why they are making changes internally. In the starting period its working fine no issue. After a few months, it showing such error. I did not understand what is the business policy?
Why every one suggesting increase size?
I already increase the size to 2 GB still having the same issue.
Many times server going down.

Reply Report
gianmarcotoscano April 25, 2017

Hi,

here you have what you asked me:

2017-04-25T11:05:06.131450Z 0 [Note] Binlog end
2017-04-25T11:05:06.131597Z 0 [Note] Shutting down plugin 'CSV'
2017-04-25T11:05:06.132363Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

2017-04-25T11:05:36.361208Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-04-25T11:05:36.361401Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-04-25T11:05:36.688896Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-04-25T11:05:36.694729Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.17-0ubuntu0.16.04.2) starting as process 7624 ...
2017-04-25T11:05:36.708734Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-04-25T11:05:36.708823Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-04-25T11:05:36.708835Z 0 [Note] InnoDB: Uses event mutexes
2017-04-25T11:05:36.708845Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-04-25T11:05:36.708855Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-04-25T11:05:36.708865Z 0 [Note] InnoDB: Using Linux native AIO
2017-04-25T11:05:36.709647Z 0 [Note] InnoDB: Number of pools: 1
2017-04-25T11:05:36.710008Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-04-25T11:05:36.714526Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-04-25T11:05:36.714649Z 0 [ERROR] InnoDB: mmap(137428992 bytes) failed; errno 12
2017-04-25T11:05:36.714679Z 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2017-04-25T11:05:36.714707Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-04-25T11:05:36.714729Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-04-25T11:05:36.714741Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-04-25T11:05:36.714767Z 0 [ERROR] Failed to initialize plugins.
2017-04-25T11:05:36.714775Z 0 [ERROR] Aborting

2017-04-25T11:05:36.714803Z 0 [Note] Binlog end
2017-04-25T11:05:36.714950Z 0 [Note] Shutting down plugin 'CSV'
2017-04-25T11:05:36.715472Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

I also checked RAM memory usage with htop, I have 103 Mb free now.

Thank you in advance

Reply Report
  • hansen April 25, 2017

    @gianmarcotoscano
    As expected, it was forced-closed because it was running out of RAM. The giveaway is this line [ERROR] InnoDB: Cannot allocate memory for the buffer pool

    But if you are on a 512MB droplet running both git and a full WordPress, then it is expected to run out of RAM. It’s actually quite difficult to run WordPress on 512MB.

    I would generally say that WordPress needs 1GB RAM minimum in production. You might be able to run on 512MB, but if just a couple of people visit your site at the same time and WordPress is checking for updates, then you can easily run out of RAM.

    Reply Report
    • mformainuddin August 23, 2017

      @hansen

      What i should do now???

      root@ubuntu-1gb-nyc3-01:~# sudo service mysqld stop
Failed to stop mysqld.service: Unit mysqld.service not loaded.
root@ubuntu-1gb-nyc3-01:~# clear
root@ubuntu-1gb-nyc3-01:~# sudo service mysql stop
root@ubuntu-1gb-nyc3-01:~# sudo service mysql start
Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -              xe" for details.
root@ubuntu-1gb-nyc3-01:~# sudo systemctl status mysql.service
● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Wed 2017-08-23 18:52:07 UTC; 2s ago
  Process: 21445 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
  Process: 21437 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 21445 (code=exited, status=1/FAILURE);         : 21446 (mysql-systemd-s)
    Tasks: 2
   Memory: 324.0K
      CPU: 250ms
   CGroup: /system.slice/mysql.service
           └─control
             ├─21446 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─21468 sleep 1

Aug 23 18:52:07 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
Aug 23 18:52:08 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
root@ubuntu-1gb-nyc3-01:~# sudo journalctl -xe
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: Started Daily apt activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apt-daily.service has finished starting up.
--
-- The start-up result is done.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 6h 8min 17.785945s random time.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 11h 27min 49.819834s random time.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/st
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/s
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/st
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:589): apparmor="DENIED" operation="open" profile="/usr
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:590): apparmor="DENIED" operation="open" profile="/usr
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:591): apparmor="DENIED" operation="open" profile="/usr
Aug 23 18:52:39 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]: pam_unix(sudo:session): session opened for user root by root(uid=0)
lines 2005-2046/2046 (END)
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: Started Daily apt activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apt-daily.service has finished starting up.
--
-- The start-up result is done.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 6h 8min 17.785945s random time.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 11h 27min 49.819834s random time.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/stat
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/sys
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/stat
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:589): apparmor="DENIED" operation="open" profile="/usr/s
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:590): apparmor="DENIED" operation="open" profile="/usr/s
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:591): apparmor="DENIED" operation="open" profile="/usr/s
Aug 23 18:52:39 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]: pam_unix(sudo:session): session opened for user root by root(uid=0)
lines 2005-2046/2046 (END)
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: Started Daily apt activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apt-daily.service has finished starting up.
--
-- The start-up result is done.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 6h 8min 17.785945s random time.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 11h 27min 49.819834s random time.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status"
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status"
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:589): apparmor="DENIED" operation="open" profile="/usr/sbin/
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:590): apparmor="DENIED" operation="open" profile="/usr/sbin/
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:591): apparmor="DENIED" operation="open" profile="/usr/sbin/
Aug 23 18:52:39 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]: pam_unix(sudo:session): session opened for user root by root(uid=0)
lines 2005-2046/2046 (END)
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: Started Daily apt activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apt-daily.service has finished starting up.
--
-- The start-up result is done.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 6h 8min 17.785945s random time.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 11h 27min 49.819834s random time.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status" pid
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/nod
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status" pid
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:589): apparmor="DENIED" operation="open" profile="/usr/sbin/mys
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:590): apparmor="DENIED" operation="open" profile="/usr/sbin/mys
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:591): apparmor="DENIED" operation="open" profile="/usr/sbin/mys
Aug 23 18:52:39 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]: pam_unix(sudo:session): session opened for user root by root(uid=0)
lines 2005-2046/2046 (END)
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: Started Daily apt activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apt-daily.service has finished starting up.
--
-- The start-up result is done.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 6h 8min 17.785945s random time.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 11h 27min 49.819834s random time.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status" pid=2155
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" p
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status" pid=2155
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:589): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:590): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:591): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
Aug 23 18:52:39 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]: pam_unix(sudo:session): session opened for user root by root(uid=0)
...skipping...
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: Started Daily apt activities.
-- Subject: Unit apt-daily.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit apt-daily.service has finished starting up.
--
-- The start-up result is done.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 6h 8min 17.785945s random time.
Aug 23 18:52:32 ubuntu-1gb-nyc3-01 systemd[1]: apt-daily.timer: Adding 11h 27min 49.819834s random time.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Failed to start MySQL Community Server.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status" pid=2155
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" p
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 audit[21554]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/21554/status" pid=2155
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:589): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:590): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
Aug 23 18:52:38 ubuntu-1gb-nyc3-01 kernel: audit: type=1400 audit(1503514358.445:591): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
Aug 23 18:52:39 ubuntu-1gb-nyc3-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]:     root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/journalctl -xe
Aug 23 18:52:49 ubuntu-1gb-nyc3-01 sudo[21595]: pam_unix(sudo:session): session opened for user root by root(uid=0)

root@ubuntu-1gb-nyc3-01:~# tail -30 /var/log/mysql/error.log
2017-08-23T18:56:12.091396Z 0 [Note] InnoDB: Uses event mutexes
2017-08-23T18:56:12.091413Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-08-23T18:56:12.091426Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-08-23T18:56:12.091437Z 0 [Note] InnoDB: Using Linux native AIO
2017-08-23T18:56:12.092156Z 0 [Note] InnoDB: Number of pools: 1
2017-08-23T18:56:12.092522Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-08-23T18:56:12.096627Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-08-23T18:56:12.119604Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-08-23T18:56:12.126470Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-23T18:56:12.141470Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-23T18:56:12.170682Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-23T18:56:12.170811Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-23T18:56:12.184443Z 0 [Warning] InnoDB: 1048576 bytes should have been written. Only 856064 bytes written. Retrying for the remaining bytes.
2017-08-23T18:56:12.184491Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
2017-08-23T18:56:12.184506Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 6291456, 1048576 bytes should have been written, only 856064 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2017-08-23T18:56:12.184523Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
2017-08-23T18:56:12.184531Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-08-23T18:56:12.184542Z 0 [ERROR] InnoDB: Could not set the file size of './ibtmp1'. Probably out of disk space
2017-08-23T18:56:12.184550Z 0 [ERROR] InnoDB: Unable to create the shared innodb_temporary
2017-08-23T18:56:12.184558Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-08-23T18:56:12.790524Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-08-23T18:56:12.790651Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-08-23T18:56:12.790675Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-08-23T18:56:12.790743Z 0 [ERROR] Failed to initialize plugins.
2017-08-23T18:56:12.790761Z 0 [ERROR] Aborting

2017-08-23T18:56:12.790777Z 0 [Note] Binlog end
2017-08-23T18:56:12.791019Z 0 [Note] Shutting down plugin 'MyISAM'
2017-08-23T18:56:12.792446Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

      That’ll be very helpful if you give the solution of this error cuz i’m not that much expert in linux
      & i use 1 gb droplet

      Reply Report
katiak May 8, 2020

Check this, my friend:
I find this info: https://github.com/laradock/laradock/issues/1492
and
Dryr commented on 1 May 2018 there

Looks like NOAUTOCREATE_USER is causing the issue. Removing it from the ‘mysql/my.cnf’ file seems to fix the issue as well.

I did this and works for me! Try it! ;)

Reply Report
hansen April 25, 2017

Hi @gianmarcotoscano

Can you run and post tail -30 /var/log/mysql/error.log?
Just need to get a few more lines of the crash. You need to run it after MySQL stopped.

I suspect you’re running out of RAM, but the log will tell us.

Reply Report
jtittle1 April 25, 2017

@gianmarcotoscano

In addition to this error:

[ERROR] InnoDB: Cannot allocate memory for the buffer pool

… this error also indicates that you’re running out of RAM:

InnoDB: mmap(137428992 bytes) failed; errno 12

You may have 103MB of RAM free with the MySQL service stopped, though as soon as you run:

service mysql restart

… MySQL is attempting to utilize more than what’s available and since it’s unable to do so, it fails.

For database-driven websites, I recommend at least 1GB of RAM minimum. You can run with 512MB, though it requires a lot of tweaking and tuning, and to do it, I’d recommend NGINX over Apache.

That said, upgrading is a the best route to take since MySQL, and even MariaDB and Percona, will need more than 103MB of RAM.

Reply Report
gianmarcotoscano April 26, 2017

@hansen @jtittle
Ok guys, I resized my droplet to 1Gb and now everything seems to be ok (and website also seems to go faster).

I also activated an alert if RAM consume is greater than 70% for above 10 minutes.

Do you suggest me some other tool to install or run some optimisation to avoid RAM usage problems?

Is 1Gb droplet suitable for a wordpress site with average traffic of maybe is required the 2Gb solution?

Thanks again for your help guys, I really appreciated it :)

Reply Report
  • hansen April 26, 2017

    @gianmarcotoscano
    It is difficult to say exactly, since it depends on what you mean by average traffic and how many plugins you have, how big your site is and which theme you are using.
    If it’s running okay on 1GB, then stay there - if you hit RAM limit again, then consider upgrading again.

    Reply Report
  • jtittle1 April 26, 2017

    @gianmarcotoscano

    There’s really not an automatic optimization tool in terms of one that’ll magically fix an issue with RAM usage. MySQL Tuner will help you to identify potential areas of optimization, though it’d be up to you to make the changes in MySQL’s configuration file and see what works for you.

    https://github.com/major/MySQLTuner-perl

    Ideally, MySQL should be running for 24-48 hours straight, without a restart, before you run the tool. It’ll output a lot of information and make a few suggestions towards the bottom. I wouldn’t, however, blindly make configuration changes unless you know what those changes do as you could very well end up making things worse (it’s not hard, even for someone who does know what they mean :-) ).

    The biggest issue is, simply put, the stock configuration for MySQL really isn’t meant for usage on production servers. It’s meant as a starting point. It may work well for a smaller site with low traffic, though it may crumble (and crash) under higher levels of traffic.

    There’s a lot of variables at play when it comes to tweaking and tuning MySQL. MySQL Tuner can help, but it’s not a replacement for a sysadmin / db admin.

    Reply Report
judi August 30, 2017

Hi

I am facing the same problem the log
If i try:

sudo service mysql restart
It says me

Job for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details.
Log of journalctl -xe says:

-- Unit mysql.service has failed.
--
-- The result is failed.
Aug 30 18:40:25 wordpress-1gb-nyc1-01 systemd[1]: mysql.service: Unit entered failed state.
Aug 30 18:40:25 wordpress-1gb-nyc1-01 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 30 18:40:25 wordpress-1gb-nyc1-01 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Aug 30 18:40:25 wordpress-1gb-nyc1-01 systemd[1]: Stopped MySQL Community Server.
-- Subject: Unit mysql.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Aug 30 18:40:25 wordpress-1gb-nyc1-01 systemd[1]: Starting MySQL Community Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has begun starting up.
Aug 30 18:40:25 wordpress-1gb-nyc1-01 audit[26410]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/26410/status" pid=26410 comm="mysqld"
Aug 30 18:40:25 wordpress-1gb-nyc1-01 kernel: audit: type=1400 audit(1504118425.522:880): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/2641
Aug 30 18:40:25 wordpress-1gb-nyc1-01 audit[26410]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=26410 comm="m
Aug 30 18:40:25 wordpress-1gb-nyc1-01 kernel: audit: type=1400 audit(1504118425.530:881): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/sys/devic
Aug 30 18:40:25 wordpress-1gb-nyc1-01 audit[26410]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/26410/status" pid=26410 comm="mysqld"
Aug 30 18:40:25 wordpress-1gb-nyc1-01 kernel: audit: type=1400 audit(1504118425.534:882): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/proc/2641
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 13 - Permission denied)
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.537771Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.537855Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.742839Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.742956Z 0 [Warning] Can't create test file /var/lib/mysql/wordpress-1gb-nyc1-01.lower-test
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.743015Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.19-0ubuntu0.16.04.1) starting as process 26410 ..
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.749482Z 0 [Warning] Can't create test file /var/lib/mysql/wordpress-1gb-nyc1-01.lower-test
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.749519Z 0 [Warning] Can't create test file /var/lib/mysql/wordpress-1gb-nyc1-01.lower-test
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.750155Z 0 [ERROR] failed to set datadir to /var/lib/mysql/
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.751566Z 0 [ERROR] Aborting
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.751862Z 0 [Note] Binlog end
Aug 30 18:40:25 wordpress-1gb-nyc1-01 mysqld[26410]: 2017-08-30T18:40:25.752226Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
Aug 30 18:40:25 wordpress-1gb-nyc1-01 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Aug 30 18:40:27 wordpress-1gb-nyc1-01 sshd[26393]: Failed password for root from 61.177.172.40 port 18852 ssh2
Aug 30 18:40:29 wordpress-1gb-nyc1-01 sshd[26393]: Failed password for root from 61.177.172.40 port 18852 ssh2
Aug 30 18:40:31 wordpress-1gb-nyc1-01 sshd[26393]: Failed password for root from 61.177.172.40 port 18852 ssh2
Aug 30 18:40:32 wordpress-1gb-nyc1-01 sshd[26393]: Received disconnect from 61.177.172.40 port 18852:11:  [preauth]
Aug 30 18:40:32 wordpress-1gb-nyc1-01 sshd[26393]: Disconnected from 61.177.172.40 port 18852 [preauth]
Aug 30 18:40:32 wordpress-1gb-nyc1-01 sshd[26393]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.40  user=root

And finally, /var/log/mysql/error.log says:

2017-08-29T12:29:59.400363Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-08-29T12:29:59.403844Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-08-29T12:30:00.296223Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-08-29T12:30:00.317117Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.19-0ubuntu0.16.04.1) starting as process 1391 ...
2017-08-29T12:30:00.359162Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-08-29T12:30:00.359204Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-29T12:30:00.359209Z 0 [Note] InnoDB: Uses event mutexes
2017-08-29T12:30:00.359212Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-08-29T12:30:00.359216Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-08-29T12:30:00.359219Z 0 [Note] InnoDB: Using Linux native AIO
2017-08-29T12:30:00.360329Z 0 [Note] InnoDB: Number of pools: 1
2017-08-29T12:30:00.361463Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-08-29T12:30:00.364269Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-08-29T12:30:00.448057Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-08-29T12:30:00.583506Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-08-29T12:30:00.625468Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-29T12:30:00.682899Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-08-29T12:30:00.682999Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-08-29T12:30:00.805429Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2017-08-29T12:30:00.816907Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-08-29T12:30:00.816955Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-08-29T12:30:00.819605Z 0 [Note] InnoDB: Waiting for purge to start
2017-08-29T12:30:00.869866Z 0 [Note] InnoDB: 5.7.19 started; log sequence number 2539683
2017-08-29T12:30:00.870572Z 0 [Note] Plugin 'FEDERATED' is disabled.
2017-08-29T12:30:00.870942Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-08-29T12:30:00.897935Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170829 12:30:00
2017-08-29T12:30:00.924711Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2017-08-29T12:30:00.924767Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2017-08-29T12:30:00.924786Z 0 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
2017-08-29T12:30:00.924850Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2017-08-29T12:30:01.031550Z 0 [Note] Event Scheduler: Loaded 0 events
2017-08-29T12:30:01.031890Z 0 [Note] /usr/sbin/mysqld: ready for connections.

Please help?

Reply Report
techsterz9890 January 5, 2018

I tried all posiible solution and yours solutions,
but same error with error log,please help me am stuck,your an expert and iam newbie to servers and
thanks in adavance:
Job for mysql.service failed because the control process exited with error code. See “systemctl status mysql.service” and “journalctl -xe” for details.

root@CampuseraDroplet:~# tail -30 /var/log/mysql/error.log
2018-01-05T11:56:22.047595Z 0 [Note] Shutting down plugin ‘INNODBFTDELETED’
2018-01-05T11:56:22.047599Z 0 [Note] Shutting down plugin ‘INNODBFTDEFAULTSTO PWORD’
2018-01-05T11:56:22.047602Z 0 [Note] Shutting down plugin ‘INNODBMETRICS’
2018-01-05T11:56:22.047605Z 0 [Note] Shutting down plugin ‘INNODBTEMPTABLEINF O’
2018-01-05T11:56:22.047608Z 0 [Note] Shutting down plugin ‘INNODBBUFFERPOOLST ATS’
2018-01-05T11:56:22.047611Z 0 [Note] Shutting down plugin ‘INNODBBUFFERPAGELR U’
2018-01-05T11:56:22.047615Z 0 [Note] Shutting down plugin ‘INNODBBUFFERPAGE’
2018-01-05T11:56:22.047618Z 0 [Note] Shutting down plugin ‘INNODBCMPPERINDEX_ RESET’
2018-01-05T11:56:22.047621Z 0 [Note] Shutting down plugin ‘INNODBCMPPERINDEX’
2018-01-05T11:56:22.047625Z 0 [Note] Shutting down plugin ‘INNODBCMPMEMRESET’
2018-01-05T11:56:22.047628Z 0 [Note] Shutting down plugin ‘INNODBCMPMEM’
2018-01-05T11:56:22.047649Z 0 [Note] Shutting down plugin ‘INNODBCMPRESET’
2018-01-05T11:56:22.047653Z 0 [Note] Shutting down plugin ‘INNODBCMP’
2018-01-05T11:56:22.047656Z 0 [Note] Shutting down plugin ‘INNODBLOCKWAITS’
2018-01-05T11:56:22.047659Z 0 [Note] Shutting down plugin ‘INNODBLOCKS’
2018-01-05T11:56:22.047661Z 0 [Note] Shutting down plugin ‘INNODBTRX’
2018-01-05T11:56:22.047664Z 0 [Note] Shutting down plugin ‘InnoDB’
2018-01-05T11:56:22.047855Z 0 [Note] InnoDB: FTS optimize thread exiting.
2018-01-05T11:56:22.048380Z 0 [Note] InnoDB: Starting shutdown…
2018-01-05T11:56:22.149021Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/ mysql/ibbufferpool
2018-01-05T11:56:22.149466Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 18 0105 11:56:22
2018-01-05T11:56:23.370580Z 0 [Note] InnoDB: Shutdown completed; log sequence nu mber 2674079
2018-01-05T11:56:23.372460Z 0 [Note] InnoDB: Removed temporary tablespace data f ile: “ibtmp1”
2018-01-05T11:56:23.372481Z 0 [Note] Shutting down plugin ‘MEMORY’
2018-01-05T11:56:23.372494Z 0 [Note] Shutting down plugin ‘CSV’
2018-01-05T11:56:23.372500Z 0 [Note] Shutting down plugin ‘sha256password’
2018-01-05T11:56:23.372503Z 0 [Note] Shutting down plugin ‘mysqlnativepassword ‘
2018-01-05T11:56:23.372914Z 0 [Note] Shutting down plugin ‘binlog’
2018-01-05T11:56:23.373409Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

Reply Report
arnisjuraga February 27, 2018

I have similar problem.
MariaDB is installed, works fine, but I cannot “stop” or “restart” it.

Although I have requested service stop, MariaDB is still “running” in the background and seems to me - ignores anything further :)

This is my

systemctl status mysql.service

output:

root@mysql-master:~# systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-02-27 11:50:59 UTC; 4min 57s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 22040 ExecStop=/etc/init.d/mysql stop (code=exited, status=1/FAILURE)
  Process: 21767 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS)
    Tasks: 27
   Memory: 394.3M
      CPU: 3.161s
   CGroup: /system.slice/mysql.service
           ├─21795 /bin/bash /usr/bin/mysqld_safe
           ├─21936 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --skip-log-error --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mys
           └─21937 logger -t mysqld -p daemon error

Feb 27 11:50:59 mysql-master systemd[1]: Stopping LSB: Start and stop the mysql database server daemon...
Feb 27 11:50:59 mysql-master mysql[22040]:  * Stopping MariaDB database server mysqld
Feb 27 11:50:59 mysql-master mysql[22040]:    ...fail!
Feb 27 11:50:59 mysql-master systemd[1]: mysql.service: Control process exited, code=exited status=1
Feb 27 11:50:59 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Feb 27 11:50:59 mysql-master systemd[1]: mysql.service: Unit entered failed state.
Feb 27 11:50:59 mysql-master systemd[1]: mysql.service: Failed with result 'exit-code'.
Feb 27 11:51:59 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Feb 27 11:53:43 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
Feb 27 11:53:45 mysql-master systemd[1]: Stopped LSB: Start and stop the mysql database server daemon.
lines 1-24/24 (END)
Reply Report
afsana January 30, 2019

Hi!
I am new to Ubuntu and started coding in Python few days back. Now I’m stuck because of this problem, please help.

afsana@afsana-k:~$ sudo /etc/init.d/mysql start
[sudo] password for afsana:
[....] Starting mysql (via systemctl): mysql.serviceJob for mysql.service failed because the control process exited with error code.
See “systemctl status mysql.service” and “journalctl -xe” for details.
failed!
afsana@afsana-k:~$ /etc/mysql/mysql.conf.d/mysqld.cnf
bash: /etc/mysql/mysql.conf.d/mysqld.cnf: No such file or directory
afsana@afsana-k:~$ systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; generated)
Active: failed (Result: exit-code) since Wed 2019-01-30 20:12:47 +06; 11min a
Docs: man:systemd-sysv-generator(8)
Process: 3901 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE

Jan 30 20:12:17 afsana-k systemd[1]: Starting LSB: Start and stop the mysql data
Jan 30 20:12:17 afsana-k mysql[3901]: * Starting MariaDB database server mysqld
Jan 30 20:12:47 afsana-k mysql[3901]: …fail!
Jan 30 20:12:47 afsana-k systemd[1]: mysql.service: Control process exited, code
Jan 30 20:12:47 afsana-k systemd[1]: mysql.service: Failed with result ‘exit-cod
Jan 30 20:12:47 afsana-k systemd[1]: Failed to start LSB: Start and stop the mys
lines 1-12/12 (END)…skipping…
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; generated)
Active: failed (Result: exit-code) since Wed 2019-01-30 20:12:47 +06; 11min ago
Docs: man:systemd-sysv-generator(8)
Process: 3901 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)

Jan 30 20:12:17 afsana-k systemd[1]: Starting LSB: Start and stop the mysql database server daemon…
Jan 30 20:12:17 afsana-k mysql[3901]: * Starting MariaDB database server mysqld
Jan 30 20:12:47 afsana-k mysql[3901]: …fail!
Jan 30 20:12:47 afsana-k systemd[1]: mysql.service: Control process exited, code=exited status=1
Jan 30 20:12:47 afsana-k systemd[1]: mysql.service: Failed with result 'exit-code’.
Jan 30 20:12:47 afsana-k systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
~
~
~

afsana@afsana-k:~$ tail -30 /var/log/mysql/error.log
tail: cannot open ’/var/log/mysql/error.log’ for reading: No such file or directory
afsana@afsana-k:~$ cd tail -30 /var/log/mysql/error.log
bash: cd: too many arguments
afsana@afsana-k:~$ tail -30 /var/log/mysql/error.log
tail: cannot open ’/var/log/mysql/error.log’ for reading: No such file or directory
afsana@afsana-k:~$ ^C
afsana@afsana-k:~$ journalctl -xe
Jan 30 20:09:04 afsana-k NetworkManager[765]: <info> [1548857344.0713] dhcp4 (enp1s0): nameserver '8.8.8.8’
Jan 30 20:09:04 afsana-k NetworkManager[765]: <info> [1548857344.0713] dhcp4 (enp1s0): state changed bound -> bound
Jan 30 20:09:04 afsana-k dbus-daemon[742]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher’ unit='dbus-o
Jan 30 20:09:04 afsana-k systemd[1]: Starting Network Manager Script Dispatcher Service…
– Subject: Unit NetworkManager-dispatcher.service has begun start-up
– Defined-By: systemd

– Support: http://www.ubuntu.com/support

– Unit NetworkManager-dispatcher.service has begun starting up.
Jan 30 20:09:04 afsana-k dbus-daemon[742]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher’
Jan 30 20:09:04 afsana-k systemd[1]: Started Network Manager Script Dispatcher Service.
– Subject: Unit NetworkManager-dispatcher.service has finished start-up
– Defined-By: systemd

– Support: http://www.ubuntu.com/support

– Unit NetworkManager-dispatcher.service has finished starting up.

– The start-up result is RESULT.
Jan 30 20:09:04 afsana-k nm-dispatcher[3805]: req:1 'dhcp4-change’ [enp1s0]: new request (2 scripts)
Jan 30 20:09:04 afsana-k nm-dispatcher[3805]: req:1 'dhcp4-change’ [enp1s0]: start running ordered scripts…
Jan 30 20:09:04 afsana-k dhclient[1134]: bound to 192.168.1.105 – renewal in 3088 seconds.
Jan 30 20:12:17 afsana-k sudo[3885]: afsana : TTY=pts/0 ; PWD=/home/afsana ; USER=root ; COMMAND=/etc/init.d/mysql start
Jan 30 20:12:17 afsana-k sudo[3885]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 30 20:12:17 afsana-k systemd[1]: Starting LSB: Start and stop the mysql database server daemon…
– Subject: Unit mysql.service has begun start-up
– Defined-By: systemd

– Support: http://www.ubuntu.com/support

– Unit mysql.service has begun starting up.
Jan 30 20:12:17 afsana-k mysql[3901]: * Starting MariaDB database server mysqld
Jan 30 20:12:47 afsana-k /etc/init.d/mysql[4448]: 0 processes alive and ’/usr/bin/mysqladmin –defaults-file=/etc/mysql/debian.cnf pi
Jan 30 20:12:47 afsana-k /etc/init.d/mysql[4448]: [61B blob data]
Jan 30 20:12:47 afsana-k /etc/init.d/mysql[4448]: error: 'Can’t connect to local MySQL server through socket ’/var/run/mysqld/mysqld.
Jan 30 20:12:47 afsana-k mysql[3901]: …fail!
Jan 30 20:12:47 afsana-k /etc/init.d/mysql[4448]: Check that mysqld is running and that the socket: ’/var/run/mysqld/mysqld.sock’ exi
Jan 30 20:12:47 afsana-k systemd[1]: mysql.service: Control process exited, code=exited status=1
Jan 30 20:12:47 afsana-k /etc/init.d/mysql[4448]:
Jan 30 20:12:47 afsana-k systemd[1]: mysql.service: Failed with result 'exit-code’.
Jan 30 20:12:47 afsana-k systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
– Subject: Unit mysql.service has failed
– Defined-By: systemd

– Support: http://www.ubuntu.com/support

– Unit mysql.service has failed.

– The result is RESULT.
Jan 30 20:12:47 afsana-k sudo[3885]: pamunix(sudo:session): session closed for user root
Jan 30 20:14:07 afsana-k gnome-shell[2235]: Some code accessed the property 'WindowPreviewMenu’ on the module 'windowPreview’. That p
Jan 30 20:17:01 afsana-k CRON[4631]: pamunix(cron:session): session opened for user root by (uid=0)
Jan 30 20:17:01 afsana-k CRON[4632]: (root) CMD ( cd / && run-parts –report /etc/cron.hourly)
Jan 30 20:17:01 afsana-k CRON[4631]: pam_unix(cron:session): session closed for user root

Reply Report
kalpeshnarwaniindia February 21, 2020

Check your droplet’s memory usage and if it’s very high then give it some time to come down and then try again to restart MySQL server.

You can also try restarting Apache2 server by running “service apache2 restart” and then again start mysql server by running “sudo service mysql start”.

I hope it helps.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help