[MDEV-14915] Attempted to upgrade from 5.5.52 to 10.2.12 Created: 2018-01-10 Updated: 2018-12-29 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Michael Hudacko | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux 2.6.32-696.13.2.el6.x86_64 #1 SMP Fri Sep 22 12:32:14 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Description |
|
Instance restart - after running mysql_upgrade script - produced following crash error. 2018-01-10 12:19:24 0x7f35c80c8700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/que/que0que.cc line 567 To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help Server version: 10.2.12-MariaDB-log Thread pointer: 0x0 |
| Comments |
| Comment by Elena Stepanova [ 2018-01-10 ] |
|
Could you please paste a bigger portion of the error log, last session of 5.5 and up to and including the first occurrence of the failure on 10.2? Thanks. |
| Comment by Michael Hudacko [ 2018-01-10 ] |
|
NOTE: after the restart that produced the crash, I removed the configuration parameter [innodb_file_format = 'Barracuda']. And restarted instance. |
| Comment by Elena Stepanova [ 2018-01-10 ] |
|
MichaelTHudacko, thanks. However, the attached log still starts from a crash on 10.2. Can we see the last shutdown on 5.5 and the first startup on 10.2, and everything else until the crash has happened? Thanks. |
| Comment by Michael Hudacko [ 2018-01-10 ] |
|
Attached as much "err" log as I have avail (ibsqldeva02.err.5.5.x) from previous runing instance. (this server is very inactive from a usage standpoint). It is also one node of a master-master replication set-up. This is inactive node #2 (10.2.12) with its master active node #1 (5.5.52). Since starting this thread it crashed another time and will provide another full error log. |
| Comment by Michael Hudacko [ 2018-01-10 ] |
|
Hi Elena, Don't wish to waste your time on this.I'm beginning to think that this issue may be related to master-master replication set-up and initiating a mysql_upgrade with the target server slave started. I reviewed my notes from a previous upgrade and now see that before starting the instance (for upgrade) at that time put skip-slave-start in the my.cnf file. Since your last update, I upgraded a totally different server without replication configured and experienced none of what I initially reported. I'm performing some tests on this server now, |
| Comment by Michael Hudacko [ 2018-04-05 ] |
|
What type of feed back is desired here? Thanks! |