|
MySQL.RU - Webboard
 Вернуться
 Не стартует mysql (zapadlowsky) 28/02/2012 - 05:35:23
 Re: Не стартует mysql (Oleg) 28/02/2012 - 11:27:43
Re: Не стартует mysql (Alexander Wiedergold) 04/03/2012 - 05:49:33
From: zapadlowsky - 28/02/2012 - 05:35:23
Subject:Не стартует mysql
-----------------
Со вчерашнего дня не стартует mysqld, в еррор-логах пишет такое
120228 7:13:19 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Log scan progressed past the checkpoint lsn 0 932411373
120228 7:13:19 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 0 932411561
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 71 row operations to undo
InnoDB: Trx id counter is 0 19188992
120228 7:13:19 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 120228 7:13:19 InnoDB: Assertion failure in thread 139878
453847808 in file ../../../storage/innobase/trx/trx0undo.c line 522
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 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/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
120228 7:13:19 - 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=16777216
read_buffer_size=131072
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 = 346495 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
mysqld(my_print_stacktrace+0x29) [0x7f38039f81a9]
mysqld(handle_segfault+0x404) [0x7f3803705884]
/lib/libpthread.so.0(+0xf8f0) [0x7f3802f768f0]
/lib/libc.so.6(gsignal+0x35) [0x7f38019f0a75]
/lib/libc.so.6(abort+0x180) [0x7f38019f45c0]
mysqld(+0x5d14ad) [0x7f38039774ad]
mysqld(trx_undo_parse_page_header+0x8c) [0x7f380397753c]
mysqld(+0x5701cb) [0x7f38039161cb]
mysqld(recv_recover_page+0x4af) [0x7f380391a84f]
mysqld(buf_page_io_complete+0x468) [0x7f38038d2d08]
mysqld(fil_aio_wait+0x11b) [0x7f38038eda1b]
mysqld(+0x5b8200) [0x7f380395e200]
/lib/libpthread.so.0(+0x69ca) [0x7f3802f6d9ca]
/lib/libc.so.6(clone+0x6d) [0x7f3801aa370d]
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.
upd.
dmesg:
[ 2071.890795] mandb[7561]: segfault at 1f0e000 ip 00007ff2595f6252 sp 00007fffff088728 error 4 in libc-2.11.1.so[7ff259571000+17a000]
[ 2089.930975] type=1505 audit(1330391225.254:89): operation="profile_replace" pid=12310 name="/usr/sbin/mysqld"
[ 2120.070892] type=1505 audit(1330391255.394:90): operation="profile_replace" pid=12385 name="/usr/sbin/mysqld"
[ 2150.212680] type=1505 audit(1330391285.534:91): operation="profile_replace" pid=12652 name="/usr/sbin/mysqld"
[ 2180.357841] type=1505 audit(1330391315.674:92): operation="profile_replace" pid=12742 name="/usr/sbin/mysqld"
[ 2210.499825] type=1505 audit(1330391345.815:93): operation="profile_replace" pid=12825 name="/usr/sbin/mysqld"
[ 2240.643056] type=1505 audit(1330391375.964:94): operation="profile_replace" pid=12904 name="/usr/sbin/mysqld"
[ 2270.785763] type=1505 audit(1330391406.104:95): operation="profile_replace" pid=12979 name="/usr/sbin/mysqld"
[ 2300.928010] type=1505 audit(1330391436.244:96): operation="profile_replace" pid=13081 name="/usr/sbin/mysqld"
[Это сообщение - спам!]
Последние сообщения из форума
Уважаемые посетители форума MySQL.RU!
Убедительная просьба, прежде чем задавать свой вопрос в этом форуме, обратите внимание на разделы:
- ответы на наиболее часто задаваемые вопросы - FAQ
- раздел документация
- раздел поиск по сообщениям форума и документации
Также, старайтесь наиболее подробно указывать свою ситуацию (версию операционной системы, версию MySQL,
версию программного обеспечения, по которому возникает вопрос, текст возникающих ошибок, и др.)
Помните, чем конкретнее Вы опишете ситуацию, тем больше шансов получить реальную помощь.
41062
|
|
