Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bamboo: Charset and collation health check fails with no helpful information

Ali Jabir July 2, 2019

Hi,

 

I am using dockerized bamboo-server on EC2 instance with Mysql 5.7 RDS as a database.

On the UI I constantly get the following popups:
Screenshot 2019-07-01 at 08.23.00.png

When I click on the "Find out more" link, it takes me to the following page:
Screenshot 2019-07-02 at 10.37.58.png

Here I don't see any details or helpful information.

On the database I see the following variables configured:

+--------------------------+-------------------------------------------+
| Variable_name | Value |
+--------------------------+-------------------------------------------+
| character_set_client | utf8mb4 |
| character_set_connection | utf8mb4 |
| character_set_database | utf8 |
| character_set_filesystem | binary |
| character_set_results | utf8mb4 |
| character_set_server | utf8 |
| character_set_system | utf8 |
| character_sets_dir | /rdsdbbin/mysql-5.7.26.R1/share/charsets/ |
+--------------------------+-------------------------------------------+
+----------------------+--------------------+
| Variable_name | Value |
+----------------------+--------------------+
| collation_connection | utf8mb4_general_ci |
| collation_database | utf8_general_ci |
| collation_server | utf8_general_ci |
+----------------------+--------------------+

Could someone please help me fix this issue?

Thanks
Ali

1 answer

0 votes
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 5, 2019

As mentioned in the Support Issue, use the following SQL query to check it:

SELECT CCSA.character_set_name FROM information_schema.`TABLES` T,  information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA  WHERE CCSA.collation_name = T.table_collation  AND T.table_schema = '<databaseName>' AND character_set_name != 'utf8';
SELECT T.TABLE_NAME, C.COLLATION_NAME FROM information_schema.TABLES AS T, information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` AS C WHERE C.collation_name = T.table_collation AND T.table_schema = '<databaseName>' AND C.COLLATION_NAME != 'utf8_bin';

For the fix, can refer to How to Fix the Collation and Character Set of a MySQL Database

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events