160112 08:49:29 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2016-01-12 08:49:30 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-01-12 08:49:30 0 [Note] /usr/local/Cellar/mysql56/5.6.27/bin/mysqld (mysqld 5.6.27) starting as process 62810 ...
2016-01-12 08:49:30 62810 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2016-01-12 08:49:30 62810 [Note] Plugin 'FEDERATED' is disabled.
00:49:30 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 = 68101 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fff57e48f00
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 = 7fff57e489a0 thread_stack 0x40000
0 mysqld 0x0000000108066665 my_print_stacktrace + 61
1 mysqld 0x0000000107eb5db2 handle_fatal_signal + 696
2 libsystem_platform.dylib 0x00007fff848bb52a _sigtramp + 26
3 mysqld 0x00000001086464c8 PSI_server + 0
4 mysqld 0x0000000107fcfae9 _Z14open_table_defP3THDP11TABLE_SHAREj + 4816
5 mysqld 0x0000000107ee80ff _Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij + 448
6 mysqld 0x0000000107eeb27b _Z10open_tableP3THDP10TABLE_LISTP18Open_table_context + 2019
7 mysqld 0x0000000107eed68b _Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy + 1252
8 mysqld 0x0000000107eedfcc _Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy + 50
9 mysqld 0x0000000107f617a5 _Z11plugin_initPiPPci + 2678
10 mysqld 0x0000000107ff7fa6 _Z11mysqld_mainiPPc + 2674
11 libdyld.dylib 0x00007fff8896d5ad start + 1
12 ??? 0x0000000000000007 0x0 + 7
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.
160112 08:49:30 mysqld_safe mysqld from pid file /usr/local/var/mysql/Services-iMac.local.pid ended
160112 08:49:43 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2016-01-12 08:49:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-01-12 08:49:43 0 [Note] /usr/local/Cellar/mysql56/5.6.27/bin/mysqld (mysqld 5.6.27) starting as process 62980 ...
2016-01-12 08:49:43 62980 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2016-01-12 08:49:43 62980 [Note] Plugin 'FEDERATED' is disabled.
00:49: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 = 68101 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fff573c1f00
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 = 7fff573c19a0 thread_stack 0x40000
0 mysqld 0x0000000108aed665 my_print_stacktrace + 61
1 mysqld 0x000000010893cdb2 handle_fatal_signal + 696
2 libsystem_platform.dylib 0x00007fff848bb52a _sigtramp + 26
3 mysqld 0x00000001090cd4c8 PSI_server + 0
4 mysqld 0x0000000108a56ae9 _Z14open_table_defP3THDP11TABLE_SHAREj + 4816
5 mysqld 0x000000010896f0ff _Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij + 448
6 mysqld 0x000000010897227b _Z10open_tableP3THDP10TABLE_LISTP18Open_table_context + 2019
7 mysqld 0x000000010897468b _Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy + 1252
8 mysqld 0x0000000108974fcc _Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy + 50
9 mysqld 0x00000001089e87a5 _Z11plugin_initPiPPci + 2678
10 mysqld 0x0000000108a7efa6 _Z11mysqld_mainiPPc + 2674
11 libdyld.dylib 0x00007fff8896d5ad start + 1
12 ??? 0x0000000000000007 0x0 + 7
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.
160112 08:49:43 mysqld_safe mysqld from pid file /usr/local/var/mysql/Services-iMac.local.pid ended
➜ mysql git:(master) sudo kill -9 62810
kill: 62810: No such process
➜ mysql git:(master) sudo cat Services-iMac.local.err
160112 08:49:29 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2016-01-12 08:49:30 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-01-12 08:49:30 0 [Note] /usr/local/Cellar/mysql56/5.6.27/bin/mysqld (mysqld 5.6.27) starting as process 62810 ...
2016-01-12 08:49:30 62810 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2016-01-12 08:49:30 62810 [Note] Plugin 'FEDERATED' is disabled.
00:49:30 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 = 68101 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fff57e48f00
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 = 7fff57e489a0 thread_stack 0x40000
0 mysqld 0x0000000108066665 my_print_stacktrace + 61
1 mysqld 0x0000000107eb5db2 handle_fatal_signal + 696
2 libsystem_platform.dylib 0x00007fff848bb52a _sigtramp + 26
3 mysqld 0x00000001086464c8 PSI_server + 0
4 mysqld 0x0000000107fcfae9 _Z14open_table_defP3THDP11TABLE_SHAREj + 4816
5 mysqld 0x0000000107ee80ff _Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij + 448
6 mysqld 0x0000000107eeb27b _Z10open_tableP3THDP10TABLE_LISTP18Open_table_context + 2019
7 mysqld 0x0000000107eed68b _Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy + 1252
8 mysqld 0x0000000107eedfcc _Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy + 50
9 mysqld 0x0000000107f617a5 _Z11plugin_initPiPPci + 2678
10 mysqld 0x0000000107ff7fa6 _Z11mysqld_mainiPPc + 2674
11 libdyld.dylib 0x00007fff8896d5ad start + 1
12 ??? 0x0000000000000007 0x0 + 7
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.
160112 08:49:30 mysqld_safe mysqld from pid file /usr/local/var/mysql/Services-iMac.local.pid ended
160112 08:49:43 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2016-01-12 08:49:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-01-12 08:49:43 0 [Note] /usr/local/Cellar/mysql56/5.6.27/bin/mysqld (mysqld 5.6.27) starting as process 62980 ...
2016-01-12 08:49:43 62980 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2016-01-12 08:49:43 62980 [Note] Plugin 'FEDERATED' is disabled.
00:49: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 = 68101 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fff573c1f00
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 = 7fff573c19a0 thread_stack 0x40000
0 mysqld 0x0000000108aed665 my_print_stacktrace + 61
1 mysqld 0x000000010893cdb2 handle_fatal_signal + 696
2 libsystem_platform.dylib 0x00007fff848bb52a _sigtramp + 26
3 mysqld 0x00000001090cd4c8 PSI_server + 0
4 mysqld 0x0000000108a56ae9 _Z14open_table_defP3THDP11TABLE_SHAREj + 4816
5 mysqld 0x000000010896f0ff _Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij + 448
6 mysqld 0x000000010897227b _Z10open_tableP3THDP10TABLE_LISTP18Open_table_context + 2019
7 mysqld 0x000000010897468b _Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy + 1252
8 mysqld 0x0000000108974fcc _Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy + 50
9 mysqld 0x00000001089e87a5 _Z11plugin_initPiPPci + 2678
10 mysqld 0x0000000108a7efa6 _Z11mysqld_mainiPPc + 2674
11 libdyld.dylib 0x00007fff8896d5ad start + 1
12 ??? 0x0000000000000007 0x0 + 7
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.
160112 08:49:43 mysqld_safe mysqld from pid file /usr/local/var/mysql/Services-iMac.local.pid ended
Trying to start mysql doesn't load it.
➜ mysql git:(master) mysql.server start
Starting MySQL
. ERROR! The server quit without updating PID file (/usr/local/var/mysql/Services-iMac.local.pid).
This happened to me after re-installing mysql.
I originally installed the default version (mysql 5.7.x), but downgraded back to mysql56.
The issue may lie on the unclean shutdown of 5.7 as I issued a brew uninstall mysql while my launchd-managed mysqld instance was running. The symlinks, data, and old 5.7.x-related stuff were not cleaned thoroughly.
As to the error, the solution so far was to follow the recommendation here: http://bugs.mysql.com/bug.php?id=70431, and i.e. adding the skip-grant-tables in your my.cnf (create one under /etc if you don't have one)
Related
I had to move from mysql (8.0.29) to mysql#5.7. MySQL in its newest formula does not compile any longer on my machine, because the machine is running Mojave in order to have native Aperture support.
I installed mysql#5.7 and changed path in my .zshrc to point to the new /usr/local/opt/mysql#5.7/bin.
After this I am still unable to start MySQL. When I run brew services list, I get:
mysql#5.7 stopped USER ~/Library/LaunchAgents/homebrew.mxcl.mysql#5.7.plist
When I try to run /usr/local/opt/mysql/bin/mysqld_safe --datadir=/usr/local/var/mysql I get:
√ ~ % /usr/local/opt/mysql/bin/mysqld_safe --datadir=/usr/local/var/mysql
2022-10-07T17:06:21.6NZ mysqld_safe Logging to '/usr/local/var/mysql/MACHINE.DOMAIN.TLD.err'.
2022-10-07T17:06:21.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
/usr/local/opt/mysql/bin/mysqld_safe: line 199: 9704 Abort trap: 6 env MYSQLD_PARENT_PID=9530 nohup /usr/local/opt/mysql/bin/mysqld --basedir=/usr/local/opt/mysql --datadir=/usr/local/var/mysql --plugin-dir=/usr/local/opt/mysql/lib/plugin --log-error=MACHINE.DOMAIN.TLD.err --pid-file=mMACHINE.DOMAIN.TLD.pid < /dev/null >> /usr/local/var/mysql/MACHINE.DOMAIN.TLD.err 2>&1
2022-10-07T17:06:21.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/MACHINE.DOMAIN.TLD.pid ended
When I check the error log file MACHINE.DOMAIN.TLD.err, I get the following output:
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 = 68222 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
0 mysqld 0x0000000101a676a9 my_print_stacktrace + 58
1 mysqld 0x00000001019e5473 handle_fatal_signal + 698
2 libsystem_platform.dylib 0x00007fff6d0b6b5d _sigtramp + 29
3 ??? 0x0000000103ae5380 0x0 + 4356723584
4 libsystem_c.dylib 0x00007fff6cf706a6 abort + 127
5 mysqld 0x0000000101c568b9 _Z23ut_dbg_assertion_failedPKcS0_m + 161
6 mysqld 0x0000000101c5929b _ZN2ib5fatalD2Ev + 91
7 mysqld 0x0000000101c592d9 _ZN2ib5fatalD1Ev + 9
8 mysqld 0x0000000101affc6d _ZL18fil_node_open_fileP10fil_node_t + 2435
9 mysqld 0x0000000101b0946b _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 191
10 mysqld 0x0000000101b09b71 _Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_ + 796
11 mysqld 0x0000000101ad0dfc _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 415
12 mysqld 0x0000000101ad0f53 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 56
13 mysqld 0x0000000101abc5d4 _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 971
14 mysqld 0x0000000101c464d4 _Z31trx_rseg_get_n_undo_tablespacesPm + 251
15 mysqld 0x0000000101c296ab _Z34innobase_start_or_create_for_mysqlv + 6608
16 mysqld 0x0000000101b589d3 _ZL13innobase_initPv + 3636
17 mysqld 0x00000001014cde2e _Z24ha_initialize_handlertonP13st_plugin_int + 78
18 mysqld 0x0000000101931b46 _ZL17plugin_initializeP13st_plugin_int + 81
19 mysqld 0x000000010193164a _Z40plugin_register_builtin_and_init_core_sePiPPc + 706
20 mysqld 0x00000001019da4e2 _Z11mysqld_mainiPPc + 2918
21 libdyld.dylib 0x00007fff6cecb3d5 start + 1
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.
2022-10-07T16:36:18.6NZ mysqld_safe mysqld from pid file /usr/local/var/mysql/MACHINE.DOMAIN.TLD.pid ended
2022-10-07T16:36:28.6NZ mysqld_safe Logging to '/usr/local/var/mysql/MACHINE.DOMAIN.TLD.err'.
2022-10-07T16:36:28.6NZ mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
2022-10-07T16:36:29.201378Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2022-10-07T16:36:29.201633Z 0 [Note] /usr/local/opt/mysql#5.7/bin/mysqld (mysqld 5.7.39) starting as process 8643 ...
2022-10-07T16:36:29.205774Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2022-10-07T16:36:29.207723Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-10-07T16:36:29.207755Z 0 [Note] InnoDB: Uses event mutexes
2022-10-07T16:36:29.207775Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-10-07T16:36:29.207791Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2022-10-07T16:36:29.210674Z 0 [Note] InnoDB: Number of pools: 1
2022-10-07T16:36:29.210835Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-10-07T16:36:29.212601Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-10-07T16:36:29.224493Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-10-07T16:36:29.273548Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2022-10-07 18:36:29 0x110a1e5c0 InnoDB: Assertion failure in thread 4574012864 in file ut0ut.cc line 921
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.
16:36:29 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.
I really hope someone can point me into the right direction. Maybe you cannot switch your databases back to 5.7 from 8?
Update
When I delete my v8 DB and try to run mysqld --initialize I get:
dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicuuc.70.dylib
Referenced from: /usr/local/bin/mysqld
Reason: image not found
zsh: abort mysqld --initialize
After restoring the whole /usr/local directory from Timemachine to a state before updating and upgrading Homebrew and its formulae, everything appears to be working again.
I do not know what caused my dysfunctional system. I suspect that, when I upgraded single formulae or when I installed a new formulae last week, something must have gone wrong.
The symptoms were, that single apps refused to run by complaining about the missing library /usr/local/opt/icu4c/lib/libicuuc.70.dylib. In fact icu4c had been upgraded to version 71.1.
Restoring the whole directory /usr/local returned all the apps, which I discovered as non working to a running state. I haven't run a brew update or brew upgrade yet.
I am running AMPPS 3.8 on OS X (Mojave v10.14)
After my HD unexpectedly died, I replaced the HD and reloaded my latest backup. MySQL does not load/run in AMMPPS :( My expectation was that the AMPPS would work as expected (Apache/php 7.1/MySQL would all run per usual).
In attempting to resolve the issue I have read through the AMPPS wiki, youtube, googling, and reading similar threads on stackOverflow, I attempted the following steps as listed below. MySQL did not turn on when i clicked on the on/off butto, nor did clicking the restart cause MySQL to start.
WHAT I ATTEMPTED:
1. Clicked on config icon: This now opens 'my.cnf', not 'my.ini'
2. added instruction line to my.cnf: innodb_force_recovery = 1
3. Save configuration
4. Clicked on/off switch (did nothing/Did not click/did not work)
5. Clicked restart icon
My MySql did not start.
OBSERVATION: when you click on the configuration tool (tool icon), it opens the file 'my.cnf' instead of 'my.ini'
mysql.err log
2020-02-24 10:38:28 1417 [Warning] You need to use --log-bin to make --binlog-format work.
2020-02-24 10:38:28 1417 [Note] Plugin 'FEDERATED' is disabled.
2020-02-24 10:38:28 1417 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-02-24 10:38:28 1417 [Note] InnoDB: The InnoDB memory heap is disabled
2020-02-24 10:38:28 1417 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-02-24 10:38:28 1417 [Note] InnoDB: Memory barrier is not used
2020-02-24 10:38:28 1417 [Note] InnoDB: Compressed tables use zlib 1.2.3
2020-02-24 10:38:28 1417 [Note] InnoDB: Not using CPU crc32 instructions
2020-02-24 10:38:28 1417 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-02-24 10:38:28 1417 [Note] InnoDB: Completed initialization of buffer pool
2020-02-24 10:38:28 1417 [Note] InnoDB: Highest supported file format is Barracuda.
2020-02-24 10:38:28 1417 [Note] InnoDB: 128 rollback segment(s) are active.
2020-02-24 10:38:28 1417 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 1140 in the data dictionary
InnoDB: but in file ./test#002emarvelchampionsuniverse/ma_images.ibd it is 1155!
2020-02-24 10:38:28 b088c000 InnoDB: Assertion failure in thread 2961752064 in file fil0fil.cc line 797
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
18:38:28 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.
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=16777216
read_buffer_size=262144
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 = 133617 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 0x30000
0 mysqld 0x00309dbe my_print_stacktrace + 46
1 mysqld 0x00148c35 handle_fatal_signal + 758
2 libsystem_platform.dylib 0xa7cd7b6e _sigtramp + 46
3 ??? 0xffffffff 0x0 + 4294967295
4 libsystem_c.dylib 0xa7b9162b abort + 133
5 mysqld 0x00377605 _ZL18fil_node_open_fileP10fil_node_tP12fil_system_tP11fil_space_t + 100
6 mysqld 0x003780ad _ZL23fil_node_prepare_for_ioP10fil_node_tP12fil_system_tP11fil_space_t + 147
7 mysqld 0x0037bea3 _Z6fil_iombmmmmmPvS_ + 513
8 mysqld 0x00354bf1 _ZL17buf_read_page_lowP7dberr_tbmmmmxm + 460
9 mysqld 0x00355134 _Z13buf_read_pagemmm + 88
10 mysqld 0x00346f06 _Z16buf_page_get_genmmmmP11buf_block_tmPKcmP5mtr_t + 488
11 mysqld 0x0033c88d _Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_tmmP9btr_cur_tmPKcmP5mtr_t + 1128
12 mysqld 0x0042100b _ZL17btr_pcur_open_lowP12dict_index_tmPK8dtuple_tmmP10btr_pcur_tPKcmP5mtr_t + 119
13 mysqld 0x0042117f _Z21row_search_on_row_refP10btr_pcur_tmPK12dict_table_tPK8dtuple_tP5mtr_t + 141
14 mysqld 0x0041f64c _ZL25row_purge_reposition_pcurmP12purge_node_tP5mtr_t + 116
15 mysqld 0x0041f73d _ZL34row_purge_remove_clust_if_poss_lowP12purge_node_tm + 194
16 mysqld 0x004203d3 _Z14row_purge_stepP9que_thr_t + 478
17 mysqld 0x003f9e0e _Z15que_run_threadsP9que_thr_t + 710
18 mysqld 0x00443413 _Z9trx_purgemmb + 2971
19 mysqld 0x00434bed _ZL12srv_do_purgemPm + 317
20 mysqld 0x00435759 srv_purge_coordinator_thread + 1055
21 libsystem_pthread.dylib 0xa7cdf63c _pthread_body + 137
22 libsystem_pthread.dylib 0xa7ce2833 _pthread_start + 82
23 libsystem_pthread.dylib 0xa7cde806 thread_start + 34
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.
I am a barista who enjoys attempting to write apps for fun and to help keep my mind sharp with early on set Alzheimer's disease, at best I am a novice. I do this to exercise my mind in an attempt to hold on to as much as I can for as long as I can. I am hoping to get MySQL working again if only once to export my local db to preserve what I have done.
Thank you for any and all help.
I am running Centos 6.4 on i686 PC and here is a problem with mysqld. It restarts all the time, look example. Sorry bad english.
service mysqld status
mysqld (pid 21563) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 21616) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 21667) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 21718) is running...
[root#ip mysql]# service mysqld status
mysqld dead but subsys locked
[root#ip mysql]# service mysqld status
mysqld dead but subsys locked
[root#ip mysql]# service mysqld status
mysqld (pid 21820) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 21922) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 21973) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 22026) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 22026) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 22128) is running...
[root#ip mysql]# service mysqld status
mysqld (pid 22179) is running...
Here is /etc/my.cnf:
[mysqld]
bind-address = 127.0.0.1
general_log = 1
general_log_file = /var/log/mysql/mysql.log
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
wait_timeout = 28800
max_allowed_packet = 32M
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
wait_timeout = 28800
max_allowed_packet = 32M
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
Look at the /var/log/mysqld.log:
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 0x30000
/usr/libexec/mysqld(my_print_stacktrace+0x2e) [0x84c6d3e]
/usr/libexec/mysqld(handle_fatal_signal+0x484) [0x82ec8b4]
[0xac3400]
[0xac3424]
/lib/libc.so.6(gsignal+0x51) [0x70f861]
/lib/libc.so.6(abort+0x17a) [0x71113a]
/usr/libexec/mysqld() [0x8396186]
/usr/libexec/mysqld(btr_cur_search_to_nth_level+0xabe) [0x839715e]
/usr/libexec/mysqld(row_search_index_entry+0x79) [0x8417949]
/usr/libexec/mysqld() [0x8416517]
/usr/libexec/mysqld(row_purge_step+0x5ab) [0x841779b]
/usr/libexec/mysqld(que_run_threads+0x535) [0x8404a45]
/usr/libexec/mysqld(trx_purge+0x375) [0x8432605]
/usr/libexec/mysqld(srv_master_thread+0x75b) [0x842a67b]
/lib/libpthread.so.0(+0x6b39) [0x6d0b39]
/lib/libc.so.6(clone+0x5e) [0x7c7ace]
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.
170621 20:14:38 mysqld_safe Number of processes running now: 0
170621 20:14:38 mysqld_safe mysqld restarted
170621 20:14:38 InnoDB: Initializing buffer pool, size = 8.0M
170621 20:14:38 InnoDB: Completed initialization of buffer pool
170621 20:14:38 InnoDB: Started; log sequence number 0 1965184248
170621 20:14:38 [Note] Event Scheduler: Loaded 0 events
170621 20:14:38 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
170621 20:14:39 InnoDB: Assertion failure in thread 2968296304 in file btr/btr0cur.c line 201
InnoDB: Failing assertion: btr_page_get_prev(get_page, mtr) == buf_frame_get_page_no(page)
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:14:39 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.
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=8384512
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 = 337742 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
And from mysql CLI sometimes I can connect and run queries:
mysql> show databases;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 1
Current database: *** NONE ***
+--------------------+
| Database |
+--------------------+
| information_schema |
| asterisk |
| asteriskcdrdb |
| drupal |
| drupal2 |
| drupal3 |
| drupal4test |
| mysql |
| statistics |
| test |
+--------------------+
10 rows in set (0.00 sec)
mysql> show databases;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
ERROR:
Can't connect to the server
mysql>
Any ideas?
Any information will be very good for me )
I have a Debian squeeze server that is supposed to run MySQL, but after a hard reboot it is having problems starting up. Attempting to start it using /etc/init.d/mysql start produces this snippet in syslog:
Oct 20 07:13:08 hyperion mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Oct 20 07:13:08 hyperion mysqld: 151020 7:13:08 [Note] Plugin 'FEDERATED' is disabled.
Oct 20 07:13:08 hyperion mysqld: 151020 7:13:08 InnoDB: Initializing buffer pool, size = 8.0M
Oct 20 07:13:08 hyperion mysqld: 151020 7:13:08 InnoDB: Completed initialization of buffer pool
Oct 20 07:13:08 hyperion mysqld: InnoDB: The log sequence number in ibdata files does not match
Oct 20 07:13:08 hyperion mysqld: InnoDB: the log sequence number in the ib_logfiles!
Oct 20 07:13:08 hyperion mysqld: 151020 7:13:08 InnoDB: Database was not shut down normally!
Oct 20 07:13:08 hyperion mysqld: InnoDB: Starting crash recovery.
Oct 20 07:13:08 hyperion mysqld: InnoDB: Reading tablespace information from the .ibd files...
Oct 20 07:13:08 hyperion mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Oct 20 07:13:08 hyperion mysqld: InnoDB: buffer...
Oct 20 07:13:08 hyperion mysqld: 151020 7:13:08 InnoDB: Started; log sequence number 0 150617369
Oct 20 07:13:08 hyperion mysqld: 151020 7:13:08 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
After googling the error I found that I had to repair a table by starting the server, then from another terminal access it and run the following:
mysql> use mysql
mysql> repair table host use_frm;
mysql> exit
However, already at the use mysql command, I get this wall of text in my mysqld terminal:
151020 7:50:03 [Note] Plugin 'FEDERATED' is disabled.
151020 7:50:03 InnoDB: Initializing buffer pool, size = 8.0M
151020 7:50:03 InnoDB: Completed initialization of buffer pool
151020 7:50:03 InnoDB: Started; log sequence number 0 150617379
151020 7:50:03 [Note] mysqld: ready for connections.
Version: '5.1.63-0+squeeze1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
mysqld: malloc.c:3097: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
05:51:07 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.
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=16777216
read_buffer_size=131072
max_used_connections=10
max_threads=151
thread_count=10
connection_count=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f98cdbcac30
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 = 7f98c59a7e88 thread_stack 0x30000
mysqld(my_print_stacktrace+0x29) [0x7f98ccc7a689]
mysqld(handle_fatal_signal+0x483) [0x7f98cca8ea53]
/lib/libpthread.so.0(+0xeff0) [0x7f98cc1e0ff0]
/lib/libc.so.6(gsignal+0x35) [0x7f98cac831b5]
/lib/libc.so.6(abort+0x180) [0x7f98cac85fc0]
/lib/libc.so.6(+0x71dda) [0x7f98cacc2dda]
/lib/libc.so.6(+0x74d2d) [0x7f98cacc5d2d]
/lib/libc.so.6(__libc_malloc+0x70) [0x7f98cacc7a30]
mysqld(my_malloc+0x32) [0x7f98ccc64372]
mysqld(alloc_root+0xd5) [0x7f98ccc64bc5]
mysqld(push_warning(THD*, MYSQL_ERROR::enum_warning_level, unsigned int, char const*)+0x194) [0x7f98cca14a84]
mysqld(my_message_sql+0x141) [0x7f98cc980c51]
mysqld(my_error+0xd8) [0x7f98ccc66118]
mysqld(open_table_def(THD*, st_table_share*, unsigned int)+0xeec) [0x7f98cc9dd95c]
mysqld(get_table_share(THD*, TABLE_LIST*, char*, unsigned int, unsigned int, int*)+0x230) [0x7f98cc9cbb00]
mysqld(+0x3c454b) [0x7f98cc9d254b]
mysqld(open_table(THD*, TABLE_LIST*, st_mem_root*, bool*, unsigned int)+0x7d5) [0x7f98cc9d3645]
mysqld(open_tables(THD*, TABLE_LIST**, unsigned int*, unsigned int)+0x6ee) [0x7f98cc9d437e]
mysqld(open_normal_and_derived_tables(THD*, TABLE_LIST*, unsigned int)+0x1e) [0x7f98cc9d451e]
mysqld(mysqld_list_fields(THD*, TABLE_LIST*, char const*)+0x20) [0x7f98ccab1f60]
mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x17f2) [0x7f98cc999a02]
mysqld(do_command(THD*)+0xea) [0x7f98cc999caa]
mysqld(handle_one_connection+0x236) [0x7f98cc98b796]
/lib/libpthread.so.0(+0x68ca) [0x7f98cc1d88ca]
/lib/libc.so.6(clone+0x6d) [0x7f98cad2092d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f98cdbd5610):
Connection ID (thread ID): 16
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.
I tried posting for help on the official forums, but it seems the moderators did not let my post through. My debugging skills are too inferior to figure out what is wrong and how to salvage data from the databases. I have been able to start up the server momentarily by skipping grant tables, but when I try to dump the databases using mysqldump --all-databases > backup.sql I hit another error:
mysqldump: Error 1194: Table 'wp_options' is marked as crashed and should be repaired when dumping table `wp_options` at row: 111
Any help is appreciated.
Today i was trying to import a database(~650MB) which failed because of my max packet size was too small.. While trying to fix this, for some reason the database got corrupted.
Now i have the following problem:
In PhpMyAdmin i try to drop the table which is corrupted and it returns the following:
Fout
SQL-query:
DROP DATABASE `database_name`
MySQL retourneerde:
#2013 - Lost connection to MySQL server during query
Every single other database works fine, exept for this one.
I tried several ways, even by putting innodb_force_recovery to 6 in my.cnf file.
Does someone ever experienced something like this?
The FULL error output is:
Markering - 27 nov. 2012 16:49:06
121127 16:49:18 InnoDB: Assertion failure in thread 4516245504 in file dict0dict.c line 2643
InnoDB: Failing assertion: for_table || ref_table
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:49:18 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.
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=16777216
read_buffer_size=262144
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 = 134066 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1010c9000
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 = 10d306ed8 thread_stack 0x40000
0 mysqld 0x000000010027a4fc my_print_stacktrace + 44�
1 mysqld 0x0000000100021134 handle_fatal_signal + 692�
2 libsystem_c.dylib 0x00007fff836038ea _sigtramp + 26�
3 mysqld 0x00000001002efd87 mtr_memo_push + 23�
4 libsystem_c.dylib 0x00007fff8365adce abort + 143�
5 mysqld 0x00000001002baf96 dict_foreign_add_to_cache + 998�
6 mysqld 0x00000001002c09c6 dict_load_foreigns + 1414�
7 mysqld 0x00000001002c2b5b dict_load_table + 1707�
8 mysqld 0x00000001003212b1 row_drop_database_for_mysql + 129�
9 mysqld 0x000000010030b322 _ZL22innobase_drop_databaseP10handlertonPc + 226�
10 mysqld 0x0000000100022601 _ZL17dropdb_handlertonP3THDP13st_plugin_intPv + 33�
11 mysqld 0x0000000100178f7d _Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_ + 845�
12 mysqld 0x0000000100140de3 _Z11mysql_rm_dbP3THDPcbb + 1859�
13 mysqld 0x0000000100167143 _Z21mysql_execute_commandP3THD + 13491�
14 mysqld 0x000000010016a386 _Z11mysql_parseP3THDPcjP12Parser_state + 294�
15 mysqld 0x000000010016b49d _Z16dispatch_command19enum_server_commandP3THDPcj + 1709�
16 mysqld 0x000000010016c387 _Z10do_commandP3THD + 231�
17 mysqld 0x000000010020b581 _Z24do_handle_one_connectionP3THD + 353�
18 mysqld 0x000000010020b639 handle_one_connection + 73�
19 libsystem_c.dylib 0x00007fff83615742 _pthread_start + 327�
20 libsystem_c.dylib 0x00007fff83602181 thread_start + 13�
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (10e002810): is an invalid pointer
Connection ID (thread ID): 9
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.
121127 16:49:19 mysqld_safe mysqld restarted
121127 16:49:19 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitive
121127 16:49:19 [Note] Plugin 'FEDERATED' is disabled.
121127 16:49:19 InnoDB: The InnoDB memory heap is disabled
121127 16:49:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121127 16:49:19 InnoDB: Compressed tables use zlib 1.2.3
121127 16:49:19 InnoDB: Initializing buffer pool, size = 128.0M
121127 16:49:19 InnoDB: Completed initialization of buffer pool
121127 16:49:19 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
121127 16:49:19 InnoDB: Waiting for the background threads to start
121127 16:49:20 InnoDB: 1.1.8 started; log sequence number 0
121127 16:49:20 InnoDB: !!! innodb_force_recovery is set to 6 !!!
121127 16:49:20 [Note] Event Scheduler: Loaded 0 events
121127 16:49:20 [Note] /Applications/MAMP/Library/bin/mysqld: ready for connections.
Version: '5.5.25' socket: '/Applications/MAMP/tmp/mysql/mysql.sock' port: 0 Source distribution
If you have tried each of the innodb_force_recovery values, (3 stops transactions being rolled back or forward), then I can only point you at the following
To cut to the chase, the person on this web page ended up deleteing the innodb files.
Until the end I don’t find a clear solution to this problem … but if you are on a testing environment you can just delete ibdata1 and ib_logfile0, ib_logfile1 and restart the server. This worked in my case.
http://www.randombugs.com/linux/crash-innodb-table.html
Obviously, if you have a load of other databases, this will involve backing up and restoring those aswell. If you find any other way around this, I suggest you try it first.
Percona provide a set of data recovery tools, but in your case the data is not the problem
http://code.google.com/p/innodb-tools/
https://launchpad.net/percona-data-recovery-tool-for-innodb