JustPaste.it

Syserr

200926 13:48:02 mysqld_safe mysqld from pid file /var/db/mysql/freebsd.pid ended
200926 13:48:37 mysqld_safe Logging to '/var/db/mysql/freebsd-12-1.err'.
200926 13:48:37 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2020-09-26 13:48:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:38 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 860 ...
2020-09-26 13:48:38 860 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:38 860 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:38 860 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:38 860 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:38 860 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:38 860 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:38 860 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:38 860 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:38 860 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:38 860 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2020-09-26 13:48:38 860 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2020-09-26 13:48:38 860 [Note] InnoDB: Database physically writes the file full: wait...
2020-09-26 13:48:38 860 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2020-09-26 13:48:38 860 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2020-09-26 13:48:39 860 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2020-09-26 13:48:39 860 [Warning] InnoDB: New log files created, LSN=45781
2020-09-26 13:48:39 860 [Note] InnoDB: Doublewrite buffer not found: creating new
2020-09-26 13:48:39 860 [Note] InnoDB: Doublewrite buffer created
2020-09-26 13:48:39 860 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:39 860 [Warning] InnoDB: Creating foreign key constraint system tables.
2020-09-26 13:48:39 860 [Note] InnoDB: Foreign key constraint system tables created
2020-09-26 13:48:39 860 [Note] InnoDB: Creating tablespace and datafile system tables.
2020-09-26 13:48:39 860 [Note] InnoDB: Tablespace and datafile system tables created.
2020-09-26 13:48:39 860 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:39 860 [Note] InnoDB: 5.6.49 started; log sequence number 0
 /usr/local/libexec/mysqld: Error on delete of './auto.cnf' (Errcode: 2 - No such file or directory)
2020-09-26 13:48:39 860 [Warning] World-writable config file './auto.cnf' has been removed.

