Difference between revisions of "I have a problem with MySQL"
From Kolmisoft Wiki
Jump to navigationJump to search
(12 intermediate revisions by 6 users not shown) | |||
Line 2: | Line 2: | ||
* [[MySQL permission problem. Contact Kolmisoft to solve it.]] | * [[MySQL permission problem. Contact Kolmisoft to solve it.]] | ||
* [[MySQL user creating and allow connecting from custom IP.]] | * [[MySQL user creating and allow connecting from custom IP.]] | ||
* [[PhpMyAdmin does not work after changing MySQL root password]] | |||
* [[Wrong permissions on configuration file, should not be world writable!]] | |||
* [[Master-Slave replication is broken because of corrupted slave relay log on Slave server]] | |||
* [[Mysql2::Error: Duplicate entry '2147483647' for key]] | |||
* [[Lock wait timeout exceeded; try restarting transaction]] | |||
* [[I have a problem with MySQL/Wrong permissions on configuration file, should not be world writable!]] | |||
* [[MySQL fails to start]] | |||
* [[High DB Load]] | |||
* [[InnoDB: ERROR: the age of the last checkpoint]] | |||
* [[A UNIQUE INDEX must include all columns in the table's partitioning function]] |
Latest revision as of 13:42, 22 July 2022
- Table X is marked as crashed and should be repaired
- MySQL permission problem. Contact Kolmisoft to solve it.
- MySQL user creating and allow connecting from custom IP.
- PhpMyAdmin does not work after changing MySQL root password
- Wrong permissions on configuration file, should not be world writable!
- Master-Slave replication is broken because of corrupted slave relay log on Slave server
- Mysql2::Error: Duplicate entry '2147483647' for key
- Lock wait timeout exceeded; try restarting transaction
- I have a problem with MySQL/Wrong permissions on configuration file, should not be world writable!
- MySQL fails to start
- High DB Load
- InnoDB: ERROR: the age of the last checkpoint
- A UNIQUE INDEX must include all columns in the table's partitioning function