Articles in this section

See more

Plesk shows ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory

Avatar
Alexandr Tumanov
Updated
Follow

Applicable to:

  • Plesk for Linux

Note: This is a troubleshooting article for Plesk server only that may require basic technical knowledge and SSH/RDP connection to the server. If you don't have SSH/RDP credentials, contact server's administrator or hosting support that hosts your server. Solution without SSH is possible only on Plesk Onyx 17.8.

General troubleshooting steps for Plesk Onyx 17.8

  1. Click Open Repair Kit and log in with Plesk admin credentials.
    Repair Kit
  2. Try to free up disk space
    Repair Kit
  3. If it was successful, try starting MySQL/MariaDB service by clicking Restart Processes
    Repair Kit
  4. If it was successfully started, click Log In to Plesk button
    Repair Kit
  5. If the issue persists, connect to the server via SSH and free up disk space or apply the instruction below.

 

General troubleshooting steps for other Plesk versions

This error usually means that MySQL is down or it is not working properly. Such behavior can occur after a system update, sudden OS shutdown or after incorrect actions with packages. The following steps should be done in order to troubleshoot the issue and find the cause of it:

  1. Log in to the server console or run Terminal and make sure that the server has enough free disk space and inodes:

    # df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/ploop21792p1 40G 4.9G 33G 13% /
    none 1.5G 4.0K 1.5G 1% /dev
    none 1.5G 0 1.5G 0% /dev/shm

    # df -i
    Filesystem Inodes IUsed IFree IUse% Mounted on
    /dev/ploop21792p1 2621440 180351 2441089 7% /
    none 393216 152 393064 1% /dev
    none 393216 1 393215 1% /dev/shm

    Note: All the listed partitions should have free disk space.

  2. Try to start MySQL service:

    # service mysqld start
    or
    # service mariadb start

    Note: On different OS versions the service may be mysql, mariadb

  3. If the service failed to start, try to find the error in service status:

    # service mysqld status
    or
    # service mariadb status

    or check service log located at /var/log/mysqld.log

    Note: The location of log may be also /var/log/mysql/error.log

  4. If you've found the following error "InnoDB log sequence number is in the future" please check the following article: #213939865

  5. The most popular issues are described below as well. Use the error from the output and try to find a solution in our knowledgebase

 

Related HUBs

Comments

2 comments

Sort by Date Votes
  • Avatar
    Matt Downer

    Crap. I go in via hyper visor and I am direct console access and login as root, can you do a remote session?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @Matt, as I can see, you have already submitted a support request to us with this issue.

    The investigation is ongoing.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles