nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

PostgreSQL SSL Configuration Causes Collation Exception on Startup

john morrissey

Running lastest jira in AWS using RDS postgresql. The RDS was created using the default post gres parameter group in AWS. THe errors.jsp is reporting a collation issue though it appears the jir log isn't (see below for more details)

our /secure/errors.jsp is reporting

The following warnings should be fixed, but you can choose to ignore them and continue starting JIRA.

Database: Your database is using an unsupported collation

Your postgres72 database is currently using an unsupported collation: en_US.UTF-8. You should change this to a supported collation:

POSIX.UTF-8
C.UTF-8
C
POSIX

Review our documentation for more information on supported collations.

jira log file

Database configuration OK

___ Database Configuration _________________

Loading entityengine.xml from : file:/opt/atlassian/jira/atlassian-jira/WEB-INF/classes/entityengine.xml
Entity model field type name : postgres72
Entity model schema name : public
Database Version : PostgreSQL - 9.6.2
Database Driver : PostgreSQL Native Driver - PostgreSQL 9.4.1212
Database URL : jdbc:postgresql://removed.us-east-1.rds.amazonaws.com:5432/removed
Database JDBC config : postgres72 jdbc:postgresql://removed.us-east-1.rds.amazonaws.com:5432/removed

2017-10-04 08:10:53,298 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

Accepted answers

All comments

Shannon S

Hi John,

Despite Jira not showing the same error, can you please try to run the steps from the following article to see if you're able to get past that error?

How to fix the collation of a Postgres JIRA database

Let us know if you run into any issues.

Kind Regards,
Shannon

john morrissey

here's the output of the select

jiraprod=> SELECT datcollate

jiraprod-> FROM pg_database

jiraprod-> WHERE datname = Current_database();

datcollate

-------------

en_US.UTF-8

(1 row)

john morrissey

also for AWS RDS I don't believe you can run set commands as they're configured in parameter groups. I can't seem to find the parameter to change collation so was hoping someone else has experienced this already.

Shannon S

Hi John,

You're on the right track; it does appear that it is set with the client_encoding option in the parameter groups.

Here's the Amazon appendix in question:

Common DBA Tasks Parameters

And it'll need to be set to one of the following, as you are aware:

POSIX.UTF-8
C.UTF-8
C
POSIX

Let us know if you have any trouble!

Kind Regards,
Shannon

Andy Heinzer

Hi John,

I took a review of this issue, and I wanted to clarify the source problem here.

Is your Jira instance connecting to this postgres database using an SSL connection?   You mentioned this in the title of this post originally, but we have never really returned that that detail here yet. My concern here is to learn more about this setup.   Atlassian does not provide support for the configuration of SSL, be it for web connections (HTTPS) or be it in regards to the way Jira is connecting to the database. My fear here that this specific problem might getting caused by the use of SSL to connect to the postgres instance.   I would like to clarify that point to understand if having Jira try to connect via an SSL connection to the database is at all a factor here. I am interested to learn if connecting to the database in a non-SSL method works without this hang up. This would be helpful for us to better understand the problem here.

When you start Jira, what URL are you first visiting on the site? Is your web browser automatically redirecting you to your $jirabaseurl/secure/errors.jsp page? Or are you manually navigating to that specific address?

Just a bit of background here, I manually setup a test instance of Jira Server 7.5.0 with a postgres database using the same collation as yours, en_US.UTF-8 (but I did so on a non-AWS instance). When I started Jira several times, I was never redirected to that errors page, and in turn my instance appears to be up and running. However when I manually navigated to /secure/errors.jsp I found that this page was indicating to me that the startup had problems. However visiting this page manually in this situation is misleading, because the site is already up and running, and in my opinion this page over-states the severity of this problem.   Primarily this page is for time when Jira completely fails to startup. In my experience, this page should be helpful for situations such as because of a problem plugin causing Jira to fail to load, or an unresponsive database during the startup of Jira.   In those cases, this page can be helpful to troubleshoot the problem.

In regards to the specific database collation here, I don't believe you are going to have any problems with using that existing collation in Jira. Historically though, Atlassian has found in other databases, such as MySQL, the use of collations like 'latin1_swedish_ci' can have adverse affects in regards to how users enter character information into Jira and then in turn exactly how the database is store that data. In your case, the use of the en_US.UTF-8 collation is extremely unlikely to cause problems with the way Jira is storing this data, but technically it is not among the list of supported collations for Jira.

Moving forward, I don't think your collation here is something that absolutely needs to be changed to make Jira work, and work well. However if you are still concerned about the inability to change this collation on the RDS platform, I would actually recommend installing postgresql separately and using that installed instance instead of the AWS RDS Postgres platform. In turn, you would then need to follow the explicit steps in Connecting Jira applications to PostgreSQL in order to create this new database with the supported collation type.

Regards,
Andy

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software