When i start Apache & MySQL it runs smoothly but when i try to access my website it stops MySQL and throws error.
1:31:29 PM [mysql] Error: MySQL shutdown unexpectedly.
1:31:29 PM [mysql] This may be due to a blocked port, missing dependencies,
1:31:29 PM [mysql] improper privileges, a crash, or a shutdown by another method.
1:31:29 PM [mysql] Press the Logs button to view error logs and check
1:31:29 PM [mysql] the Windows Event Viewer for more clues
1:31:29 PM [mysql] If you need more help, copy and post this
1:31:29 PM [mysql] entire log window on the forums
```
2020-07-02 13:51:05 1c24 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2020-07-02 13:51:05 7204 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2020-07-02 13:51:05 7204 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2020-07-02 13:51:05 7204 [Note] InnoDB: The InnoDB memory heap is disabled
2020-07-02 13:51:05 7204 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-07-02 13:51:05 7204 [Note] InnoDB: Memory barrier is not used
2020-07-02 13:51:05 7204 [Note] InnoDB: Compressed tables use zlib 1.2.3
2020-07-02 13:51:05 7204 [Note] InnoDB: Using generic crc32 instructions
2020-07-02 13:51:05 7204 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2020-07-02 13:51:05 7204 [Note] InnoDB: Completed initialization of buffer pool
2020-07-02 13:51:05 7204 [Note] InnoDB: Highest supported file format is Barracuda.
2020-07-02 13:51:05 7204 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2917356559
2020-07-02 13:51:05 7204 [Note] InnoDB: Database was not shutdown normally!
2020-07-02 13:51:05 7204 [Note] InnoDB: Starting crash recovery.
2020-07-02 13:51:05 7204 [Note] InnoDB: Reading tablespace information from the .ibd files...
2020-07-02 13:51:06 7204 [Note] InnoDB: Restoring possible half-written data pages
2020-07-02 13:51:06 7204 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2917374181
2020-07-02 13:51:07 7204 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
2020-07-02 13:51:08 7204 [Note] InnoDB: 128 rollback segment(s) are active.
2020-07-02 13:51:08 7204 [Note] InnoDB: Waiting for purge to start
2020-07-02 13:51:08 7204 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 2917374181
2020-07-02 13:51:08 1804 [Note] InnoDB: Dumping buffer pool(s) not yet started
2020-07-02 13:51:08 7204 [Note] Plugin 'FEEDBACK' is disabled.
2020-07-02 13:51:08 7204 [Note] Server socket created on IP: '::'.
2020-07-02 13:51:08 7204 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.16-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2020-07-02 13:51:09 1884 InnoDB: Assertion failure in thread 6276 in file fsp0fsp.cc line 1763
InnoDB: Failing assertion: n != ULINT_UNDEFINED
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.
200702 13:51:09 [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.1.16-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=1
max_threads=1001
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787100 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x84571e0
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!my_wildcmp_mb_bin()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?ha_update_row@handler@@QAEHPBEPAE@Z()
mysqld.exe!?mysql_update@@YAHPAVTHD@@PAUTABLE_LIST@@AAV?$List@VItem@@@@2PAVItem@@IPAUst_order@@_KW4enum_duplicates@@_NPA_K8@Z()
mysqld.exe!?mysql_execute_command@@YAHPAVTHD@@@Z()
mysqld.exe!?mysql_parse@@YAXPAVTHD@@PADIPAVParser_state@@@Z()
mysqld.exe!?dispatch_command@@YA_NW4enum_server_command@@PAVTHD@@PADI@Z()
mysqld.exe!?do_command@@YA_NPAVTHD@@@Z()
mysqld.exe!?threadpool_process_request@@YAHPAVTHD@@@Z()
mysqld.exe!?init_io@@YAHPAUconnection_t@@PAVTHD@@@Z()
KERNEL32.DLL!SetUserGeoName()
ntdll.dll!RtlInitializeHandleTable()
ntdll.dll!TpCallbackIndependent()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x83980a0): UPDATE `wp_options` SET `option_value` = '1593678099' WHERE `option_name` = '_transient_timeout__redux_activation_redirect'
Connection ID (thread ID): 2
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=off
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.
``
