InnoDB error after 5.5 - 5.6 upgrade on Slave
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
||||
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi,
We are doing a 5.5 mysql to 5.6 Percona server update, Master has completed, as has 2nd slave.
Main slave failed during the "--skip-
I have tried defining the tmpdir, but this appears to make no difference.
error is as follows. Note the replication on both slaves had been stopped prior to the update beginning on the master. A similar group of files were present on the second slave, but after a failed attempt to restart replication, they were removed, and no further errors occured on that server.
Master vr4
primary slave vr11
secondary slave vr9
[root@h77-245-67-66 tmp]# /usr/sbin/mysqld --skip-grant-tables --user=mysql &
[1] 13162
[root@h77-245-67-66 tmp]# 2017-09-25 10:18:04 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_
2017-09-25 10:18:04 0 [Note] /usr/sbin/mysqld (mysqld 5.6.37-82.2-log) starting as process 13162 ...
2017-09-25 10:18:04 13162 [Note] Plugin 'FEDERATED' is disabled.
2017-09-25 10:18:04 13162 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-25 10:18:04 13162 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-25 10:18:04 13162 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-25 10:18:04 13162 [Note] InnoDB: Memory barrier is not used
2017-09-25 10:18:04 13162 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-25 10:18:04 13162 [Note] InnoDB: Using Linux native AIO
2017-09-25 10:18:04 13162 [Note] InnoDB: Using CPU crc32 instructions
2017-09-25 10:18:04 13162 [Note] InnoDB: Initializing buffer pool, size = 24.0G
2017-09-25 10:18:04 13162 [Note] InnoDB: Completed initialization of buffer pool
2017-09-25 10:18:05 13162 [Note] InnoDB: Highest supported file format is Barracuda.
2017-09-25 10:18:05 7fbb539fa7e0 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2017-09-25 10:18:05 13162 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysqltmp/
2017-09-25 10:18:05 13162 [ERROR] InnoDB: Tablespace open failed for '"mysqltmp"
2017-09-25 10:18:05 7fbb539fa7e0 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2017-09-25 10:18:05 13162 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysqltmp/
2017-09-25 10:18:05 13162 [ERROR] InnoDB: Tablespace open failed for '"mysqltmp"
2017-09-25 10:18:05 7fbb539fa7e0 InnoDB: Assertion failure in thread 140442538584032 in file pars0pars.cc line 865
InnoDB: Failing assertion: sym_node->table != NULL
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
09:18:05 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=4098
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
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
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
[1]+ Exit 1 /usr/sbin/mysqld --skip-grant-tables --user=mysql
Do you have any suggestions ? I could either restore this mornings backup and roll forward, create a new set of backup data on the master and replace on the primary slave, but would need to be able to start the DB first.
Thanks,
Mike Shield
Forgot to add, we have added innodb_ force_recovery = 1 to the cnf file, with no obvious effect