2020-09-26 13:48:39 860 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: fb90f197-fffe-11ea-ad7f-42010a800005.
2020-09-26 13:48:39 860 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:39 860 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:39 860 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:39 860 [Note] IPv6 is available.
2020-09-26 13:48:39 860 [Note]   - '::' resolves to '::';
2020-09-26 13:48:39 860 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:39 860 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:39 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:39 mysqld_safe mysqld restarted
2020-09-26 13:48:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:40 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 872 ...
2020-09-26 13:48:40 872 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:40 872 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:40 872 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:40 872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:40 872 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:40 872 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:40 872 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:40 872 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:40 872 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:40 872 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:40 872 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:40 872 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:40 872 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:40 872 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:40 872 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:40 872 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:40 872 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:41 872 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:41 872 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:41 872 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:41 872 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:41 872 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:41 872 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:41 872 [Note] IPv6 is available.
2020-09-26 13:48:41 872 [Note]   - '::' resolves to '::';
2020-09-26 13:48:41 872 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:41 872 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:41 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:41 mysqld_safe mysqld restarted
2020-09-26 13:48:41 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:41 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 884 ...
2020-09-26 13:48:41 884 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:41 884 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:41 884 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:41 884 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:41 884 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:41 884 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:41 884 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:41 884 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:41 884 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:41 884 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:41 884 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:41 884 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:41 884 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:41 884 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:41 884 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:41 884 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:41 884 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:42 884 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:42 884 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:42 884 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:42 884 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:42 884 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:42 884 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:42 884 [Note] IPv6 is available.
2020-09-26 13:48:42 884 [Note]   - '::' resolves to '::';
2020-09-26 13:48:42 884 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:42 884 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:42 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:42 mysqld_safe mysqld restarted
2020-09-26 13:48:42 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:42 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 895 ...
2020-09-26 13:48:42 895 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:42 895 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:42 895 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:42 895 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:42 895 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:42 895 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:42 895 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:42 895 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:42 895 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:42 895 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:42 895 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:42 895 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:42 895 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:42 895 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:42 895 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:42 895 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:42 895 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:43 895 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:43 895 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:43 895 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:43 895 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:43 895 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:43 895 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:43 895 [Note] IPv6 is available.
2020-09-26 13:48:43 895 [Note]   - '::' resolves to '::';
2020-09-26 13:48:43 895 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:43 895 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:43 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:43 mysqld_safe mysqld restarted
2020-09-26 13:48:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:43 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 906 ...
2020-09-26 13:48:43 906 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:43 906 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:43 906 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:43 906 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:43 906 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:43 906 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:43 906 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:43 906 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:43 906 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:43 906 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:43 906 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:43 906 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:43 906 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:43 906 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:43 906 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:43 906 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:43 906 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:44 906 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:44 906 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:44 906 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:44 906 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:44 906 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:44 906 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:44 906 [Note] IPv6 is available.
2020-09-26 13:48:44 906 [Note]   - '::' resolves to '::';
2020-09-26 13:48:44 906 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:44 906 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:44 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:44 mysqld_safe mysqld restarted
2020-09-26 13:48:45 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:45 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 917 ...
2020-09-26 13:48:45 917 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:45 917 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:45 917 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:45 917 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:45 917 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:45 917 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:45 917 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:45 917 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:45 917 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:45 917 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:45 917 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:45 917 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:45 917 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:45 917 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:45 917 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:45 917 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:45 917 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:45 917 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:45 917 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:46 917 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:46 917 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:46 917 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:46 917 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:46 917 [Note] IPv6 is available.
2020-09-26 13:48:46 917 [Note]   - '::' resolves to '::';
2020-09-26 13:48:46 917 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:46 917 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:46 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:46 mysqld_safe mysqld restarted
2020-09-26 13:48:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:46 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 928 ...
2020-09-26 13:48:46 928 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:46 928 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:46 928 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:46 928 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:46 928 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:46 928 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:46 928 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:46 928 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:46 928 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:46 928 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:46 928 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:46 928 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:46 928 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:46 928 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:46 928 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:46 928 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:46 928 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:47 928 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:47 928 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:47 928 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:47 928 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:47 928 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:47 928 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:47 928 [Note] IPv6 is available.
2020-09-26 13:48:47 928 [Note]   - '::' resolves to '::';
2020-09-26 13:48:47 928 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:47 928 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:47 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:47 mysqld_safe mysqld restarted
2020-09-26 13:48:47 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:47 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 956 ...
2020-09-26 13:48:47 956 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:47 956 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:47 956 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:47 956 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:47 956 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:47 956 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:47 956 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:47 956 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:47 956 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:47 956 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:47 956 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:47 956 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:47 956 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:47 956 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:47 956 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:47 956 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:47 956 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:48 956 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:48 956 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:48 956 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:48 956 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:48 956 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:48 956 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:48 956 [Note] IPv6 is available.
2020-09-26 13:48:48 956 [Note]   - '::' resolves to '::';
2020-09-26 13:48:48 956 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:48 956 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:48 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:48 mysqld_safe mysqld restarted
2020-09-26 13:48:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:48 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 967 ...
2020-09-26 13:48:48 967 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:48 967 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:48 967 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:48 967 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:48 967 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:48 967 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:48 967 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:48 967 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:48 967 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:48 967 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:48 967 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:48 967 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:48 967 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:48 967 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:48 967 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:48 967 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:48 967 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:49 967 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:49 967 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:49 967 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:49 967 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:49 967 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:49 967 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:49 967 [Note] IPv6 is available.
2020-09-26 13:48:49 967 [Note]   - '::' resolves to '::';
2020-09-26 13:48:49 967 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:49 967 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:49 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:49 mysqld_safe mysqld restarted
2020-09-26 13:48:50 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:50 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 978 ...
2020-09-26 13:48:50 978 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:50 978 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:50 978 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:50 978 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:50 978 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:50 978 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:50 978 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:50 978 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:50 978 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:50 978 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:50 978 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:50 978 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:50 978 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:50 978 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:50 978 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:50 978 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:50 978 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:50 978 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:50 978 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:50 978 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:50 978 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:50 978 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:50 978 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:50 978 [Note] IPv6 is available.
2020-09-26 13:48:50 978 [Note]   - '::' resolves to '::';
2020-09-26 13:48:50 978 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:50 978 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:50 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:50 mysqld_safe mysqld restarted
2020-09-26 13:48:51 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:51 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 989 ...
2020-09-26 13:48:51 989 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:51 989 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:51 989 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:51 989 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:51 989 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:51 989 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:51 989 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:51 989 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:51 989 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:51 989 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:51 989 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:51 989 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:51 989 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:51 989 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:51 989 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:51 989 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:51 989 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:52 989 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:52 989 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:52 989 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:52 989 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:52 989 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:52 989 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:52 989 [Note] IPv6 is available.
2020-09-26 13:48:52 989 [Note]   - '::' resolves to '::';
2020-09-26 13:48:52 989 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:52 989 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:52 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:52 mysqld_safe mysqld restarted
2020-09-26 13:48:52 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:52 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1000 ...
2020-09-26 13:48:52 1000 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:52 1000 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:52 1000 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:52 1000 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:52 1000 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:52 1000 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:52 1000 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:52 1000 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:52 1000 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:52 1000 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:52 1000 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:52 1000 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:52 1000 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:52 1000 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:52 1000 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:52 1000 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:52 1000 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:53 1000 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:53 1000 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:53 1000 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:53 1000 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:53 1000 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:53 1000 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:53 1000 [Note] IPv6 is available.
2020-09-26 13:48:53 1000 [Note]   - '::' resolves to '::';
2020-09-26 13:48:53 1000 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:53 1000 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:53 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:53 mysqld_safe mysqld restarted
2020-09-26 13:48:53 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:53 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1101 ...
2020-09-26 13:48:53 1101 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:53 1101 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:53 1101 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:53 1101 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:53 1101 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:53 1101 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:53 1101 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:53 1101 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:53 1101 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:53 1101 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:53 1101 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:53 1101 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:53 1101 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:53 1101 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:53 1101 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:53 1101 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:53 1101 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:54 1101 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:54 1101 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:54 1101 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:54 1101 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:54 1101 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:54 1101 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:54 1101 [Note] IPv6 is available.
2020-09-26 13:48:54 1101 [Note]   - '::' resolves to '::';
2020-09-26 13:48:54 1101 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:54 1101 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:54 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:54 mysqld_safe mysqld restarted
2020-09-26 13:48:54 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:54 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1111 ...
2020-09-26 13:48:54 1111 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:54 1111 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:54 1111 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:54 1111 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:54 1111 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:54 1111 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:54 1111 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:54 1111 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:54 1111 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:54 1111 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:54 1111 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:54 1111 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:54 1111 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:54 1111 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:54 1111 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:54 1111 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:54 1111 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:55 1111 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:55 1111 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:55 1111 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:55 1111 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:55 1111 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:55 1111 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:55 1111 [Note] IPv6 is available.
2020-09-26 13:48:55 1111 [Note]   - '::' resolves to '::';
2020-09-26 13:48:55 1111 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:55 1111 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:55 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:55 mysqld_safe mysqld restarted
2020-09-26 13:48:55 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:55 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1121 ...
2020-09-26 13:48:55 1121 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:55 1121 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:55 1121 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:55 1121 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:55 1121 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:55 1121 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:55 1121 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:55 1121 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:55 1121 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:55 1121 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:55 1121 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:55 1121 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:55 1121 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:55 1121 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:55 1121 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:55 1121 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:56 1121 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:56 1121 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:56 1121 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:56 1121 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:56 1121 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:56 1121 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:56 1121 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:56 1121 [Note] IPv6 is available.
2020-09-26 13:48:56 1121 [Note]   - '::' resolves to '::';
2020-09-26 13:48:56 1121 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:56 1121 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:56 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:56 mysqld_safe mysqld restarted
2020-09-26 13:48:57 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:57 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1131 ...
2020-09-26 13:48:57 1131 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:57 1131 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:57 1131 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:57 1131 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:57 1131 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:57 1131 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:57 1131 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:57 1131 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:57 1131 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:57 1131 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:57 1131 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:57 1131 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:57 1131 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:57 1131 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:57 1131 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:57 1131 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:57 1131 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:57 1131 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:57 1131 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:57 1131 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:57 1131 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:57 1131 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:57 1131 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:57 1131 [Note] IPv6 is available.
2020-09-26 13:48:57 1131 [Note]   - '::' resolves to '::';
2020-09-26 13:48:57 1131 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:57 1131 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:57 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:57 mysqld_safe mysqld restarted
2020-09-26 13:48:58 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:58 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1141 ...
2020-09-26 13:48:58 1141 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:58 1141 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:58 1141 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:58 1141 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:58 1141 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:58 1141 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:58 1141 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:58 1141 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:58 1141 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:58 1141 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:58 1141 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:58 1141 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:58 1141 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:58 1141 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:58 1141 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:58 1141 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:58 1141 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:48:59 1141 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:48:59 1141 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:48:59 1141 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:48:59 1141 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:59 1141 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:48:59 1141 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:48:59 1141 [Note] IPv6 is available.
2020-09-26 13:48:59 1141 [Note]   - '::' resolves to '::';
2020-09-26 13:48:59 1141 [Note] Server socket created on IP: '::'.
2020-09-26 13:48:59 1141 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:48:59 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:48:59 mysqld_safe mysqld restarted
2020-09-26 13:48:59 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:48:59 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1153 ...
2020-09-26 13:48:59 1153 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:48:59 1153 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:48:59 1153 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:48:59 1153 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:48:59 1153 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:48:59 1153 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:48:59 1153 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:48:59 1153 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:48:59 1153 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:48:59 1153 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:48:59 1153 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:48:59 1153 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:48:59 1153 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:48:59 1153 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:48:59 1153 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:48:59 1153 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:48:59 1153 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:00 1153 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:00 1153 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:00 1153 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:00 1153 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:00 1153 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:00 1153 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:00 1153 [Note] IPv6 is available.
2020-09-26 13:49:00 1153 [Note]   - '::' resolves to '::';
2020-09-26 13:49:00 1153 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:00 1153 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:00 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:00 mysqld_safe mysqld restarted
2020-09-26 13:49:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:00 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1163 ...
2020-09-26 13:49:00 1163 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:00 1163 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:00 1163 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:00 1163 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:00 1163 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:00 1163 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:00 1163 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:00 1163 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:00 1163 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:00 1163 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:00 1163 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:00 1163 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:00 1163 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:00 1163 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:00 1163 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:00 1163 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:00 1163 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:01 1163 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:01 1163 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:01 1163 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:01 1163 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:01 1163 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:01 1163 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:01 1163 [Note] IPv6 is available.
2020-09-26 13:49:01 1163 [Note]   - '::' resolves to '::';
2020-09-26 13:49:01 1163 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:01 1163 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:01 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:01 mysqld_safe mysqld restarted
2020-09-26 13:49:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:01 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1173 ...
2020-09-26 13:49:01 1173 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:01 1173 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:01 1173 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:01 1173 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:01 1173 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:01 1173 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:01 1173 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:01 1173 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:01 1173 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:01 1173 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:01 1173 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:01 1173 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:01 1173 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:01 1173 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:01 1173 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:01 1173 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:01 1173 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:02 1173 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:02 1173 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:02 1173 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:02 1173 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:02 1173 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:02 1173 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:02 1173 [Note] IPv6 is available.
2020-09-26 13:49:02 1173 [Note]   - '::' resolves to '::';
2020-09-26 13:49:02 1173 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:02 1173 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:02 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:02 mysqld_safe mysqld restarted
2020-09-26 13:49:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:02 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1183 ...
2020-09-26 13:49:02 1183 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:02 1183 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:02 1183 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:02 1183 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:02 1183 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:02 1183 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:02 1183 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:02 1183 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:02 1183 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:02 1183 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:02 1183 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:02 1183 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:02 1183 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:02 1183 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:02 1183 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:02 1183 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:03 1183 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:03 1183 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:03 1183 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:03 1183 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:03 1183 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:03 1183 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:03 1183 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:03 1183 [Note] IPv6 is available.
2020-09-26 13:49:03 1183 [Note]   - '::' resolves to '::';
2020-09-26 13:49:03 1183 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:03 1183 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:03 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:03 mysqld_safe mysqld restarted
2020-09-26 13:49:04 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:04 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1193 ...
2020-09-26 13:49:04 1193 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:04 1193 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:04 1193 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:04 1193 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:04 1193 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:04 1193 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:04 1193 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:04 1193 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:04 1193 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:04 1193 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:04 1193 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:04 1193 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:04 1193 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:04 1193 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:04 1193 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:04 1193 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:04 1193 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:04 1193 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:04 1193 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:04 1193 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:04 1193 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:04 1193 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:04 1193 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:04 1193 [Note] IPv6 is available.
2020-09-26 13:49:04 1193 [Note]   - '::' resolves to '::';
2020-09-26 13:49:04 1193 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:04 1193 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:04 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:04 mysqld_safe mysqld restarted
2020-09-26 13:49:04 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:04 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1204 ...
2020-09-26 13:49:04 1204 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:04 1204 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:04 1204 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:04 1204 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:04 1204 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:04 1204 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:04 1204 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:04 1204 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:04 1204 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:04 1204 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:04 1204 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:04 1204 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:04 1204 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:04 1204 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:04 1204 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:04 1204 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:04 1204 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:05 1204 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:05 1204 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:05 1204 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:05 1204 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:05 1204 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:05 1204 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:05 1204 [Note] IPv6 is available.
2020-09-26 13:49:05 1204 [Note]   - '::' resolves to '::';
2020-09-26 13:49:05 1204 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:05 1204 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:05 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:05 mysqld_safe mysqld restarted
2020-09-26 13:49:05 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:05 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1215 ...
2020-09-26 13:49:05 1215 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:05 1215 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:05 1215 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:05 1215 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:05 1215 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:05 1215 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:05 1215 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:05 1215 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:05 1215 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:05 1215 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:05 1215 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:05 1215 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:05 1215 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:05 1215 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:05 1215 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:05 1215 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:05 1215 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:06 1215 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:06 1215 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:06 1215 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:06 1215 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:06 1215 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:06 1215 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:06 1215 [Note] IPv6 is available.
2020-09-26 13:49:06 1215 [Note]   - '::' resolves to '::';
2020-09-26 13:49:06 1215 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:06 1215 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:06 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:06 mysqld_safe mysqld restarted
2020-09-26 13:49:06 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:06 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1225 ...
2020-09-26 13:49:06 1225 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:06 1225 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:06 1225 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:06 1225 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:06 1225 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:06 1225 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:06 1225 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:06 1225 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:06 1225 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:07 1225 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:07 1225 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:07 1225 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:07 1225 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:07 1225 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:07 1225 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:07 1225 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:07 1225 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:07 1225 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:07 1225 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:07 1225 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:07 1225 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:07 1225 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:07 1225 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:07 1225 [Note] IPv6 is available.
2020-09-26 13:49:07 1225 [Note]   - '::' resolves to '::';
2020-09-26 13:49:07 1225 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:07 1225 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:07 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:07 mysqld_safe mysqld restarted
2020-09-26 13:49:08 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:08 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1235 ...
2020-09-26 13:49:08 1235 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:08 1235 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:08 1235 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:08 1235 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:08 1235 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:08 1235 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:08 1235 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:08 1235 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:08 1235 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:08 1235 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:08 1235 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:08 1235 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:08 1235 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:08 1235 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:08 1235 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:08 1235 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:08 1235 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:08 1235 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:08 1235 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:08 1235 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:08 1235 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:08 1235 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:08 1235 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:08 1235 [Note] IPv6 is available.
2020-09-26 13:49:08 1235 [Note]   - '::' resolves to '::';
2020-09-26 13:49:08 1235 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:08 1235 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:08 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:08 mysqld_safe mysqld restarted
2020-09-26 13:49:09 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:09 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1248 ...
2020-09-26 13:49:09 1248 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:09 1248 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:09 1248 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:09 1248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:09 1248 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:09 1248 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:09 1248 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:09 1248 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:09 1248 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:09 1248 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:09 1248 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:09 1248 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:09 1248 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:09 1248 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:09 1248 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:09 1248 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:09 1248 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:09 1248 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:09 1248 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:09 1248 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:09 1248 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:09 1248 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:09 1248 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:09 1248 [Note] IPv6 is available.
2020-09-26 13:49:09 1248 [Note]   - '::' resolves to '::';
2020-09-26 13:49:09 1248 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:09 1248 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:09 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:09 mysqld_safe mysqld restarted
2020-09-26 13:49:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:10 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1258 ...
2020-09-26 13:49:10 1258 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:10 1258 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:10 1258 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:10 1258 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:10 1258 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:10 1258 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:10 1258 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:10 1258 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:10 1258 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:10 1258 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:10 1258 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:10 1258 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:10 1258 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:10 1258 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:10 1258 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:10 1258 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:10 1258 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:10 1258 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:10 1258 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:11 1258 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:11 1258 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:11 1258 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:11 1258 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:11 1258 [Note] IPv6 is available.
2020-09-26 13:49:11 1258 [Note]   - '::' resolves to '::';
2020-09-26 13:49:11 1258 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:11 1258 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:11 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:11 mysqld_safe mysqld restarted
2020-09-26 13:49:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:11 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1268 ...
2020-09-26 13:49:11 1268 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:11 1268 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:11 1268 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:11 1268 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:11 1268 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:11 1268 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:11 1268 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:11 1268 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:11 1268 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:11 1268 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:11 1268 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:11 1268 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:11 1268 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:11 1268 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:11 1268 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:11 1268 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:11 1268 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:12 1268 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:12 1268 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:12 1268 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:12 1268 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:12 1268 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:12 1268 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:12 1268 [Note] IPv6 is available.
2020-09-26 13:49:12 1268 [Note]   - '::' resolves to '::';
2020-09-26 13:49:12 1268 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:12 1268 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:12 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:12 mysqld_safe mysqld restarted
2020-09-26 13:49:12 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:12 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1278 ...
2020-09-26 13:49:12 1278 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:12 1278 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:12 1278 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:12 1278 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:12 1278 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:12 1278 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:12 1278 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:12 1278 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:12 1278 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:12 1278 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:12 1278 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:12 1278 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:12 1278 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:12 1278 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:12 1278 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:12 1278 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:12 1278 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:13 1278 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:13 1278 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:13 1278 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:13 1278 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:13 1278 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:13 1278 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:13 1278 [Note] IPv6 is available.
2020-09-26 13:49:13 1278 [Note]   - '::' resolves to '::';
2020-09-26 13:49:13 1278 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:13 1278 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:13 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:13 mysqld_safe mysqld restarted
2020-09-26 13:49:13 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:13 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1292 ...
2020-09-26 13:49:13 1292 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:13 1292 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:13 1292 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:13 1292 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:13 1292 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:13 1292 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:13 1292 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:13 1292 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:13 1292 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:13 1292 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:13 1292 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:13 1292 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:13 1292 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:13 1292 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:13 1292 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:13 1292 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:13 1292 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:14 1292 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:14 1292 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:14 1292 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:14 1292 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:14 1292 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:14 1292 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:14 1292 [Note] IPv6 is available.
2020-09-26 13:49:14 1292 [Note]   - '::' resolves to '::';
2020-09-26 13:49:14 1292 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:14 1292 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:14 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:14 mysqld_safe mysqld restarted
2020-09-26 13:49:14 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:14 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1302 ...
2020-09-26 13:49:14 1302 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:14 1302 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:14 1302 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:14 1302 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:14 1302 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:14 1302 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:14 1302 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:14 1302 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:14 1302 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:14 1302 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:14 1302 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:14 1302 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:14 1302 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:14 1302 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:14 1302 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:14 1302 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:14 1302 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:15 1302 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:15 1302 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:15 1302 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:15 1302 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:15 1302 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:15 1302 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:15 1302 [Note] IPv6 is available.
2020-09-26 13:49:15 1302 [Note]   - '::' resolves to '::';
2020-09-26 13:49:15 1302 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:15 1302 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:15 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:15 mysqld_safe mysqld restarted
2020-09-26 13:49:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:16 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1312 ...
2020-09-26 13:49:16 1312 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:16 1312 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:16 1312 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:16 1312 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:16 1312 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:16 1312 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:16 1312 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:16 1312 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:16 1312 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:16 1312 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:16 1312 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:16 1312 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:16 1312 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:16 1312 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:16 1312 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:16 1312 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:16 1312 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:17 1312 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:17 1312 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:17 1312 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:17 1312 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:17 1312 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:17 1312 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:17 1312 [Note] IPv6 is available.
2020-09-26 13:49:17 1312 [Note]   - '::' resolves to '::';
2020-09-26 13:49:17 1312 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:17 1312 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
13:49:17 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802223800
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 = 7fffffffe6e0 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
200926 13:49:17 mysqld_safe mysqld restarted
2020-09-26 13:49:17 1393 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:17 1393 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:17 1393 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:17 1393 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:17 1393 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:17 1393 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:17 1393 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:17 1393 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:17 1393 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:17 1393 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:17 1393 [Note] InnoDB: Log scan progressed past the checkpoint lsn 49463
2020-09-26 13:49:17 1393 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:17 1393 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:17 1393 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:17 1393 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:17 1393 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1600607
2020-09-26 13:49:17 1393 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
2020-09-26 13:49:17 1393 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:17 1393 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:17 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-09-26 13:49:17 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.49) starting as process 1403 ...
2020-09-26 13:49:17 1403 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:17 1403 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:17 1403 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:17 1403 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:17 1403 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:17 1403 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:17 1403 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:17 1403 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:17 1403 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:17 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:17 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:17 1403 [Note] InnoDB: Retrying to lock the first data file
2020-09-26 13:49:17 1393 [Note] InnoDB: 5.6.49 started; log sequence number 1600607
2020-09-26 13:49:17 1393 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:17 1393 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:17 1393 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:17 1393 [Note] IPv6 is available.
2020-09-26 13:49:17 1393 [Note]   - '::' resolves to '::';
2020-09-26 13:49:17 1393 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:17 1393 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
2020-09-26 13:49:18 1393 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:18 1393 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:18 1393 [ERROR] Column count of mysql.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Column count of mysql.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:18 1393 [ERROR] Column count of mysql.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
2020-09-26 13:49:18 1393 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
2020-09-26 13:49:18 1393 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.49'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
2020-09-26 13:49:18 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:18 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:19 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:19 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:21 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:21 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:22 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:22 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:23 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:23 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:24 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:24 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:25 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:25 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:26 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:26 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:27 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:27 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:28 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:28 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:29 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:29 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:30 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:30 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:31 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:31 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:32 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:32 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:33 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:33 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:34 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:34 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:35 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:35 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:36 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:36 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:37 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:37 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:38 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:38 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:39 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:39 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:40 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:40 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:41 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:41 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:42 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:42 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:43 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:43 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:44 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:44 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:45 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:45 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:46 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:46 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:48 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:48 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:49 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:49 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:50 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:50 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:51 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:51 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
13:49:51 UTC - mysqld got signal 11 ;
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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68058 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x802220800
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 = 7fffdd5a6f40 thread_stack 0x40000
0xaee638 <my_print_stacktrace+0x38> at /usr/local/libexec/mysqld
0xa72f79 <handle_fatal_signal+0x279> at /usr/local/libexec/mysqld
0x8012893c0 <_pthread_sigmask+0x530> at /lib/libthr.so.3

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2020-09-26 13:49:51 1411 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:49:51 1411 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:49:51 1411 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:49:51 1411 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:49:51 1411 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:49:51 1411 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:49:51 1411 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:49:51 1411 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:49:51 1411 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:49:51 1411 [Note] InnoDB: Highest supported file format is Barracuda.
2020-09-26 13:49:51 1411 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600617 in the ib_logfiles!
2020-09-26 13:49:51 1411 [Note] InnoDB: Database was not shutdown normally!
2020-09-26 13:49:51 1411 [Note] InnoDB: Starting crash recovery.
2020-09-26 13:49:51 1411 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-09-26 13:49:51 1411 [Note] InnoDB: Restoring possible half-written data pages 
2020-09-26 13:49:51 1411 [Note] InnoDB: from the doublewrite buffer...
2020-09-26 13:49:51 1411 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-26 13:49:51 1411 [Note] InnoDB: Waiting for purge to start
2020-09-26 13:49:51 1411 [Note] InnoDB: 5.6.49 started; log sequence number 1600617
2020-09-26 13:49:51 1411 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:51 1411 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2020-09-26 13:49:51 1411 [Note] Server hostname (bind-address): '*'; port: 3306
2020-09-26 13:49:51 1411 [Note] IPv6 is available.
2020-09-26 13:49:51 1411 [Note]   - '::' resolves to '::';
2020-09-26 13:49:51 1411 [Note] Server socket created on IP: '::'.
2020-09-26 13:49:51 1411 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
2020-09-26 13:49:51 1411 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:51 1411 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:51 1411 [ERROR] Column count of mysql.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Column count of mysql.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:51 1411 [ERROR] Column count of mysql.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Column count of mysql.threads is wrong. Expected 14, found 3. Created with MySQL 50533, now running 50649. Please use mysql_upgrade to fix this error.
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
2020-09-26 13:49:51 1411 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
2020-09-26 13:49:51 1411 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.49'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
2020-09-26 13:49:52 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:52 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:53 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:53 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:54 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:54 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:55 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:55 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:56 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:56 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:57 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:57 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:58 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:58 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:49:59 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:49:59 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:00 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:00 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:01 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:01 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:02 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:02 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:03 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:03 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:03 1556 [Note] Plugin 'FEDERATED' is disabled.
2020-09-26 13:50:03 1556 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-09-26 13:50:03 1556 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-26 13:50:03 1556 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-09-26 13:50:03 1556 [Note] InnoDB: Memory barrier is not used
2020-09-26 13:50:03 1556 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-26 13:50:03 1556 [Note] InnoDB: Using CPU crc32 instructions
2020-09-26 13:50:03 1556 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-26 13:50:03 1556 [Note] InnoDB: Completed initialization of buffer pool
2020-09-26 13:50:03 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:03 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:03 1556 [Note] InnoDB: Retrying to lock the first data file
2020-09-26 13:50:04 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:04 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:04 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:04 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:05 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:05 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:06 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:06 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:06 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:06 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:07 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:07 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:07 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:07 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:08 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:08 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:08 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:08 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:09 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:09 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:09 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:09 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:10 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:10 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:11 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:11 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:11 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:11 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:12 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:12 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:12 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:12 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:13 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:13 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:13 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:13 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:14 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:14 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:14 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:14 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:15 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:15 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:15 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:15 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:16 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:16 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:16 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:16 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:17 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:17 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:17 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:17 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:18 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:18 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:18 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:18 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:19 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:19 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:19 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:19 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:20 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:20 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:20 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:20 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:21 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:21 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:21 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:21 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:22 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:22 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:22 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:22 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:23 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:23 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:23 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:23 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:24 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:24 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:24 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:24 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:25 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:25 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:25 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:25 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:26 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:26 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:26 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:26 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:27 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:27 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:27 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:27 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:28 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:28 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:28 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:28 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:29 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:29 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:30 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:30 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:30 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:30 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:31 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:31 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:31 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:31 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:32 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:32 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:32 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:32 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:33 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:33 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:33 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:33 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:34 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:34 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:35 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:35 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:35 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:35 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:36 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:36 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:36 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:36 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:37 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:37 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:37 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:37 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:38 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:38 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:38 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:38 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:39 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:39 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:39 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:39 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:40 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:40 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:40 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:40 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:41 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:41 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:41 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:41 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:42 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:42 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:42 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:42 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:43 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:43 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:43 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:43 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:44 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:44 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:44 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:44 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:45 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:45 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:45 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:45 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:46 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:46 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:46 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:46 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:47 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:47 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:47 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:47 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:48 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:48 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:48 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:48 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:49 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:49 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:49 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:49 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:50 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:50 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:50 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:50 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:51 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:51 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:51 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:51 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:52 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:52 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:52 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:52 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:53 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:53 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:53 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:53 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:54 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:54 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:55 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:55 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:55 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:55 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:56 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:56 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:57 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:57 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:57 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:57 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:58 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:58 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:58 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:58 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:59 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:59 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:50:59 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:50:59 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:00 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:00 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:00 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:00 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:01 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:01 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:01 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:01 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:02 1403 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:02 1403 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:02 1403 [Note] InnoDB: Unable to open the first data file
2020-09-26 13:51:02 801780000  InnoDB: Operating system error number 35 in a file operation.
InnoDB: Error number 35 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2020-09-26 13:51:02 1403 [ERROR] InnoDB: Can't open './ibdata1'
2020-09-26 13:51:02 1403 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2020-09-26 13:51:02 1403 [ERROR] Plugin 'InnoDB' init function returned error.
2020-09-26 13:51:02 1403 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-09-26 13:51:02 1403 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-09-26 13:51:02 1403 [ERROR] Aborting

