Issue SQLSTATE[HY000] [2002] No such file or directory

[Nicklls]

Greetings,

I had an unexpected shutdown to the server which in result after powering up gave me the following...

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


I followed some solutions through the KB but nothing worked so far. Plesk is unaccessible

#mysql status - shows that is running but restarting the service always fails although the status is always on running.

mysql Ver 14.14 Distrib 5.5.55

Plesk Onyx on the latest version

mysql.log file prints the following

multiple entries of the following error with different seq number

This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 226945 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x79005e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x6781f3]
/lib64/libpthread.so.0(+0xf7e0)[0x7f1d8042c7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f1d7e8704f5]
/lib64/libc.so.6(abort+0x175)[0x7f1d7e871cd5]
/usr/libexec/mysqld[0x8269d4]
/usr/libexec/mysqld[0x826d41]
/usr/libexec/mysqld[0x8e4bff]
/usr/libexec/mysqld[0x8daf85]
/usr/libexec/mysqld[0x825695]
/usr/libexec/mysqld[0x8188cc]
/usr/libexec/mysqld[0x81ca13]
/lib64/libpthread.so.0(+0x7aa1)[0x7f1d80424aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f1d7e926c4d]
The manual page at MySQL :: MySQL 8.0 Reference Manual :: B.4.3.3 What to Do If MySQL Keeps Crashing contains
information that should help you find out what is causing the crash.
190625 16:38:55 [Note] Plugin 'FEDERATED' is disabled.
190625 16:38:55 InnoDB: The InnoDB memory heap is disabled
190625 16:38:55 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190625 16:38:55 InnoDB: Compressed tables use zlib 1.2.3
190625 16:38:55 InnoDB: Using Linux native AIO
190625 16:38:55 InnoDB: Initializing buffer pool, size = 12.0G
190625 16:38:56 InnoDB: Completed initialization of buffer pool
190625 16:38:56 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
190625 16:38:56 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
190625 16:38:56 InnoDB: Error: page 6 log sequence number 239452500219
InnoDB: is in the future! Current system log sequence number 239451927149.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.23.2 Forcing InnoDB Recovery
InnoDB: for more information.

Tried innodb_force_recovery = 1, 2, 3 but with no luck.
plesk repair does not work either.
df -h & -i shows a lot of available space...

Any suggestions? Thank you

 

[IgorG]

Any suggestions?

Contact Plesk Support Team. They will check and fix the issue directly on your server.