It doesn't seems to be fixed on the version 5.7.30 and Bryce never
mentioned that the bug is fixed but need to retrieve patches.
I can still reproduce the bug with the version 5.7.30 "mysql-server-core
5.7.30-0ubuntu0.16.04.1":
# service mysql restart
2020-06-06T15:01:13.632638Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
2020-06-06T15:01:13.632650Z 0 [Note] Shutting down plugin 'INNODB_TRX'
2020-06-06T15:01:13.632671Z 0 [Note] Shutting down plugin 'InnoDB'
2020-06-06T15:01:13.802792Z 0 [Note] InnoDB: FTS optimize thread exiting.
2020-06-06T15:01:13.803959Z 0 [Note] InnoDB: Starting shutdown...
2020-06-06T15:01:13.904557Z 0 [Note] InnoDB: Dumping buffer pool(s) to
/mysql/ib_buffer_pool
2020-06-06T15:01:13.908147Z 0 [Note] InnoDB: Buffer pool(s) dump completed at
200606 17:01:13
2020-06-06T15:01:14.405452Z 0 [ERROR] [FATAL] InnoDB: Page [page id:
space=118412, page number=324] still fixed or dirty
2020-06-06 17:01:14 0x7fa0b89d7740 InnoDB: Assertion failure in thread
140328268822336 in file ut0ut.cc line 918
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:01:14 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=92
max_threads=200
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 = 674420 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8b15b]
/usr/sbin/mysqld(handle_fatal_signal+0x36f)[0x77279f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fa0b6e7e390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fa0b6237428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fa0b623902a]
/usr/sbin/mysqld[0x747f1c]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x145)[0x10c7a35]
/usr/sbin/mysqld[0x110335c]
/usr/sbin/mysqld(_Z13buf_all_freedv+0x4c)[0x11033cc]
/usr/sbin/mysqld(_Z37logs_empty_and_mark_files_at_shutdownv+0x1c19)[0xf857e9]
/usr/sbin/mysqld(_Z27innobase_shutdown_for_mysqlv+0xa27)[0x10697b7]
/usr/sbin/mysqld[0xf18345]
/usr/sbin/mysqld(_Z22ha_finalize_handlertonP13st_plugin_int+0x2c)[0x7c667c]
/usr/sbin/mysqld[0xc67d67]
/usr/sbin/mysqld(_Z15plugin_shutdownv+0x3fd)[0xc6a21d]
/usr/sbin/mysqld[0x767be4]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1fe5)[0x76dc05]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fa0b6222830]
/usr/sbin/mysqld(_start+0x29)[0x762839]
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-06-06T15:01:15.212853Z 0 [Warning] TIMESTAMP with implicit DEFAULT value
is deprecated. Please use --explicit_defaults_for_timestamp server option (see
documentation for more details).
2020-06-06T15:01:15.214780Z 0 [Note] /usr/sbin/mysqld (mysqld
5.7.30-0ubuntu0.16.04.1) starting as process 7459 ...
2020-06-06T15:01:15.246934Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-06-06T15:01:15.246974Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC
atomic builtins
2020-06-06T15:01:15.246980Z 0 [Note] InnoDB: Uses event mutexes
2020-06-06T15:01:15.246984Z 0 [Note] InnoDB: GCC builtin
__atomic_thread_fence() is used for memory barrier
2020-06-06T15:01:15.246988Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2020-06-06T15:01:15.246991Z 0 [Note] InnoDB: Using Linux native AIO
2020-06-06T15:01:15.247268Z 0 [Note] InnoDB: Number of pools: 1
2020-06-06T15:01:15.247380Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-06-06T15:01:15.249194Z 0 [Note] InnoDB: Initializing buffer pool, total
size = 128M, instances = 1, chunk size = 128M
2020-06-06T15:01:15.257605Z 0 [Note] InnoDB: Completed initialization of buffer
pool
2020-06-06T15:01:15.260202Z 0 [Note] InnoDB: If the mysqld execution user is
authorized, page cleaner thread priority can be changed. See the man page of
setpriority().
2020-06-06T15:01:15.272993Z 0 [Note] InnoDB: Highest supported file format is
Barracuda.
2020-06-06T15:01:15.278629Z 0 [Note] InnoDB: The log sequence number
1129973168574 in the system tablespace does not match the log sequence number
1241207936140 in the ib_logfiles!
2020-06-06T15:01:15.278648Z 0 [Note] InnoDB: Database was not shutdown normally!
2020-06-06T15:01:15.278655Z 0 [Note] InnoDB: Starting crash recovery.
2020-06-06T15:01:41.810524Z 0 [Note] InnoDB: Removed temporary tablespace data
file: "ibtmp1"
2020-06-06T15:01:41.810562Z 0 [Note] InnoDB: Creating shared tablespace for
temporary tables
2020-06-06T15:01:41.810632Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12
MB. Physically writing the file full; Please wait ...
2020-06-06T15:01:41.832362Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-06-06T15:01:41.837996Z 0 [Note] InnoDB: 96 redo rollback segment(s) found.
96 redo rollback segment(s) are active.
2020-06-06T15:01:41.838042Z 0 [Note] InnoDB: 32 non-redo rollback segment(s)
are active.
2020-06-06T15:01:41.839388Z 0 [Note] InnoDB: Waiting for purge to start
2020-06-06T15:01:41.889664Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop
took 26629ms. The settings might not be optimal. (flushed=0 and evicted=0,
during the time.)
2020-06-06T15:01:41.889675Z 0 [Note] InnoDB: 5.7.30 started; log sequence
number 1241207936140
2020-06-06T15:01:41.890172Z 0 [Note] InnoDB: Loading buffer pool(s) from
/home/mysql/ib_buffer_pool
2020-06-06T15:01:41.892904Z 0 [Note] Plugin 'FEDERATED' is disabled.
2020-06-06T15:01:41.915491Z 0 [Note] Found ca.pem, server-cert.pem and
server-key.pem in data directory. Trying to enable SSL support using them.
2020-06-06T15:01:41.915537Z 0 [Note] Skipping generation of SSL certificates as
certificate files are present in data directory.
2020-06-06T15:01:41.920961Z 0 [Warning] CA certificate ca.pem is self signed.
2020-06-06T15:01:41.921003Z 0 [Note] Skipping generation of RSA key pair as key
files are present in data directory.
2020-06-06T15:01:41.921418Z 0 [Note] Server hostname (bind-address): '*'; port:
3306
2020-06-06T15:01:41.921454Z 0 [Note] IPv6 is available.
2020-06-06T15:01:41.921484Z 0 [Note] - '::' resolves to '::';
2020-06-06T15:01:41.921529Z 0 [Note] Server socket created on IP: '::'.
2020-06-06T15:01:41.982020Z 0 [Note] InnoDB: Buffer pool(s) load completed at
200606 17:01:41
2020-06-06T15:01:42.016421Z 0 [Note] Event Scheduler: Loaded 0 events
2020-06-06T15:01:42.016887Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.30-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock'
port: 3306 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831773
Title:
High CPU usage, MySQL process got stuck on "SHOW SESSION VARIABLES
LIKE 'FOREIGN_KEY_CHECKS' "
To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1831773/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