2020-09-26 13:51:02 1403 [Note] Binlog end
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'partition'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_METRICS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_CMPMEM'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_CMP'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_LOCKS'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'INNODB_TRX'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'BLACKHOLE'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'ARCHIVE'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'MRG_MYISAM'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'MyISAM'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'MEMORY'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'CSV'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'sha256_password'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'mysql_old_password'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'mysql_native_password'
2020-09-26 13:51:02 1403 [Note] Shutting down plugin 'binlog'
2020-09-26 13:51:02 1403 [Note] /usr/local/libexec/mysqld: Shutdown complete

200926 13:51:02 mysqld_safe mysqld from pid file /var/db/mysql/freebsd.pid ended
2020-09-26 13:51:02 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:02 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:03 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:03 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:04 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:04 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:05 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:05 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:06 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:06 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:07 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:07 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:08 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:08 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:09 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:09 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:10 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:10 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:11 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:11 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:12 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:12 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:13 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:13 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:14 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:14 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:15 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:15 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:17 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:17 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:18 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:18 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:19 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:19 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:20 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:20 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:21 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:21 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:22 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:22 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:23 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:23 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:24 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:24 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:25 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:25 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:26 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:26 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:27 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:27 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:28 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:28 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:29 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:29 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:30 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:30 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:31 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:31 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:32 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:32 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:33 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:33 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:34 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:34 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:35 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:35 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:36 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:36 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:37 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:37 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:39 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:39 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:40 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:40 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:41 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:41 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:42 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:42 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:43 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:43 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:44 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:44 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:45 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:45 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:46 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:46 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:47 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:47 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:48 1556 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 35
2020-09-26 13:51:48 1556 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-09-26 13:51:48 1556 [Note] InnoDB: Unable to open the first data file
2020-09-26 13:51:48 801780000  InnoDB: Operating system error number 35 in a file operation.
InnoDB: Error number 35 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2020-09-26 13:51:48 1556 [ERROR] InnoDB: Can't open './ibdata1'
2020-09-26 13:51:48 1556 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2020-09-26 13:51:48 1556 [ERROR] Plugin 'InnoDB' init function returned error.
2020-09-26 13:51:48 1556 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-09-26 13:51:48 1556 [ERROR] Unknown/unsupported storage engine: InnoDB
2020-09-26 13:51:48 1556 [ERROR] Aborting

2020-09-26 13:51:48 1556 [Note] Binlog end
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'partition'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_METRICS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_CMPMEM'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_CMP'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_LOCKS'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'INNODB_TRX'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'BLACKHOLE'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'ARCHIVE'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'MRG_MYISAM'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'MyISAM'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'MEMORY'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'CSV'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'sha256_password'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'mysql_old_password'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'mysql_native_password'
2020-09-26 13:51:48 1556 [Note] Shutting down plugin 'binlog'
2020-09-26 13:51:48 1556 [Note] /usr/local/libexec/mysqld: Shutdown complete