Bamboo MySQL InnoDB Log File Size
Bamboo Instance Health check
On this page
Related content
- Bamboo MySQL Max Allowed Packet
- Specified key was too long errors in the logs even when Bamboo database is correctly set to InnoDB
- MySQL - Lock wait timeout exceeded - try restarting transaction
- Initial Azure MySQL database connection attempt fails with error null java.lang.IllegalStateException
- Connect Bamboo to a MySQL database
- Bamboo MySQL Character Set
- Bamboo Instance Health check
- Bamboo fails to start with error "Bamboo bootstrap failed: Your Bamboo instance could not start because health check failed."
- MySQL Communications link failure
- Bamboo Embedded database
This check verifies if the innodb_log_file_size variable in your MySQL database is appropriate.
A fail might be caused either by the maximum allowed packet size of the MySQL server being too small or when the InnoDB log file is too small (sometimes both).
For more information, see:
Last modified on May 24, 2016
Related content
- Bamboo MySQL Max Allowed Packet
- Specified key was too long errors in the logs even when Bamboo database is correctly set to InnoDB
- MySQL - Lock wait timeout exceeded - try restarting transaction
- Initial Azure MySQL database connection attempt fails with error null java.lang.IllegalStateException
- Connect Bamboo to a MySQL database
- Bamboo MySQL Character Set
- Bamboo Instance Health check
- Bamboo fails to start with error "Bamboo bootstrap failed: Your Bamboo instance could not start because health check failed."
- MySQL Communications link failure
- Bamboo Embedded database
Powered by Confluence and Scroll Viewport.