Unable to restore/initialize server getting "mysqld got signal 6 ;"

Hi everyone,
I keep on getting a mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

I got this when I was trying to restore a backup on our standby.
I used 2 different backups and both got the same error.

Now I am trying to initialize and just create a new server.
When i do the initialize i get the exact same error.

I am guessing this is not a bug but something with our hardware. The server was upgrade to Oracle linux 8 from centos 7.

What steps can I do to troubleshoot with our sysadmin?
thanks.

2024-06-24T11:21:10.088706-04:00 0 [Warning] [MY-011070] [Server] ‘Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it’ is deprecated and will be removed in a future release.
2024-06-24T11:21:10.088810-04:00 0 [Warning] [MY-010084] [Server] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --slow-query-log is not set
2024-06-24T11:21:10.088838-04:00 0 [Warning] [MY-010915] [Server] ‘NO_ZERO_DATE’, ‘NO_ZERO_IN_DATE’ and ‘ERROR_FOR_DIVISION_BY_ZERO’ sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-06-24T11:21:10.089021-04:00 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.21-12) initializing of server in progress as process 77049
2024-06-24T11:21:10.183220-04:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
15:21:10 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

Build ID: Not Available
Server Version: 8.0.21-12 Percona Server (GPL), Release 12, Revision 7ddfdfe

Thread pointer: 0x4608130
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 = 7f27c42fbd20 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x2018061]
/usr/sbin/mysqld(handle_fatal_signal+0x3c3) [0x12458c3]
/lib64/libpthread.so.0(+0x12d80) [0x7f27f711dd80]
/lib64/libc.so.6(gsignal+0x10f) [0x7f27f50005ef]
/lib64/libc.so.6(abort+0x127) [0x7f27f4fd3e65]
/usr/sbin/mysqld(file_info::RegisterFilename(int, char const*, file_info::OpenType)+0x1fd) [0x201070d]
/usr/sbin/mysqld(create_temp_file(char*, char const*, char const*, int, UnlinkOrKeepFile, int)+0x26c) [0x200d8cc]
/usr/sbin/mysqld(mysql_tmpfile_path(char const*, char const*)+0xe0) [0x11b0e60]
/usr/sbin/mysqld(innobase_mysql_tmpfile(char const*)+0x8c) [0x20e477c]
/usr/sbin/mysqld(os_file_create_tmpfile(char const*)+0x28) [0x21dda18]
/usr/sbin/mysqld(srv_start(bool)+0x1052) [0x22bfda2]
/usr/sbin/mysqld() [0x2111a67]
/usr/sbin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xa6) [0x1dcd1e6]
/usr/sbin/mysqld(dd::bootstrap::initialize(THD*)+0x8d) [0x1dcdbcd]
/usr/sbin/mysqld() [0x13059f8]
/usr/sbin/mysqld() [0x252d768]
/lib64/libpthread.so.0(+0x81da) [0x7f27f71131da]
/lib64/libc.so.6(clone+0x43) [0x7f27f4feb8d3]

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

Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

You may download the Percona Server operations manual by visiting
Percona Server for MySQL - Open Source MySQL Server Alternative. You may find information
in the manual which will help you identify the cause of the crash.

Hi @ipcmlr ,

This stack trace was related to a temporary file creation:

/usr/sbin/mysqld(create_temp_file(char*, char const*, char const*, int, UnlinkOrKeepFile, int)+0x26c) [0x200d8cc]
/usr/sbin/mysqld(mysql_tmpfile_path(char const*, char const*)+0xe0) [0x11b0e60]
/usr/sbin/mysqld(innobase_mysql_tmpfile(char const*)+0x8c) [0x20e477c]
/usr/sbin/mysqld(os_file_create_tmpfile(char const*)+0x28) [0x21dda18]

So, I would suggest you start by checking temp file configurations, free space in the tmp folder, right privileges, etc.
Also, you can check dmesg to find anything strange.
Let us know how it goes.

thanks.
this pointed me in the right direction.
my tmpdir is under the data dir which means i delete it when i need to restore the xtrabackup backup.
i needed to manually create the tmpdir after the restore.

1 Like