Trying to install a fresh jira 7.9 fails on database setup with
You have specified a database that is not empty, please specify an empty database. If you want to upgrade an existing installation, please follow these instructions instead.
if the database is an azure postgres managed database.
The database _is_ empty.
What could be the issue ? Could it be that jira is assuming I am installing the datacenter version of jira for some reason ?
I found this error in the logs which lead me to https://jira.atlassian.com/browse/JRASERVER-67274
Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
The long and short of it is you need an older mysql-connector-java-5.1.x.jar driver instead of the latest mysql-connector-java-8.0.x.jar that the documentation would lead you to install.
Reverting my driver to mysql-connector-java-5.1.47.jar fixed the issue for me.
По английски не говорю, напишу на русском, 21 век всё таки, у всех есть онлайн переводчики =)
Проблема была с mysql-connector
Я скачал два коннетора 8.0.15 и 5.1.47
После удаления 8.0.15 и перезапуска jira всё заработало.
If there are tables found in the database instance, Jira will mark it as not empty.
If you confirm no other Jira instance(s) is referencing the same database instance, try dropping all the tables and restart the setup:
DROP SCHEMA public CASCADE;
(assuming public is the schema)
I had the same issue for a slightly different setup; I am using a MySQL 5.7.22 database in AWS RDS.
First, I made sure I had all the right parameters set (had to create a new parameters group based on the default one for MySQL 5.7, modified the values for the parameters as documented at https://confluence.atlassian.com/adminjiraserver0813/connecting-jira-applications-to-mysql-5-7-1027137456.html and then applied the parameters group to my AWS RDS MySQL instance). However, I was still getting the message about the database not being empty. I was using the connector mysql-connector-java-8.0.23; as soon as I changed to use mysql-connector-java-5.1.49, the issue was gone and I was able to proceed with the setup of the instance.
Keep hitting this problem when trying to setup a burner instance on Digital Ocean
If I DROP DATABASE jiradb; then jira tells me that it can't find 'jiradb'
If I then CREATE DATABASE jiradb; then jira tells me the DB is not empty.
Returns empty set (0.0)seconds
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events