Message System ใน directadmin
[TABLE=“class: list, width: 774”]
[TR]
[TD=“bgcolor: #EEEEEE”]000001270[/TD]
[TD=“class: listwrap, bgcolor: #EEEEEE”]The service ‘mysqld’ on server ns1.thsite.net is currently down[/TD]
[/TR]
[/TABLE]
[COLOR=#000000][FONT=verdana]
Error connecting to MySQL: Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2)
start , stop บน directadmin แล้วก็ไม่เกิดอะไรขึ้น ครับ เหมือนเดิม
ลอง remote เข้าไป สั่ง ใน /usr/local/etc/rc.d/mysqld
[/FONT][/COLOR]/usr/local/etc/rc.d
ns1# mysqld start
mysqld: Command not found.
ค้นๆดู ลองทุกวิธี จาก http://help.directadmin.com/item.php?id=332
สุดท้าย เจอ error ตามข้อ 5 ครับ
131202 07:53:11 mysqld restarted
131202 7:53:11 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…
131202 7:53:11 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 19 2247520409.
InnoDB: Doing recovery: scanned up to log sequence number 19 2247520535
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 0 1582488576
131202 7:53:11 InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percents: 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
131202 7:53:12 InnoDB: Started; log sequence number 19 2247520535
InnoDB: Starting in background the rollback of uncommitted transactions
131202 7:53:12 InnoDB: Rolling back trx with id 0 1582488076, 1 rows to undo
InnoDB: Error: trying to access page number 947832219 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131202 7:53:12InnoDB: Assertion failure in thread 163303424 in file fil0fil.c line 3959
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html
InnoDB: about forcing recovery.
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=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
131202 07:53:12 mysqld ended
ขอความช่วยเหลือด้วยครับ
ปล.เหตุเกิด หลังจาก กสทไฟดับ และ ไฟมา เมื่อวานครับ
[COLOR=#000000][FONT=verdana]
[/FONT][/COLOR]
