mysqldump got errors, Lost connection to MySQL server during query - mysql

When i am use mysqldump -uroot -p xxx > xxx.sql, i got some errors, 'mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table GAMES at row: 20826'.
Then i checked the mysql error logs, i found the errors below. I search lots of sites in google but got nothing.
Anyone who can help me with this, thank you!
2018-07-31 00:21:04 0x7fb3cc0ab700 InnoDB: Assertion failure in thread 140410199127808 in file btr0pcur.cc line 452
InnoDB: Failing assertion: page_is_comp(next_page) == page_is_comp(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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:21:04 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=16777216
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 = 76387 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fb3a4012330
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 = 7fb3cc0aae70 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe907ab]
/usr/sbin/mysqld(handle_fatal_signal+0x489)[0x789b49]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fb3e79ca390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fb3e6d83428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fb3e6d8502a]
/usr/sbin/mysqld[0x75f3e0]
/usr/sbin/mysqld(_Z26btr_pcur_move_to_next_pageP10btr_pcur_tP5mtr_t+0x1c8)[0x114e6f8]
/usr/sbin/mysqld[0x75cfbf]
/usr/sbin/mysqld(_Z15row_search_mvccPh15page_cur_mode_tP14row_prebuilt_tmm+0x11e5)[0x1099745]
/usr/sbin/mysqld(_ZN11ha_innobase13general_fetchEPhjj+0x6a)[0xf87a7a]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0xfc)[0x7d961c]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x35)[0xbb3445]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP7QEP_TABb+0x13e)[0xc23ffe]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x3c8)[0xc1cd18]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x233)[0xc8e753]
/usr/sbin/mysqld[0x7533a8]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x492e)[0xc506ee]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3ad)[0xc52b3d]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x102a)[0xc53c7a]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1c7)[0xc55137]
/usr/sbin/mysqld(handle_connection+0x288)[0xd16788]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xec9294]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fb3e79c06ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb3e6e5541d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fb3a404ae60): is an invalid pointer
Connection ID (thread ID): 4
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.
2018-07-30T16:21:04.660409Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2018-07-30T16:21:04.660458Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2018-07-30T16:21:04.840982Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-07-30T16:21:04.842849Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.22-0ubuntu0.16.04.1) starting as process 26568 ...
2018-07-30T16:21:04.847280Z 0 [Note] InnoDB: PUNCH HOLE support available
2018-07-30T16:21:04.847312Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-07-30T16:21:04.847319Z 0 [Note] InnoDB: Uses event mutexes
2018-07-30T16:21:04.847324Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-07-30T16:21:04.847331Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-07-30T16:21:04.847336Z 0 [Note] InnoDB: Using Linux native AIO
2018-07-30T16:21:04.847618Z 0 [Note] InnoDB: Number of pools: 1
2018-07-30T16:21:04.847762Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-07-30T16:21:04.849397Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-07-30T16:21:04.857825Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-07-30T16:21:04.860275Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-07-30T16:21:04.872370Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-07-30T16:21:04.892980Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 5386460686
2018-07-30T16:21:04.893001Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 5386460695
2018-07-30T16:21:04.893008Z 0 [Note] InnoDB: Database was not shutdown normally!
2018-07-30T16:21:04.893013Z 0 [Note] InnoDB: Starting crash recovery.
2018-07-30T16:21:05.008438Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-07-30T16:21:05.008468Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-07-30T16:21:05.008507Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-07-30T16:21:05.103402Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-07-30T16:21:05.104128Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-07-30T16:21:05.104147Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-07-30T16:21:05.105002Z 0 [Note] InnoDB: 5.7.22 started; log sequence number 5386460695
2018-07-30T16:21:05.105371Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2018-07-30T16:21:05.106533Z 0 [Note] Plugin 'FEDERATED' is disabled.
2018-07-30T16:21:05.112425Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2018-07-30T16:21:05.112600Z 0 [Warning] CA certificate ca.pem is self signed.
2018-07-30T16:21:05.114984Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2018-07-30T16:21:05.115009Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2018-07-30T16:21:05.115029Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2018-07-30T16:21:05.121314Z 0 [Note] Event Scheduler: Loaded 0 events
2018-07-30T16:21:05.122659Z 0 [Note] InnoDB: Buffer pool(s) load completed at 180731 0:21:05
2018-07-30T16:21:05.122807Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.22-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2018-07-30T16:21:05.661985Z 2 [Note] Access denied for user 'root'#'localhost' (using password: NO)

Suggestions to consider for your my.cnf or my.ini [mysqld] section
SELECT ##thread_cache_size; # will give you current setting
SELECT ##innodb_buffer_pool_size; # will give you current setting
Multiply each by 1.3 and set with
SET GLOBAL thread_cache_size=<calculated-size>; # use rounded UP whole numbers
SET GLOBAL innodb_buffer_pool_size=<calculated-size>;
or if you have an OLD VERSION of MySQL, you must change in your
my.cnf or my.ini, shutdown/restart.
Let us know how it goes, please.
For additional assistance, view profile, Network Profile, for contact info including Skype ID. Thanks

Related

Lost connect to MySQL server during query

I have an Innodb database which have a big table with many rows. Once I'm trying to access the data or run any query(like "check table_name") against this specific table mysql crashes(restarts) and I'm getting the error:
ERROR 2013 (HY000): Lost connection to MySQL server during query
I have already tried to increase max_packetsize and the net_timeouts flags.
Any help will be appreciated, Thanks!
Edit:
Crash log:
2022-12-30T16:25:56.676880Z 208 [ERROR] InnoDB: In pages [page id: space=372, pa ge number=11135] and [page id: space=372, page number=11136] of index `GEN_CLUST _INDEX` of table `SHAS_2015_NEW`.`b_media_21_646_0000_11925`
InnoDB: broken FIL_PAGE_NEXT or FIL_PAGE_PREV links
2022-12-30T16:25:56.676925Z 208 [ERROR] InnoDB: In pages [page id: space=372, pa ge number=11135] and [page id: space=372, page number=11136] of index `GEN_CLUST _INDEX` of table `SHAS_2015_NEW`.`b_media_21_646_0000_11925`
InnoDB: 'compact' flag mismatch
2022-12-30T16:25:56.676936Z 208 [ERROR] InnoDB: Page index id 0 != data dictiona ry index id 577
2022-12-30 18:25:56 0x7fa1384e9700 InnoDB: Assertion failure in thread 14033041 1136768 in file btr0btr.cc line 4710
InnoDB: Failing assertion: !page_is_empty(page) || (level == 0 && page_get_page_ no(page) == dict_index_get_page(index))
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:25:56 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=16777216
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 = 76388 K b ytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fa0f81dd110
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 = 7fa1384e8e70 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8e68b]
/usr/sbin/mysqld(handle_fatal_signal+0x36f)[0x77524f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fa67f45d390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fa67e816438]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fa67e81803a]
/usr/sbin/mysqld[0x74a77c]
/usr/sbin/mysqld[0x10dd73d]
/usr/sbin/mysqld(_Z18btr_validate_indexP12dict_index_tPK5trx_tb+0x264)[0x10dec34 ]
/usr/sbin/mysqld(_ZN11ha_innobase5checkEP3THDP15st_ha_check_opt+0x278)[0xf2a378]
/usr/sbin/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0x7b)[0x7cd71b]
/usr/sbin/mysqld[0xdb48f4]
/usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0x97)[0xdb5497]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x2160)[0xc42570]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3dd)[0xc473ad]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11a 0)[0xc48610]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1c7)[0xc49ae7]
/usr/sbin/mysqld(handle_connection+0x290)[0xd0e140]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xeb03e4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fa67f4536ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa67e8e851d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa0f8072240): check table b_media_21_646_0000_11925
Connection ID (thread ID): 208
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.
2022-12-30T16:25:56.970335Z 0 [Warning] Changed limits: max_open_files: 1024 (re quested 5000)
2022-12-30T16:25:56.970397Z 0 [Warning] Changed limits: table_open_cache: 431 (r equested 2000)
2022-12-30T16:25:57.145883Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see doc umentation for more details).
2022-12-30T16:25:57.148901Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16 .04.1-log) starting as process 9454 ...
2022-12-30T16:25:57.153242Z 0 [Note] InnoDB: PUNCH HOLE support available
2022-12-30T16:25:57.153267Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-12-30T16:25:57.153272Z 0 [Note] InnoDB: Uses event mutexes
2022-12-30T16:25:57.153276Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-12-30T16:25:57.153283Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2022-12-30T16:25:57.153286Z 0 [Note] InnoDB: Using Linux native AIO
2022-12-30T16:25:57.153526Z 0 [Note] InnoDB: Number of pools: 1
2022-12-30T16:25:57.153643Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-12-30T16:25:57.155093Z 0 [Note] InnoDB: Initializing buffer pool, total siz e = 20G, instances = 8, chunk size = 128M
2022-12-30T16:25:58.482523Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-12-30T16:25:58.719968Z 0 [Note] InnoDB: If the mysqld execution user is aut horized, page cleaner thread priority can be changed. See the man page of setpri ority().
2022-12-30T16:25:58.744995Z 0 [Note] InnoDB: Highest supported file format is Ba rracuda.
2022-12-30T16:25:58.915826Z 0 [Note] InnoDB: Log scan progressed past the checkp oint lsn 10408206134578
2022-12-30T16:25:58.915857Z 0 [Note] InnoDB: Doing recovery: scanned up to log s equence number 10408206134587
2022-12-30T16:25:58.915862Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-12-30T16:25:58.915872Z 0 [Note] InnoDB: Starting crash recovery.
2022-12-30T16:25:59.270028Z 0 [Note] InnoDB: Last MySQL binlog file position 0 1 862900, file name mysql-bin.000001
2022-12-30T16:26:00.014203Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-12-30T16:26:00.014242Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-12-30T16:26:00.014281Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-12-30T16:26:00.075009Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-12-30T16:26:00.076863Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2022-12-30T16:26:00.076904Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2022-12-30T16:26:00.077640Z 0 [Note] InnoDB: Waiting for purge to start
2022-12-30T16:26:00.127880Z 0 [Note] InnoDB: 5.7.33 started; log sequence number 10408206134587
2022-12-30T16:26:00.128095Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-12-30T16:26:00.128605Z 0 [Note] Plugin 'FEDERATED' is disabled.
2022-12-30T16:26:00.138272Z 0 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
2022-12-30T16:26:00.138325Z 0 [Note] Starting crash recovery...
2022-12-30T16:26:00.138384Z 0 [Note] Crash recovery finished.
If I'm Using select with Limit statement then I can select up to 681,000 rows

MAMP not working after Macbook crashes. How do I restore MAMP and my databases?

My Macbook crashed and now MAMP (latest version v6.6.3) is not working anymore.
I was able to log in to MYSQL only over command line with
/Applications/MAMP/bin/startMysql.sh
/Applications/MAMP/bin/startApache.sh
But my databases are gone.
However, I can see in the error log that there is an issue with one of my databases (drupal8). So the database is still somewhere? But why can't I see it?
2022-10-12T02:36:17.6NZ mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'.
2022-10-12T02:36:17.6NZ mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql57
mysqld: [Warning] World-writable config file '/Applications/MAMP/tmp/mysql/my.cnf' is ignored.
2022-10-12T02:36:17.347806Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-10-12T02:36:17.349461Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2022-10-12T02:36:17.350939Z 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.7.34) starting as process 62124 ...
2022-10-12T02:36:17.363631Z 0 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql57/ is case insensitive
2022-10-12T02:36:17.373326Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-10-12T02:36:17.373353Z 0 [Note] InnoDB: Uses event mutexes
2022-10-12T02:36:17.373365Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2022-10-12T02:36:17.373375Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-10-12T02:36:17.375559Z 0 [Note] InnoDB: Number of pools: 1
2022-10-12T02:36:17.378292Z 0 [Note] InnoDB: Using CPU crc32 instructions
2022-10-12T02:36:17.380118Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2022-10-12T02:36:17.390613Z 0 [Note] InnoDB: Completed initialization of buffer pool
2022-10-12T02:36:17.415180Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-10-12T02:36:17.418235Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 73772091416
2022-10-12T02:36:17.418356Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 73772146375
2022-10-12T02:36:17.422286Z 0 [Note] InnoDB: Database was not shutdown normally!
2022-10-12T02:36:17.422329Z 0 [Note] InnoDB: Starting crash recovery.
2022-10-12T02:36:17.467479Z 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 2022-10-12T02:36:17.468325Z 0 [ERROR] InnoDB: Trying to access page number 32 in space 580, space name drupal8/cache_menu, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
2022-10-12T02:36:17.468359Z 0 [ERROR] InnoDB: Server exits.
2022-10-12T02:36:17.6NZ mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
When I open PhpMyAdmin I get an error as well:
PHP 5.5+ is required.
Currently installed version is: 5.4.45
But I have PHP set to 7.4.21 in MAMP.

MySql startup error ' ERROR! The server quit without updating PID file'

I have tried every link that is on S.O but still getting the same outcome every time I try to start MySQL. Following is the log from the .err file.
2018-01-07T06:58:11.729500Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2018-01-07T06:58:11.731659Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-07T06:58:11.731673Z 0 [Note] InnoDB: Uses event mutexes
2018-01-07T06:58:11.731679Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-01-07T06:58:11.731682Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-07T06:58:11.731969Z 0 [Note] InnoDB: Number of pools: 1
2018-01-07T06:58:11.732068Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-01-07T06:58:11.733672Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-01-07T06:58:11.745339Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-01-07T06:58:11.761905Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-07T06:58:11.906535Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-01-07T06:58:11.906692Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-01-07T06:58:11.918639Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-01-07T06:58:11.919925Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2018-01-07T06:58:11.919938Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2018-01-07T06:58:11.920116Z 0 [Note] InnoDB: Waiting for purge to start
2018-01-07T06:58:11.974340Z 0 [Note] InnoDB: 5.7.20 started; log sequence number 129183358
2018-01-07T06:58:11.974571Z 0 [Note] InnoDB: Loading buffer pool(s) from /usr/local/var/mysql/ib_buffer_pool
2018-01-07T06:58:11.974744Z 0 [Note] Plugin 'FEDERATED' is disabled.
2018-01-07T06:58:11.974853Z 0 [Note] InnoDB: Buffer pool(s) load completed at 180107 12:28:11
2018-01-07T06:58:11.983233Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2018-01-07T06:58:11.983254Z 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
2018-01-07T06:58:11.983981Z 0 [Warning] CA certificate ca.pem is self signed.
2018-01-07T06:58:11.984032Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
2018-01-07T06:58:11.989041Z 0 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2018-01-07T06:58:11.989070Z 0 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2018-01-07T06:58:11.989136Z 0 [Note] Server socket created on IP: '127.0.0.1'.
2018-01-07T06:58:11.989166Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2018-01-07T06:58:11.989169Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2018-01-07T06:58:11.989199Z 0 [ERROR] Aborting
It looks like you have some other software that is using the port 3306. MySQL uses this port, but it's failing to bind to it because it is in use. End the other software and try to launch MySQL again.
If you need to have the other software running at the same time with MySQL, you have to change the default port in one of them to some other unused port.
To change the port in MySQL. If you're on Windows, find the my.ini file for MySQL installation, open this file in a text editor and look for this section:
# The TCP/IP Port the MySQL Server will listen on
port=3306
Then change the number of the port, save the file, and restart the MySQL service.

PHPMyadmin Error: #2002 - No such file or directory<br />The server is not responding

I have phpMyAdmin installed on Ubuntu 16.04 Lamp Server on an Oracle VM. When I try to enter phpMyAdmin via http://localhost/phpmyadmin, I receive the following error:
Error: #2002 - No such file or directoryThe server is not responding
After reading previous threads, I have tried to unsuccessfully reinstall mysql-server to no avail. The MySQL error log in /var/log/... contains the following:
2017-01-22T16:18:06.214161Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
2017-01-22T16:18:06.214326Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
2017-01-22T16:18:06.536519Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-22T16:18:06.543467Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.17-0ubuntu0.16.04.1) starting as process 3647 ...
2017-01-22T16:18:06.571026Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-01-22T16:18:06.571095Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-22T16:18:06.571106Z 0 [Note] InnoDB: Uses event mutexes
2017-01-22T16:18:06.571120Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-01-22T16:18:06.571130Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-01-22T16:18:06.571139Z 0 [Note] InnoDB: Using Linux native AIO
2017-01-22T16:18:06.571731Z 0 [Note] InnoDB: Number of pools: 1
2017-01-22T16:18:06.571975Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-01-22T16:18:06.577202Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-22T16:18:06.625715Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-22T16:18:06.631873Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-01-22T16:18:06.647876Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-01-22T16:18:06.736500Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-01-22T16:18:06.736633Z 0 [Note] InnoDB: Setting file \'./ibtmp1\' size to 12 MB. Physically writing the file full; Please wait ...
2017-01-22T16:18:07.143892Z 0 [Note] InnoDB: File \'./ibtmp1\' size is now 12 MB.
2017-01-22T16:18:07.145163Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-01-22T16:18:07.145188Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2017-01-22T16:18:07.150769Z 0 [Note] InnoDB: Waiting for purge to start
2017-01-22T16:18:07.201406Z 0 [Note] InnoDB: 5.7.17 started; log sequence number 16765716
2017-01-22T16:18:07.207484Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2017-01-22T16:18:07.208190Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170122 17:18:07
2017-01-22T16:18:07.208412Z 0 [Note] Plugin \'FEDERATED\' is disabled.
2017-01-22T16:18:07.229256Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2017-01-22T16:18:07.229286Z 0 [Note] Server hostname (bind-address): \'127.0.0.1\'; port: 3306
2017-01-22T16:18:07.229302Z 0 [Note] - \'127.0.0.1\' resolves to \'127.0.0.1\';
2017-01-22T16:18:07.229351Z 0 [Note] Server socket created on IP: \'127.0.0.1\'.
2017-01-22T16:18:07.230207Z 0 [ERROR] Fatal error: Can\'t open and lock privilege tables: Incorrect file format \'user\'
2017-01-22T16:18:07.230287Z 0 [ERROR] Aborting
');
I have tried to apply various solutions including this - MySQL Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
Unfortunately, I am not able to access Mysql and therefore unable to follow the solution. $ sudo mysqld --skip-grant-tables does not allow me to access it.

Issue with MySql installation on Windows 10

