Hi,
We are in the process of a 5.5 to 5.6 upgrade, and after successfully updating the master, I had updated the first slave, and attempted to do the restart with the “–skip-grant-tables” option as per the upgrade guide.
There are 4 files in /home/mysqltmp, which the startup appears to have an issue with, and I’m currently unable to get the server to come up.
Even with an explicit definition of tmdir, the command fails as follows.
[root@h77-245-67-66 tmp]# /usr/sbin/mysqld --skip-grant-tables --user=mysql &
2017-09-25 09:30:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-09-25 09:30:16 0 [Note] /usr/sbin/mysqld (mysqld 5.6.37-82.2-log) starting as process 9158 …
2017-09-25 09:30:16 9158 [Note] Plugin ‘FEDERATED’ is disabled.
2017-09-25 09:30:16 9158 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-09-25 09:30:16 9158 [Note] InnoDB: The InnoDB memory heap is disabled
2017-09-25 09:30:16 9158 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-25 09:30:16 9158 [Note] InnoDB: Memory barrier is not used
2017-09-25 09:30:16 9158 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-09-25 09:30:16 9158 [Note] InnoDB: Using Linux native AIO
2017-09-25 09:30:16 9158 [Note] InnoDB: Using CPU crc32 instructions
2017-09-25 09:30:16 9158 [Note] InnoDB: Initializing buffer pool, size = 24.0G
2017-09-25 09:30:16 9158 [Note] InnoDB: Completed initialization of buffer pool
2017-09-25 09:30:16 9158 [Note] InnoDB: Highest supported file format is Barracuda.
2017-09-25 09:30:17 7f7f1fa2a7e0 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 09:30:17 9158 [ERROR] InnoDB: Could not find a valid tablespace file for ‘mysqltmp/#sqld17_dd9ab8_6592’. See [url]http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html[/url] for how to resolve the issue.
2017-09-25 09:30:17 9158 [ERROR] InnoDB: Tablespace open failed for ‘“mysqltmp”.“#sqld17_dd9ab8_6592”’, ignored.
2017-09-25 09:30:17 7f7f1fa2a7e0 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 09:30:17 9158 [ERROR] InnoDB: Could not find a valid tablespace file for ‘mysqltmp/#sqld17_dd9ab8_6593’. See [url]http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html[/url] for how to resolve the issue.
2017-09-25 09:30:17 9158 [ERROR] InnoDB: Tablespace open failed for ‘“mysqltmp”.“#sqld17_dd9ab8_6593”’, ignored.
2017-09-25 09:30:17 7f7f1fa2a7e0 InnoDB: Assertion failure in thread 140183968327648 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://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: [url]http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html[/url]
InnoDB: about forcing recovery.
08:30:17 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 [url]System Dashboard - Percona JIRA
key_buffer_size=67108864
read_buffer_size=4194304
max_used_connections=0
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_size)*max_threads = 33693261 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
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8da27c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x65b061]
/lib64/libpthread.so.0[0x3e9b40f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x3e9ac325e5]
/lib64/libc.so.6(abort+0x175)[0x3e9ac33dc5]
/usr/sbin/mysqld[0x9b4669]
/usr/sbin/mysqld(_Z7yyparsev+0xe1b)[0xaf722b]
/usr/sbin/mysqld[0x9b5f71]
/usr/sbin/mysqld[0x9b9f56]
/usr/sbin/mysqld[0x9e121c]
/usr/sbin/mysqld[0x9e333d]
/usr/sbin/mysqld[0x98e23e]
/usr/sbin/mysqld[0xa0b543]
/usr/sbin/mysqld[0x94767c]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x59bc58]
/usr/sbin/mysqld[0x6e9ee1]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x982)[0x6f04b2]
/usr/sbin/mysqld[0x5944fd]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x40d)[0x59557d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x3e9ac1ed1d]
/usr/sbin/mysqld[0x586e8d]
You may download the Percona Server operations manual by visiting
[url]http://www.percona.com/software/percona-server/[/url]. You may find information
in the manual which will help you identify the cause of the crash.
[1]+ Exit 1 /usr/sbin/mysqld --skip-grant-tables --user=mysql
Any suggestions, we’ve run out of ideas.
Mike