• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved mysql.service can't start

Alaa Mansour

Basic Pleskian
Hello everybody

i have this problem :

Server Error
500
Zend_Db_Adapter_Exception
SQLSTATE[HY000] [2002] No such file or directory

Type Zend_Db_Adapter_Exception
Message SQLSTATE[HY000] [2002] No such file or directory
File Abstract.php
Line 144


, here is the two results

Code:
root@plesk:~# 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 Thu 2019-09-19 12:29:08 CEST; 10s ago
  Process: 8369 ExecStart=/usr/sbin/mysqld (code=exited, status=1/FAILURE)
  Process: 8361 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
 Main PID: 8369 (code=exited, status=1/FAILURE);         : 8370 (mysql-systemd-s)
    Tasks: 2
   Memory: 336.0K
      CPU: 300ms
   CGroup: /system.slice/mysql.service
           └─control
             ├─8370 /bin/bash /usr/share/mysql/mysql-systemd-start post
             └─8417 sleep 1

Sep 19 12:29:08 plesk.mns.ps systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Sep 19 12:29:08 plesk.mns.ps systemd[1]: Stopped MySQL Community Server.
Sep 19 12:29:08 plesk.mns.ps systemd[1]: Starting MySQL Community Server...
Sep 19 12:29:10 plesk.mns.ps systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE

Code:
lines 1455-1511/1511 (END)
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has finished shutting down.
Sep 19 12:27:35 plesk.mns.ps 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.
Sep 19 12:27:36 plesk.mns.ps systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
Sep 19 12:28:01 plesk.mns.ps CRON[8055]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 19 12:28:01 plesk.mns.ps CRON[8056]: (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/revisium-antivirus/scripts/ra_executor_run.php')
Sep 19 12:28:01 plesk.mns.ps CRON[8055]: pam_unix(cron:session): session closed for user root
Sep 19 12:28:03 plesk.mns.ps monit[1151]: 'mysql' failed to start
Sep 19 12:28:05 plesk.mns.ps monit[1151]: 'mysql' process is not running
Sep 19 12:28:05 plesk.mns.ps monit[1151]: 'mysql' trying to restart
Sep 19 12:28:05 plesk.mns.ps monit[1151]: 'mysql' start: /opt/psa/admin/sbin/pleskrc
Sep 19 12:28:05 plesk.mns.ps dovecot[4844]: pop3-login: Aborted login (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<bRq1aOWSRM9/AAAB>
Sep 19 12:28:05 plesk.mns.ps dovecot[4844]: pop3-login: Aborted login (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<1C+1aOWSdI1/AAAB>
Sep 19 12:28:05 plesk.mns.ps dovecot[4844]: imap-login: Aborted login (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<wHC1aOWSmtV/AAAB>
Sep 19 12:28:05 plesk.mns.ps dovecot[4844]: imap-login: Aborted login (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<XoG1aOWScut/AAAB>
Sep 19 12:28:06 plesk.mns.ps 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.
Sep 19 12:28:06 plesk.mns.ps systemd[1]: mysql.service: Unit entered failed state.
Sep 19 12:28:06 plesk.mns.ps systemd[1]: mysql.service: Failed with result 'exit-code'.
Sep 19 12:28:06 plesk.mns.ps monit[1151]: Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.
Sep 19 12:28:06 plesk.mns.ps systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Sep 19 12:28:06 plesk.mns.ps 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.
Sep 19 12:28:06 plesk.mns.ps 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.
Sep 19 12:28:06 plesk.mns.ps monit[1151]: INFO: [Thu Sep 19 12:28:05 CEST 2019]: Service: mysql, Action: start
Sep 19 12:28:06 plesk.mns.ps monit[1151]:  Trying to start service mysql... /usr/sbin/mysqld is stopped
Sep 19 12:28:06 plesk.mns.ps monit[1151]: Sep 19 12:28:06 plesk.mns.ps systemd[1]: Failed to start MySQL Community Server.
Sep 19 12:28:06 plesk.mns.ps monit[1151]: Sep 19 12:28:06 plesk.mns.ps systemd[1]: mysql.service: Unit entered failed state.
Sep 19 12:28:06 plesk.mns.ps monit[1151]: Sep 19 12:28:06 plesk.mns.ps systemd[1]: mysql.service: Failed with result 'exit-code'.
Sep 19 12:28:06 plesk.mns.ps monit[1151]: WARNING!
Sep 19 12:28:06 plesk.mns.ps monit[1151]: Some problems are found during start service mysql(see log file: /var/log/plesk/rc_actions.log)
Sep 19 12:28:06 plesk.mns.ps monit[1151]: Continue...
Sep 19 12:28:07 plesk.mns.ps monit[1151]: Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
Sep 19 12:28:07 plesk.mns.ps monit[1151]: Collector: no server available -- aborting message
Sep 19 12:28:08 plesk.mns.ps systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE
~
~


I cant understand what is going on?any help please?
 
Do you see more details in
# systemctl status mysql.service
or
# journalctl -xe
? Normally these should show a detailed explanation on why it is shutting down or not starting.
 
Back
Top