Всем привет!
[QUOTE]
Mikhail Kryachek написал:
1. Покажите нам результаты выполнения df -h[/QUOTE]
[root@portal mail]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 147G 2.6G 137G 2% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/sda1 190M 43M 138M 24% /boot
/dev/sdb1 197G 15G 172G 8% /home
[QUOTE]
Mikhail Kryachek написал:
free -m[/QUOTE]
[root@portal ~]# free -m
total used free shared buffers cached
Mem: 3925 970 2954 11 502 223
-/+ buffers/cache: 244 3681
Swap: 511 0 511
[QUOTE]
Mikhail Kryachek написал:
2. Предоставьте более подробные логи относящиеся к проблеме[/QUOTE]
Я прочитала, как следить за логом в реальном времени. Запустила слежение, потом команду service mysqld start, и получила следующий полный текст:
(дополнение: в файле messages сообщения не обновляются при попытке запустить БД)
------------------------------------------------------------------------------------------------
171211 11:34:25 mysqld_safe Starting mysqld daemon with databases fr om /var/lib/mysql
171211 11:34:25 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
171211 11:34:25 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
171211 11:34:25 [Note] Plugin 'FEDERATED' is disabled.
171211 11:34:25 InnoDB: The InnoDB memory heap is disabled
171211 11:34:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171211 11:34:25 InnoDB: Compressed tables use zlib 1.2.3
171211 11:34:25 InnoDB: Using Linux native AIO
171211 11:34:25 InnoDB: Initializing buffer pool, size = 756.0M
171211 11:34:25 InnoDB: Completed initialization of buffer pool
171211 11:34:25 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 13195165898
171211 11:34:25 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...
InnoDB: Doing recovery: scanned up to log sequence number 13195181479
171211 11:34:25 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 18 19 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 171211 11:34:25 InnoDB: Assertion failure in thread 1995471728 in file trx0undo.c line 561
InnoDB: Failing assertion: free + TRX_UNDO_LOG_XA_HDR_SIZE < UNIV_PAGE_SIZE - 100
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to [URL=http://bugs.mysql.com]http://bugs.mysql.com[/URL].
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: [URL=http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html]http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html[/URL]
InnoDB: about forcing recovery.
08:34:25 UTC - mysqld got signal 6 ;
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=67108864
read_buffer_size=131072
max_used_connections=0
max_threads=20
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 = 232083 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
wh ere mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x20000
/usr/libexec/mysqld(my_print_stacktrace+0x34)[0x83efa34]
/usr/libexec/mysqld(handle_fatal_signal+0x48c)[0x82bd89c]
[0xf23400]
[0xf23424]
/lib/libc.so.6(gsignal+0x51)[0xafc871]
/lib/libc.so.6(abort+0x17a)[0xafe14a]
/usr/libexec/mysqld[0x8451069]
/usr/libexec/mysqld[0x8451603]
72 73 74 75 /usr/libexec/mysqld[0x84d9b2a]
/usr/libexec/mysqld[0x84db1d5]
76 /usr/libexec/mysqld[0x847825d]
77 /usr/libexec/mysqld[0x84a35dd]
78 /usr/libexec/mysqld[0x8432d10]
/lib/libpthread.so.0(+0x6b39)[0x62fb39]
/lib/libc.so.6(clone+0x5e)[0xbb4c2e]
The manual page at [URL=http://dev.mysql.com/doc/mysql/en/crashing.html]http://dev.mysql.com/doc/mysql/en/crashing.html[/URL] contains
information that should help you find out what is causing the crash.
171211 11:34:25 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
------------------------------------------------------------------------------------------------
На binlog вроде намеков нет, поэтому применять последнюю команду не стала.