MySQL Forums
Forum List  »  InnoDB

Mysql crash on startup
Posted by: Stefano Passiatore
Date: October 14, 2019 01:48AM

Hi to all, after a restore process I got a lots of errors like this:

2019-10-14T07:10:57.219430Z 0 [Warning] InnoDB: Ignoring tablespace `vecchiosesto05_0/wysiwyg_user` because it could not be opened.
2019-10-14T07:10:57.219457Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-10-14T07:10:57.219467Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-10-14T07:10:57.219476Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-10-14T07:10:57.219485Z 0 [ERROR] InnoDB: Cannot open datafile for read-only: './vecchiosesto05_0/xmlsitemap.ibd' OS error: 71
2019-10-14T07:10:57.219494Z 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2019-10-14T07:10:57.219503Z 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2019-10-14T07:10:57.219511Z 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2019-10-14T07:10:57.219520Z 0 [ERROR] InnoDB: Could not find a valid tablespace file for `vecchiosesto05_0/xmlsitemap`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.

All the errors refer to old objects and database dropped and no more existing.

At the and of error.log I find this message:

07:10:57 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
# Copyright (c) 2014, 2016, Oracle and/or its affiliates. All rights reserved.
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
# Copyright (c) 2014, 2016, Oracle and/or its affiliates. All rights reserved.
read_buffer_size=131072
max_used_connections=0
max_threads=500
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 = 206883 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f7e94000900
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 = 7f7e9a7fbcb8 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x55a66794081c]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x55a66726b879]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f7ef7a9c0e0]
/usr/sbin/mysqld(_Z28fil_space_is_being_truncatedm+0x88)[0x55a667bbe2b8]
/usr/sbin/mysqld(_Z14row_purge_stepP9que_thr_t+0x382)[0x55a667a7afc2]
/usr/sbin/mysqld(_Z15que_run_threadsP9que_thr_t+0xa55)[0x55a667a2aa95]
/usr/sbin/mysqld(_Z9trx_purgemmb+0xa54)[0x55a667ad87d4]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xac5)[0x55a667aafee5]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f7ef7a924a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f7ef62ded0f]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0

How to clean the server from dropped objects and restart it? Now it's impossibile start the server...
Thanks

Options: ReplyQuote


Subject
Views
Written By
Posted
Mysql crash on startup
79
October 14, 2019 01:48AM
30
October 15, 2019 10:48AM


Sorry, only registered users may post in this forum.

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.