I have earlier MySQL 5.7 over Ubuntu 16.04 with following configuration in
[mysqld] innodb_buffer_pool_size = 1228M innodb_log_file_size = 512M innodb_log_buffer_size = 16M innodb_read_io_threads = 64 innodb_write_io_threads = 64 query_cache_size = 10M max_allowed_packet = 16M key_buffer_size = 1M interactive_timeout=180 wait_timeout=180
I have upgraded it to MariaDB 10.3 and it worked but then I got high memory usage warnings over Ubuntu and database keeps dropping connection. I noticed that
/etc/mysql/my.cnf was overwritten with default settings provided along with installation and I was getting error as below:
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/innodb-recovery-modes/ InnoDB: about forcing recovery. 21:23:59 [ERROR] 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. To report this bug, see https://mariadb.com/kb/en/reporting-bugs 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. Server version: 10.3.13-MariaDB-1:10.3.13+maria~xenial-log key_buffer_size=1048576 read_buffer_size=1048576 max_used_connections=0 max_threads=102 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 316620K 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 = 0x0 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5650a112b36e] /usr/sbin/mysqld(handle_fatal_signal+0x347)[0x5650a0bda187] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f2fd0fc1390] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f2fd0590428] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f2fd059202a] /usr/sbin/mysqld(+0x499234)[0x5650a0921234] /usr/sbin/mysqld(+0xae7dd4)[0x5650a0f6fdd4] /usr/sbin/mysqld(+0xad2088)[0x5650a0f5a088] /usr/sbin/mysqld(+0xadd1b9)[0x5650a0f651b9] /usr/sbin/mysqld(+0xaa71f5)[0x5650a0f2f1f5] /usr/sbin/mysqld(+0x998249)[0x5650a0e20249] /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64) [0x5650a0bdca44] /usr/sbin/mysqld(+0x584cd9)[0x5650a0a0ccd9] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x7da)[0x5650a0a0d6ca] /usr/sbin/mysqld(+0x4b9b01)[0x5650a0941b01] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x46a)[0x5650a0947baa] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f2fd057b830] /usr/sbin/mysqld(_start+0x29)[0x5650a093a5d9] 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.
That error was fixed but I am wondering in which file should I change parameters so that it won't be overwritten?