-
Bug
-
Resolution: Fixed
-
Low
-
6.14.2, 6.14.3, 7.0.1
-
32
-
Severity 3 - Minor
-
14
-
Bug Summary:
post-upgrade health-check throws false warning: The database collation 'en_US.utf8' is not supported by Confluence. You need to use 'utf-8'.
Environment:
Confluence 6.4 -> upgraded to 6.14.2, postgresql 9.6
Steps to replicate
- Create postgres database with en_US.utf8 collation/cset:
CREATE DATABASE test_db with ENCODING 'UTF-8' LC_COLLATE 'en_US.utf8' LC_CTYPE 'en_US.utf8' TEMPLATE template0 OWNER postgres;
- Create new Confluence environment (using the oldest supported version of the installer), use database created in previous step
- Download latest Confluence installer file, proceed with upgrading existing environment
- Start Confluence after the upgrade
Expected results
Confluence starts without any issues
Actual results
Following warning is displayed during the startup:
We discovered a problem while preparing to start Confluence. If you're a Confluence admin, you can either fix this problem now or ignore it, and start Confluence anyway. Database: The database collation 'en_US.utf8' is not supported by Confluence. You need to use 'utf-8'.
Notes
This occurs because the health check verifies against all utf-8 collations, and does not include utf8. utf8 is a supported collation, we are incorrectly reporting this as a failure.
Workaround
If using Docker, the initdb args can be overridden by setting POSTGRES_INITDB_ARGS to the below as per the example (this is using Kitematic).
--encoding=UTF8 --lc-collate='en_US.UTF-8' --lc-ctype='en_US.UTF-8'
It is safe to ignore the health check failure now and continue - it will only appear on upgrade.
- is related to
-
CONFSERVER-57749 Update health check with correct encoding requirements for Windows users on installation with PostgreSQL
- Closed
- relates to
-
CONFSERVER-58739 Configuring the Tomcat connector with a protocol different from NIO might cause a false warning about maximum HTTP thread size
- Closed
-
XPLN-1027 Loading...
-
XPLN-1238 Loading...
- was cloned as
-
JRASERVER-74353 Jira doesn't recognize en_US.utf8 as a supported collation
- Gathering Impact
- mentioned in
-
Page Loading...