What follows is a circumvention / repair for Windows/XAMPP users. Otherwise the problem may later recur even after a complete uninstall/re-install of 7.3.7 for example. General advice seems to be to cut your losses and downgrade your XAMPP to 7.3.5 Problem occurs after user password changes - often user root. This is almost certainly a known bug in mariaDB (ie mySQL). Tried already to repair, but the mySQL Service won't even start, so I'm kinda helpless. 23:47:14 0 Fatal error: Can't open and lock privilege tables: Index for table 'user' is corrupt try to repair it 23:47:14 0 mysqld.exe: Index for table '.\mysql\user' is corrupt try to repair it 23:47:14 0 mysqld.exe: Table '.\mysql\user' is marked as crashed and should be repaired 23:47:14 0 Plugin 'FEEDBACK' is disabled. 23:47:14 0 InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool 23:47:14 0 InnoDB: Waiting for purge to start 23:47:14 0 InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB. Physically writing the file full Please wait. 23:47:14 0 InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. 23:47:14 0 InnoDB: Creating shared tablespace for temporary tables 23:47:14 0 InnoDB: Removed temporary tablespace data file: "ibtmp1" 23:47:14 0 InnoDB: 128 out of 128 rollback segments are active. 23:47:13 0 InnoDB: Starting crash recovery from checkpoint LSN=1819402 23:47:13 0 InnoDB: Completed initialization of buffer pool 23:47:13 0 InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M 23:47:13 0 InnoDB: Using SSE2 crc32 instructions 23:47:13 0 InnoDB: Compressed tables use zlib 1.2.11 This is the MySQL Error Log: 23:47:13 0 InnoDB: Uses event mutexes Today I wanted to continue working on it but xampp control panel gave me some weir errors. 17:08:48 9368 Plugin 'FEEDBACK' is disabled.I used Xampp yesterday to create some simple Web-based utility tool. 17:08:48 9368 Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 17:08:48 9368 Plugin 'InnoDB' init function returned error. But be careful: do not remove old data files which contain your precious data! InnoDB only wrote those files full of zeros, but did not yet use them in any way. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. ![]() 17:08:48 9368 InnoDB: Could not open or create the system tablespace. 17:08:48 9368 InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1 17:08:48 9368 InnoDB: Doublewrite does not have page_no=0 of space: 0 17:08:48 9368 InnoDB: Restoring page 0 of tablespace 0 17:08:48 9368 InnoDB: Completed initialization of buffer pool 17:08:48 9368 InnoDB: Initializing buffer pool, size = 16.0M 17:08:48 9368 InnoDB: Using generic crc32 instructions ![]() 17:08:48 9368 InnoDB: Memory barrier is not used 17:08:48 9368 InnoDB: Mutexes and rw_locks use Windows interlocked functions 17:08:48 9368 InnoDB: The InnoDB memory heap is disabled ![]() 17:08:48 9368 InnoDB: Using mutexes to ref count buffer pool pages This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. ![]() Logs: 17:08:48 2498 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. Nestat is showing 3306 is used by mysqld.exe, so I think XAMPP MySQL should work correctly on 3360.Īlso I've tried to switch off MySQL server, didn't help to.Įrror: Error: MySQL shutdown unexpectedly MySQL Server is using port 3306, so I've changed in xampp\mysql\bin\my.ini: Īnd in xampp\php\php.ini: fault_port=3360Īlso in XAMPP Control Panel -> Config -> Service and Port Settings -> MySQL changed Main Port to 3360.Īfter all these changes it still isn't working. MySQL in XAMPP isn't starting after I installed MySQL Server.
0 Comments
Leave a Reply. |