What can be possible reasons for the Jira setup wizard, to show up?

[mibemerami]

Background:

I'm migrating Jira, to test my backup process. But after the migration the setup wizard shows up on the new server, on the old server everything still works fine. The same process has worked before and all data seems to be there.

In the Jira home folder is a dbconfig.xml, the database is populated, and the migration log doesn't show any errors.

My question:

It surprises me especially, that the setup wizard appears. I mean if the database wasn't reachable, or the data was corrupted, I would have expected an error message, or an error code like 500. Also I thought that the presence of a dbconfig.xml would prevent the setup wizard from starting. So what could be the reason? Or in general, what could be a reason for the setup wizard to start?

My Setup:

The Jira version 7.3, the DB-Server is Postgres 9.4. I'm using pg_dump to migrate the database, and I pack the whole Jira home and installation directory into a tar and extract it on the destination server. The whole stack is running in Centos based containers.

[Nic Brough -Adaptavist- · Accepted solution]

The setup wizard only runs when you connect Jira to an empty database, or at least one that looks empty to it.  Are you sure the user you are connecting as has full access to the database?  (That's my usual trick - a valid user with the right credentials, but no "read table" access, so when it looks at a full database, it sees no tables and thinks "ah, that's empty then")

[mibemerami]

Thanks for the reply, it sounds sensible, but it seems like this is not the problem.

I connected to the postgres-server as user postgres and granted all privileges to the jira user. Than I restarted Jira. But still the setup wizard appears. 

root@f-stack-test-docker-s-4vcpu-8gb-fra1-01:~# docker run --network astack_default -ti  postgres:9.4 psql -h db -U postgres
Password for user postgres:
psql (9.4.18)
Type "help" for help.

postgres=# \l
                                     List of databases
     Name     |  Owner   | Encoding |  Collate   |   Ctype    |      Access privileges
--------------+----------+----------+------------+------------+-----------------------------
 bitbucketdb  | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/postgres               +
              |          |          |            |            | postgres=CTc/postgres      +
              |          |          |            |            | bitbucketuser=CTc/postgres
 confluencedb | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/postgres               +
              |          |          |            |            | postgres=CTc/postgres      +
              |          |          |            |            | confluenceuser=CTc/postgres
 crowddb      | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/postgres               +
              |          |          |            |            | postgres=CTc/postgres      +
              |          |          |            |            | crowduser=CTc/postgres
 crowdiddb    | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/postgres               +
              |          |          |            |            | postgres=CTc/postgres      +
              |          |          |            |            | crowduser=CTc/postgres
 jiradb       | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =Tc/postgres               +
              |          |          |            |            | postgres=CTc/postgres      +
              |          |          |            |            | jirauser=CTc/postgres
 postgres     | postgres | UTF8     | en_US.utf8 | en_US.utf8 |
 template0    | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres                +
              |          |          |            |            | postgres=CTc/postgres
 template1    | postgres | UTF8     | en_US.utf8 | en_US.utf8 | =c/postgres                +
              |          |          |            |            | postgres=CTc/postgres
(8 rows)

postgres=# GRANT ALL PRIVILEGES ON DATABASE "jiradb" TO jirauser;
GRANT

[Nic Brough -Adaptavist-]

I can't see anything immediately wrong with that, but the problem remains - the setup wizard appears when Jira sees an empty database (or one that looks empty for wahtever reason)

[mibemerami]

I just discovered that the database is there, and the users are there, and the tables are there, in the database, BUT the tables are empty. So, you were right :-)

Now I know at least where to look for the problem/solution.