MySQL Forums
Forum List  »  Backup

Re: New install with backup from older version
Posted by: Marc Adler
Date: January 20, 2016 09:44AM

To add some mor information. This is what I see in my loghfile, whe I try to start the new mysql with the old data:

----------------------------
2016-01-20 16:33:19 6757 [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.
2016-01-20 16:33:19 6757 [Note] Plugin 'FEDERATED' is disabled.
2016-01-20 16:33:19 6757 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-01-20 16:33:19 6757 [Note] InnoDB: The InnoDB memory heap is disabled
2016-01-20 16:33:19 6757 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-01-20 16:33:19 6757 [Note] InnoDB: Memory barrier is not used
2016-01-20 16:33:19 6757 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-01-20 16:33:19 6757 [Note] InnoDB: Using Linux native AIO
2016-01-20 16:33:19 6757 [Note] InnoDB: Using CPU crc32 instructions
2016-01-20 16:33:19 6757 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-01-20 16:33:19 6757 [Note] InnoDB: Completed initialization of buffer pool
2016-01-20 16:33:19 6757 [Note] InnoDB: Highest supported file format is Barracuda.
2016-01-20 16:33:19 6757 [Note] InnoDB: The log sequence numbers 131218802 and 131218802 in ibdata files do not match the log sequence number 131229533 in the ib_logfiles!
2016-01-20 16:33:19 6757 [Note] InnoDB: Database was not shutdown normally!
2016-01-20 16:33:19 6757 [Note] InnoDB: Starting crash recovery.
2016-01-20 16:33:19 6757 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-01-20 16:33:19 6757 [Note] InnoDB: Restoring possible half-written data pages
2016-01-20 16:33:19 6757 [Note] InnoDB: from the doublewrite buffer...
15:33:20 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=131072
max_used_connections=0
max_threads=151
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 = 76296 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
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
mysqld(my_print_stacktrace+0x3b)[0x8dbb4b]
mysqld(handle_fatal_signal+0x37b)[0x63c7bb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7f08ed19cd10]
mysqld[0xa38edb]
mysqld[0xa39980]
mysqld[0x9aea4b]
mysqld[0x8f3a64]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x57d2e8]
mysqld[0x6d0cb5]
mysqld(_Z11plugin_initPiPPci+0x6c8)[0x6d6e88]
mysqld[0x5746c9]
mysqld(_Z11mysqld_mainiPPc+0x55e)[0x5756ee]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f08ec541a40]
mysqld(_start+0x29)[0x569ea9]
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.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: New install with backup from older version
1206
January 20, 2016 09:44AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.