Nurah.lee

 This MariaDB log shows that the server failed to start due to a corrupted InnoDB data file , specifically involving a missing MLOG_CHECKPOINT . Let’s walk through what’s happening and how you can attempt recovery step-by-step. 🔍 What’s Happening? Key Log Line: [ERROR] InnoDB: Missing MLOG_CHECKPOINT at 50981968 between the checkpoint 50981968 and the end 50981959. This means the InnoDB redo log is corrupted — it’s expecting a checkpoint that either doesn’t exist or is unreadable, which prevents InnoDB from initializing. 🛠️ Fix Step-by-Step ✅ 1. Backup First! Before trying anything else: Backup the entire MariaDB data directory (default on Windows is usually in C:\Program Files\MariaDB xx\data ). Also backup ib_logfile0 , ib_logfile1 , and ibdata1 . 🛑 2. Try Forcing InnoDB Recovery Edit your my.ini (or my.cnf ) file and add the following under the [mysqld] section : [mysqld] innodb_force_recovery = 1 Try restarting the MariaDB service. If it still fails,...

MySQL failed to start. The error.log file show log as below; 2024-08-18 20:45:04 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 22548 2024-08-18 20:45:04 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!! 2024-08-18 20:45:04 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2024-08-18 20:45:04 0 [Note] InnoDB: Uses event mutexes 2024-08-18 20:45:04 0 [Note] InnoDB: Compressed tables use zlib 1.3 2024-08-18 20:45:04 0 [Note] InnoDB: Number of pools: 1 2024-08-18 20:45:04 0 [Note] InnoDB: Using SSE2 crc32 instructions 2024-08-18 20:45:04 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M 2024-08-18 20:45:04 0 [Note] InnoDB: Completed initialization of buffer pool 2024-08-18 20:45:04 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2024-08-18 20:45:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2024-08-18 20:45:04 0 [Note]...

2024-05-26 12:20:54 0 [ERROR] mysqld: Table '.\mysql\proxies_priv' is marked as crashed and last (automatic?) repair failed 2024-05-26 12:20:54 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table '.\mysql\proxies_priv' is marked as crashed and last (automatic?) repair failed 2024-05-26 12:20:54 0 [ERROR] Aborting Refer Chatgpt :  https://chatgpt.com/share/73109e3b-a5c5-4b92-a51d-067ce10ffed3 The error message indicates that the proxies_priv table in the MySQL system database is corrupted and the automatic repair attempt has failed. This is preventing MariaDB from starting up because it cannot access the necessary privilege tables. Here's how you can manually repair the table and potentially resolve the issue: Steps to Repair the Corrupted Table Stop the MariaDB Server : Ensure that the MariaDB server is stopped before attempting to repair the table. You can stop the server from the XAMPP Control Panel or by running: net stop mysql Start MariaDB i...

  Command >  mysql -u root > ALTER USER 'root'@'localhost' IDENTIFIED BY 'password';

 https://learnsql.com/blog/join-tables-without-common-column/#:~:text=Yes%2C%20you%20can!,for%20merging%20tables%20in%20SQL.

Error :  Solution 1: Edit phpmyadmin config.inc.php File dir : C:\xampp2\phpMyAdmin\config.inc.php $cfg['Servers'][$i]['host'] = '127.0.0.1' Solution 2: Check windows host  File dir : C:\Windows\System32\drivers\etc\hosts

 SQLSTATE[HY000] [2006] MySQL server has gone away Cara untuk fix isu ni.. 1. Mula - mula check port mysql dulu. Check samada port duplicate atau tidak.  mysql> SHOW GLOBAL VARIABLES LIKE 'PORT'; Rujukan :  How to check what port mysql is running on 2. Allow connection from user and host mysql> GRANT ALL ON *.* to root@'127.0.0.1' IDENTIFIED BY 'root' Rujukan :  Host 'xxx.xx.xxx.xxx' is not allowed to connect to this MySQL server 3. Change definer on view