UPDATE: Solved! Here is my solution:
Todays systems are often running on a disk which is formatted in GPT. This is because Windows 10 needs such a partition to be installed. The problem is that MySql cant deal with this partition style and so it crashes. Here is my workaround:
Create a virtual disk: manual here
Format this VHD with MBR
Install MySql custom on your new VHD (dont forget to create a user
for DB)
This should be it! :)
I try to install MySql on my Dell XPS 13 9360 with Windows 10. When it comes to starting the server as a service, the service cannot start. As so far this problem is widely known and there are many attempts to solve this issue. Unfortunately non of these work for me. Here is what I tried:
insert innodb_flush_method=normal into my.ini
change service to register at local account
check firewall for port rules
So my question: Does anybody experience the same issue and knows a way to get it running? You would help me really so much :)
Here is my error log:
2017-01-23T14:11:44.458654Z 0 [Warning] option 'new': boolean value 't' wasn't recognized. Set to OFF.
2017-01-23T14:11:44.458654Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-23T14:11:44.458654Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-23T14:11:44.459156Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 5340 ...
2017-01-23T14:11:44.468178Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-23T14:11:44.469212Z 0 [Note] InnoDB: Uses event mutexes
2017-01-23T14:11:44.469713Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-23T14:11:44.470716Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-23T14:11:44.471217Z 0 [Note] InnoDB: Number of pools: 1
2017-01-23T14:11:44.471719Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-23T14:11:44.474727Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-23T14:11:44.481212Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-23T14:11:44.546889Z 0 [ERROR] InnoDB: Header page consists of zero bytes in datafile: .\ibdata1, Space ID:0, Flags: 0. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2017-01-23T14:11:44.548924Z 0 [ERROR] InnoDB: Corrupted page [page id: space=0, page number=0] of datafile '.\ibdata1' could not be found in the doublewrite buffer.
2017-01-23T14:11:44.550425Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
2017-01-23T14:11:44.771283Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-23T14:11:44.772134Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-23T14:11:44.772635Z 0 [ERROR] Failed to initialize plugins.
2017-01-23T14:11:44.773135Z 0 [ERROR] Aborting
2017-01-23T14:11:44.773636Z 0 [Note] Binlog end
2017-01-23T14:11:44.774138Z 0 [Note] Shutting down plugin 'CSV'
2017-01-23T14:11:44.774640Z 0 [Note] mysqld: Shutdown complete
thank you in advance!
#Bill Karwin :
OK, so after removing the tablespace the result is this:
2017-01-23T15:39:39.874463Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-23T15:39:39.874965Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 624 ...
2017-01-23T15:39:39.880480Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-23T15:39:39.880980Z 0 [Note] InnoDB: Uses event mutexes
2017-01-23T15:39:39.881484Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-23T15:39:39.882022Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-23T15:39:39.882986Z 0 [Note] InnoDB: Number of pools: 1
2017-01-23T15:39:39.882986Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-23T15:39:39.885491Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-23T15:39:39.891024Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-23T15:39:39.914631Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2017-01-23T15:39:39.915071Z 0 [ERROR] InnoDB: redo log file '.\ib_logfile1' exists. Creating system tablespace with existing redo log files is not recommended. Please delete all redo log files before creating new system tablespace.
2017-01-23T15:39:39.916074Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again.
2017-01-23T15:39:40.132668Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-01-23T15:39:40.132668Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-01-23T15:39:40.134090Z 0 [ERROR] Failed to initialize plugins.
2017-01-23T15:39:40.134590Z 0 [ERROR] Aborting
2017-01-23T15:39:40.135594Z 0 [Note] Binlog end
2017-01-23T15:39:40.136094Z 0 [Note] Shutting down plugin 'CSV'
2017-01-23T15:39:40.136595Z 0 [Note] mysqld: Shutdown complete
new error after deleting logdata1 and 0:
2017-01-23T15:55:22.158765Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-01-23T15:55:22.159266Z 0 [Note] mysqld (mysqld 5.7.17) starting as process 2880 ...
2017-01-23T15:55:22.165783Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-01-23T15:55:22.165783Z 0 [Note] InnoDB: Uses event mutexes
2017-01-23T15:55:22.165783Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-01-23T15:55:22.166284Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-23T15:55:22.166284Z 0 [Note] InnoDB: Number of pools: 1
2017-01-23T15:55:22.166786Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-01-23T15:55:22.169292Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-23T15:55:22.178820Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-23T15:55:22.202407Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2017-01-23T15:55:22.203383Z 0 [Note] InnoDB: Setting file '.\ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2017-01-23T15:55:22.249691Z 0 [Note] InnoDB: File '.\ibdata1' size is now 12 MB.
2017-01-23T15:55:22.263685Z 0 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
2017-01-23T15:55:22.342287Z 0 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
2017-01-23T15:55:22.452340Z 0 [ERROR] InnoDB: Operating system error number 87 in a file operation.
2017-01-23T15:55:22.452842Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
2017-01-23T15:55:22.453346Z 0 [ERROR] InnoDB: File .\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
2017-01-23T15:55:22.453346Z 0 [ERROR] InnoDB: Cannot continue operation.
Found the solution:
Todays systems are often running on a disk which is formatted in GPT. This is because Windows 10 needs such a partition to be installed. The problem is that MySql cant deal with this partition style and so it crashes. Here is my workaround:
Create a virtual disk: manual here
Format this VHD with MBR
Install MySql custom on your new VHD (dont forget to create a user for DB)
This should be it! :)