Why is there no connection to mysql in openserver?

Question

MySQL

Hello! I'm trying to login to phpmyadmin, but it gives an error mysqli_real_connect(): (HY000/2002). The openserver log shows this:

spoiler

2019-07-17 11:07:12 0 [Note] c:\ospanel\modules\database\MariaDB-10.3-x64\bin\mysqld.exe (mysqld 10.3.13-MariaDB) starting as process 1148 ...
2019-07-17 11:07:12 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-07-17 11:07:12 0 [Note] InnoDB: Uses event mutexes
2019-07-17 11:07:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-07-17 11:07:12 0 [Note] InnoDB: Number of pools: 1
2019-07-17 11:07:12 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-07-17 11:07:12 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-07-17 11:07:12 0 [Note] InnoDB: Completed initialization of buffer pool
2019-07-17 11:07:12 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=84399922
2019-07-17 11:07:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-07-17 11:07:23 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-07-17 11:07:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-07-17 11:07:23 0 [Note] InnoDB: Setting file 'c:\ospanel\userdata\MariaDB-10.3-x64\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-07-17 11:07:23 0 [Note] InnoDB: File 'c:\ospanel\userdata\MariaDB-10.3-x64\ibtmp1' size is now 12 MB.
2019-07-17 11:07:23 0 [Note] InnoDB: Waiting for purge to start
2019-07-17 11:07:23 0x279c InnoDB: Assertion failure in file d:\winx64-packages\build\src\storage\innobase\include\fut0lst.ic line 85
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-...
InnoDB: about forcing recovery.
190717 11:07:23 [ERROR] mysqld got exception 0x80000003 ;
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
key_buffer_size=26214400
read_buffer_size=2097152
max_used_connections=0
max_threads=65537
thread_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 29271 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x24ef7853dd8
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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
2019-07-17 11:07:23 0 [Note] InnoDB: 10.3.13 started; log sequence number 84399931; transaction id 7599329634443862051
2019-07-17 11:07:23 0 [Note] InnoDB: Loading buffer pool(s) from c:\ospanel\userdata\MariaDB-10.3-x64\ib_buffer_pool
mysqld.exe!parse_user()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 1
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
The manual page at dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2019-07-17 11:07:23 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-07-17 11:07:23 0 [Note] Server socket created on IP: '127.0.0.1'.

What could be the problem?

Answer 1

Try to restore innodb by specifying in mysql.ini
innodb_force_recovery = 2