Question

systemd[1]: Stopped MySQL Community Server

Posted December 9, 2019 1.6k views
Ubuntu 16.04
10-10-50-101 systemd[1]: Stopped MySQL Community Server. -- Subject: Unit mysql.service has finished shutting down -- Defined-By: systemd

I have updated to ubuntu 16.04 and mySql Stopped working

systemctl status mysql.service:

● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; disabled; vendor preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Mon 2019-12-09 16:36:00 UTC; 11s ago
  Process: 16289 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
  Process: 16280 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 16289 (code=exited, status=1/FAILURE);         : 16290 (mysql-systemd-s)
    Tasks: 2
   Memory: 316.0K
      CPU: 294ms
   CGroup: /system.slice/mysql.service
           └─control
             ├─16290 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─16343 sleep 1

Dec 09 16:36:00 ip-10-10-50-101 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Dec 09 16:36:00 ip-10-10-50-101 systemd[1]: Stopped MySQL Community Server.
Dec 09 16:36:00 ip-10-10-50-101 systemd[1]: Starting MySQL Community Server...
Dec 09 16:36:02 ip-10-10-50-101 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE

journalctl -xe:

Dec 09 16:36:00 ip-10-10-50-101 sudo[16133]: pam_unix(sudo:session): session closed for user root
Dec 09 16:36:00 ip-10-10-50-101 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Dec 09 16:36:00 ip-10-10-50-101 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.
Dec 09 16:36:00 ip-10-10-50-101 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.
Dec 09 16:36:02 ip-10-10-50-101 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Dec 09 16:36:30 ip-10-10-50-101 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.
Dec 09 16:36:30 ip-10-10-50-101 systemd[1]: mysql.service: Unit entered failed state.
Dec 09 16:36:30 ip-10-10-50-101 systemd[1]: mysql.service: Failed with result 'exit-code'.
Dec 09 16:36:30 ip-10-10-50-101 systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Dec 09 16:36:30 ip-10-10-50-101 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.
Dec 09 16:36:30 ip-10-10-50-101 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.
Dec 09 16:36:32 ip-10-10-50-101 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
lines 3188-3226/3226 (END)

Any helping hand?

Thank you

edited by MattIPv4

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.

×
2 answers

Hello, @cdeva

Can you also check the MySQL error log to see if there is a more detailed error logged? This can happen when there is insufficient RAM.

The location of the log should be:

/var/log/mysql/error.log

Looking forward to hearing from your

Regards,
Alex

Hello, @cdeva

Thanks for sharing this information.

Could you please let me know if the issue is still occurring? If that is correct you can also check the RAM usage on your droplet. You can do that by running:

free -m

or using top / htop

It will help you to determinate if the droplet is utilizing all of it’s RAM.

Let me know how it goes.

Regards,
Alex G

Submit an Answer