krasn0ff
Newbie | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Друзья, ещё один препон. Поднял сайт, всё отлично работало, но после попытки добавить lampp в автозагрузку (к слову, успешной), после нескольких проверочных ребутов перестал стартовать MySQL:
XAMPP: Starting MySQL...
XAMPP: Couldn't start MySQL!
В /opt/lampp/var/mysql есть лог debian.err фрагмент которого я привожу:
100819 10:30:51 mysqld_safe Starting mysqld daemon with databases from /opt/lampp/var/mysql
100819 10:30:51 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use
'--skip-external-locking' instead.
100819 10:30:51 [Note] Plugin 'FEDERATED' is disabled.
100819 10:30:52 InnoDB: Started; log sequence number 0 44263
100819 10:30:52 [Note] PrimeBase XT (PBXT) Engine 1.0.11-6 Pre-GA loaded...
100819 10:30:52 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
100819 10:30:52 [Note] The server was not shutdown correctly, recovery required
100819 10:30:52 [Note] Recovering after a crash using tc.log
100819 10:30:52 - 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=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133316 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 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 = (nil) thread_stack 0x30000
/opt/lampp/sbin/mysqld(my_print_stacktrace+0x26)[0x847e346]
/opt/lampp/sbin/mysqld(handle_segfault+0x3ff)[0x81c93df]
[0xb770c400]
/opt/lampp/sbin/mysqld(_ZN11TC_LOG_MMAP4openEPKc+0x289)[0x826d669]
/opt/lampp/sbin/mysqld[0x81ce775]
/opt/lampp/sbin/mysqld(main+0x1d5)[0x81c9b55]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7371455]
/opt/lampp/sbin/mysqld[0x8112801]
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.
100819 10:30:52 mysqld_safe mysqld from pid file /opt/lampp/var/mysql/debian.pid ended
Дальше всё то же самое по кругу... Что может являться причиной ошибки? Как восстановить работу сборки не повредив базу сайта? Спасибо! |
