[提問] V3 SQLSTATE [HY000][2002] No such file or directory 報錯

參謀帶個長

用的是WDCP V3，訪問網(wǎng)站，時不時就出現(xiàn)SQLSTATE [HY000][2002] No such file or directory這樣的錯誤，請問大神這是什么原因��？

admin

這錯誤還第一次見，可以檢查下mysql的日志

參謀帶個長

160419 12:11:57 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.5.48/data
160419 12:11:57 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160419 12:11:57 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160419 12:11:57 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld (mysqld 5.5.48) starting as process 14248 ...
160419 12:11:57 [Note] Plugin 'FEDERATED' is disabled.
160419 12:11:57 InnoDB: The InnoDB memory heap is disabled
160419 12:11:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160419 12:11:57 InnoDB: Compressed tables use zlib 1.2.3
160419 12:11:57 InnoDB: Initializing buffer pool, size = 128.0M
160419 12:11:57 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
160419 12:11:57  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
160419 12:11:57  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
160419 12:11:58  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
160419 12:11:58  InnoDB: Waiting for the background threads to start
160419 12:11:59 InnoDB: 5.5.48 started; log sequence number 0
160419 12:11:59 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160419 12:11:59 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160419 12:11:59 [Note] Server socket created on IP: '0.0.0.0'.
160419 12:11:59 [Note] Event Scheduler: Loaded 0 events
160419 12:11:59 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: ready for connections.
Version: '5.5.48'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
160419 12:38:42 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: Normal shutdown

160419 12:38:42 [Note] Event Scheduler: Purging the queue. 0 events
160419 12:38:42  InnoDB: Starting shutdown...
160419 12:38:43  InnoDB: Shutdown completed; log sequence number 1595675
160419 12:38:43 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: Shutdown complete

160419 12:38:43 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.5.48/data/ebs-20185.pid ended
160419 12:38:44 mysqld_safe Starting mysqld daemon with databases from /www/wdlinux/mysql-5.5.48/data
160419 12:38:44 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160419 12:38:44 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160419 12:38:44 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld (mysqld 5.5.48) starting as process 1438 ...
160419 12:38:44 [Note] Plugin 'FEDERATED' is disabled.
160419 12:38:44 InnoDB: The InnoDB memory heap is disabled
160419 12:38:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160419 12:38:44 InnoDB: Compressed tables use zlib 1.2.3
160419 12:38:44 InnoDB: Initializing buffer pool, size = 128.0M
160419 12:38:44 InnoDB: Completed initialization of buffer pool
160419 12:38:44 InnoDB: highest supported file format is Barracuda.
160419 12:38:44  InnoDB: Waiting for the background threads to start
160419 12:38:45 InnoDB: 5.5.48 started; log sequence number 1595675
160419 12:38:45 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160419 12:38:45 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160419 12:38:45 [Note] Server socket created on IP: '0.0.0.0'.
160419 12:38:45 [Note] Event Scheduler: Loaded 0 events
160419 12:38:45 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: ready for connections.
Version: '5.5.48'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
160419 12:57:42 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: Normal shutdown

160419 12:57:42 [Note] Event Scheduler: Purging the queue. 0 events
160419 12:57:42  InnoDB: Starting shutdown...
160419 12:57:43  InnoDB: Shutdown completed; log sequence number 1595675
160419 12:57:43 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: Shutdown complete

160419 12:57:43 mysqld_safe mysqld from pid file /www/wdlinux/mysql-5.5.48/data/ebs-20185.pid ended



這個上日志文件 的內(nèi)容，是ebs-20185.err文件 ，請問管理，我找的日志文件 是否正確，此日志中有想著錯誤信息嗎？

再次對大神及管理的幫助表示感謝；

參謀帶個長

InnoDB: End of page dump
160713 10:12:57  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
02:12:57 UTC - mysqld got signal 11 ;
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=134217728
read_buffer_size=1048576
max_used_connections=1
max_threads=1000
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2190603 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2f3d660
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 = 7fead45d1e68 thread_stack 0x40000
/www/wdlinux/mysql-5.5.48/bin/mysqld(my_print_stacktrace+0x2e)[0x76392e]
/www/wdlinux/mysql-5.5.48/bin/mysqld(handle_fatal_signal+0x41a)[0x657c9a]
/lib64/libpthread.so.0[0x36b620f7e0]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x8864b5]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x8120b7]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x7d3211]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x7b2f69]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x589ea9]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x71)[0x58ff21]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x5954f7]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_ZN4JOIN4execEv+0xbe9)[0x5a6b99]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x162)[0x5a8202]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x174)[0x5a8c44]
/www/wdlinux/mysql-5.5.48/bin/mysqld[0x56a764]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z21mysql_execute_commandP3THD+0x102f)[0x56eaaf]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x189)[0x571fc9]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x19eb)[0x57410b]
/www/wdlinux/mysql-5.5.48/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x176)[0x601976]
/www/wdlinux/mysql-5.5.48/bin/mysqld(handle_one_connection+0x4a)[0x6019da]
/lib64/libpthread.so.0[0x36b6207aa1]
/lib64/libc.so.6(clone+0x6d)[0x36b5ee893d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7feaa8005920): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED

參謀帶個長

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
160713 10:12:57 mysqld_safe Number of processes running now: 0
160713 10:12:57 mysqld_safe mysqld restarted
160713 10:12:57 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160713 10:12:57 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
160713 10:12:57 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld (mysqld 5.5.48) starting as process 16092 ...
160713 10:12:57 [Note] Plugin 'FEDERATED' is disabled.
160713 10:12:57 InnoDB: The InnoDB memory heap is disabled
160713 10:12:57 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160713 10:12:57 InnoDB: Compressed tables use zlib 1.2.3
160713 10:12:57 InnoDB: Initializing buffer pool, size = 128.0M
160713 10:12:57 InnoDB: Completed initialization of buffer pool
160713 10:12:57 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!
160713 10:12:57  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...
160713 10:12:57  InnoDB: Waiting for the background threads to start
160713 10:12:58 InnoDB: 5.5.48 started; log sequence number 697729617
160713 10:12:58 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160713 10:12:58 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160713 10:12:58 [Note] Server socket created on IP: '0.0.0.0'.
160713 10:12:58 [Note] Event Scheduler: Loaded 0 events
160713 10:12:58 [Note] /www/wdlinux/mysql-5.5.48/bin/mysqld: ready for connections.
Version: '5.5.48'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
160713 10:15:28 [Warning] IP address '211.149.164.233' could not be resolved: Name or service not known

參謀帶個長

InnoDB: Page may be a freshly allocated page
02:12:57 UTC - mysqld got signal 11 ;
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.


這一段出現(xiàn)了1355次，不知道有沒有重要的信息；