danke erstmal
wie könnte ich denn raus bekommen was an der DB kaputt ist?
hier mal teile vom error log wenn ich den dump machen will:
root@frodo /usr/local/pd-admin2/var/mysql # tailf frodo.err
151110 16:09:08 mysqld_safe mysqld restarted
151110 16:09:08 InnoDB: Initializing buffer pool, size = 8.0M
151110 16:09:08 InnoDB: Completed initialization of buffer pool
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
151110 16:09:09 InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
151110 16:09:09 [Note] Event Scheduler: Loaded 0 events
151110 16:09:09 [Note] /usr/local/pd-admin2/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/usr/local/pd-admin2/var/mysql.run/mysql.sock' port: 3306 Source distribution
151110 17:24:58 InnoDB: error: space object of table roundcubemail/cache,
InnoDB: space id 4 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/contactgroupmembers,
InnoDB: space id 7 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/contactgroups,
InnoDB: space id 6 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/contacts,
InnoDB: space id 5 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/identities,
InnoDB: space id 8 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/messages,
InnoDB: space id 3 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/session,
InnoDB: space id 1 did not exist in memory. Retrying an open.
151110 17:24:58 InnoDB: error: space object of table roundcubemail/users,
InnoDB: space id 2 did not exist in memory. Retrying an open.
InnoDB: Page directory corruption: infimum not pointed to
151110 17:24:59 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex f7493e2c000000330000000000000000000000002d3ce321000200000000000000000000000000022cda3369ffffffff0000ffffffff000000042c2000000000000000c702720000000100000033002c00000033002c000000000016fd82000000000016fd83000001100000000000000000000006fb000000000033071dffffffff0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006fb1c000d00000016fd800000322e9d203564313338336639383635303735333238396464343864343633363231363930010685b4624746755a3356685a325638637a6f314f694a6b5a5639455253493763327470626e787a4f6a5536496d7868636e4a35496a747062574677583235686257567a6347466a5a5878684f6a513665334d364f446f696347567963323975595777694f3245364d54703761546f774f3245364d6a703761546f774f334d364e6a6f695355354354316775496a74704f6a4537637a6f784f694975496a743966584d364e546f696233526f5a5849694f303437637a6f324f694a7a614746795a5751694f3245364d6a703761546f774f3245364d6a703761546f774f334d364f446f6949334e6f59584a6c5a4334694f326b364d54747a4f6a4536496934694f3331704f6a453759546f794f6e74704f6a4137637a6f334f694a7a614746795a575175496a74704f6a4537637a6f784f694975496a743966584d364e6a6f6963484a6c5a6d6c34496a747a4f6a5936496b6c4f516b39594c69493766576c74595842665a475673615731706447567966484d364d546f694c69493764584e6c636c39705a48787a4f6a4936496a4577496a743163325679626d46745a58787a4f6a6736496e4e6f59584a685a6d6c68496a747a644739795957646c5832687663335238637a6f354f694a7362324e6862476876633351694f334e3062334a685a32566663473979644878704f6a45304d7a747a644739795957646c58334e7a6248784f4f33426863334e3362334a6b66484d364d7a4936496d316964327452576b5642646e52785a6e525452304d3553317054566e6848613364314d55356f4
... ganz viel mehr davon
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043c22e622d3ce321; asc I>, 3 -< ! , 3i , r 3 , 3 , 3 2. 5d1383f98650753289dd48d463621690 bGFuZ3VhZ2V8czo1OiJkZV9ERSI7c2tpbnxzOjU6ImxhcnJ5IjtpbWFwX25hbWVzcGFjZXxhOjQ6e3M6ODoicGVyc29uYWwiO2E6MTp7aTowO2E6Mjp7aTowO3M6NjoiSU5CT1guIjtpOj
... nochmal ganz viel mehr
C .b-< !;InnoDB: End of page dump
151110 17:24:59 InnoDB: Page checksum 4148772396, prior-to-4.0.14-form checksum 1136799330
InnoDB: stored checksum 4148772396, prior-to-4.0.14-form stored checksum 1136799330
InnoDB: Page lsn 0 758965025, low 4 bytes of lsn at page end 758965025
InnoDB: Page number (if stored to page already) 51,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
InnoDB: Page directory corruption: supremum not pointed to
151110 17:24:59 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex f7493e2c000000330000000000000000000000002d3ce321000200000000000000000000000000022cda3369ffffffff0000ffffffff000000042c2000000000000000c702720000000100000033002c00000033002c000000000016fd82000000000016fd83000001100000000000000000000006fb000000000033071dffffffff000000000000000000000000000000000000000000000
....mehr²
C .b-< !;InnoDB: End of page dump
151110 17:24:59 InnoDB: Page checksum 4148772396, prior-to-4.0.14-form checksum 1136799330
InnoDB: stored checksum 4148772396, prior-to-4.0.14-form stored checksum 1136799330
InnoDB: Page lsn 0 758965025, low 4 bytes of lsn at page end 758965025
InnoDB: Page number (if stored to page already) 51,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
16:24:59 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=16777216
read_buffer_size=262144
max_used_connections=3
max_threads=151
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 = 133350 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0xa1bcf88
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 = fffffffff17ae394 thread_stack 0x30000
/usr/local/pd-admin2/libexec/mysqld(my_print_stacktrace+0x23)[0x846eee3]
/usr/local/pd-admin2/libexec/mysqld(handle_fatal_signal+0x2b5)[0x829e255]
[0xf7787400]
/usr/local/pd-admin2/libexec/mysqld(page_cur_search_with_match+0xb3c)[0x83b208c]
/usr/local/pd-admin2/libexec/mysqld(btr_cur_search_to_nth_level+0xa64)[0x8336f44]
/usr/local/pd-admin2/libexec/mysqld(btr_pcur_open_on_user_rec+0x48)[0x8412ae8]
/usr/local/pd-admin2/libexec/mysqld(dict_load_table+0x2a5)[0x8365505]
/usr/local/pd-admin2/libexec/mysqld(dict_table_get+0x11a)[0x8359b3a]
/usr/local/pd-admin2/libexec/mysqld(open__11ha_innobasePCciUi+0x137)[0x832ca47]
/usr/local/pd-admin2/libexec/mysqld(ha_open__7handlerP8st_tablePCcii+0x2d)[0x829800d]
/usr/local/pd-admin2/libexec/mysqld(open_table_from_share__FP3THDP14st_table_sharePCcUiUiUiP8st_tableb+0x49e)[0x821162e]
/usr/local/pd-admin2/libexec/mysqld[0x8207780]
/usr/local/pd-admin2/libexec/mysqld(open_table__FP3THDP10TABLE_LISTP11st_mem_rootPbUi+0x918)[0x82064e8]
/usr/local/pd-admin2/libexec/mysqld(open_tables__FP3THDPP10TABLE_LISTPUiUi+0x20c)[0x8207c7c]
/usr/local/pd-admin2/libexec/mysqld(open_normal_and_derived_tables__FP3THDP10TABLE_LISTUi+0x1c)[0x820e29c]
/usr/local/pd-admin2/libexec/mysqld[0x82bd408]
/usr/local/pd-admin2/libexec/mysqld(get_all_tables__FP3THDP10TABLE_LISTP4Item+0x603)[0x82bdf23]
/usr/local/pd-admin2/libexec/mysqld(get_schema_tables_result__FP4JOIN23enum_schema_table_state+0x1ae)[0x82c560e]
/usr/local/pd-admin2/libexec/mysqld(exec__4JOIN+0x410)[0x8219870]
/usr/local/pd-admin2/libexec/mysqld(mysql_select__FP3THDPPP4ItemP10TABLE_LISTUiRt4List1Z4ItemP4ItemUiP8st_orderT7T5T7UxP13select_resultP18st_select_lex_unitP13st_select_lex+0x3e7)[0x821b147]
/usr/local/pd-admin2/libexec/mysqld(handle_select__FP3THDP6st_lexP13select_resultUl+0x10c)[0x82167cc]
/usr/local/pd-admin2/libexec/mysqld[0x81d1fc3]
/usr/local/pd-admin2/libexec/mysqld(mysql_execute_command__FP3THD+0x679)[0x81ca629]
/usr/local/pd-admin2/libexec/mysqld(mysql_parse__FP3THDPcUiPPCc+0x1b5)[0x81d3165]
/usr/local/pd-admin2/libexec/mysqld(dispatch_command__F19enum_server_commandP3THDPcUi+0x998)[0x81c8828]
/usr/local/pd-admin2/libexec/mysqld(do_command__FP3THD+0x11e)[0x81c7d7e]
/usr/local/pd-admin2/libexec/mysqld(handle_one_connection+0x1d9)[0x81c69d9]
/lib32/libpthread.so.0(+0x5c39)[0xf7767c39]
/lib32/libc.so.6(clone+0x5e)[0xf73f0dde]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (a274730): show table status like 'wp\_wplc\_chat\_msgs'
Connection ID (thread ID): 217
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.
151110 17:24:59 mysqld_safe Number of processes running now: 0
151110 17:24:59 mysqld_safe mysqld restarted
151110 17:24:59 InnoDB: Initializing buffer pool, size = 8.0M
151110 17:24:59 InnoDB: Completed initialization of buffer pool
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
151110 17:24:59 InnoDB: Started; log sequence number 0 0
InnoDB: !!! innodb_force_recovery is set to 6 !!!
151110 17:24:59 [Note] Event Scheduler: Loaded 0 events
151110 17:24:59 [Note] /usr/local/pd-admin2/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/usr/local/pd-admin2/var/mysql.run/mysql.sock' port: 3306 Source distribution
Alles anzeigen
ist echt blöd wenn man selber keine ahnung hat
update: habe jetzt einfach auf dem neuen server die databases gedroppt und konnte dann über phpmyadmin das gedöns importieren, dabei habe ich die fehlerhafte database gefunden, es ist unsere eigne von wordpress... klicke ich die auf dem alten server an kommt: #2013 - Lost connection to MySQL server during query
interessant ist das sie auf dem neuen server auch vorhanden ist und kein fehler auftaucht, da aber beim importieren ein fehler kam, gehe ich davon aus das nicht alles importiert wurde
mfg