docker-image-atlassian-jira icon indicating copy to clipboard operation
docker-image-atlassian-jira copied to clipboard

New image MySQL DB connection broken

Open romancin opened this issue 4 years ago • 6 comments

Hi again @EugenMayer

With the latest image, DB connection to MySQL is broken. I added the new ENV variable to indicate mysql57 version, but when Jira starts, it says:

02-Jan-2020 08:34:50.603 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] 02-Jan-2020 08:34:50.612 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read 2020-01-02 08:34:50,625+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 02-Jan-2020 08:34:50.678 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 5709 ms 2020-01-02 08:34:50,767+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2020-01-02 08:34:50,769+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2020-01-02 08:34:51,471+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2020-01-02 08:34:51,481+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Starting the JIRA Plugin System _________________

2020-01-02 08:34:55,964+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2020-01-02 08:34:56,013+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks. 2020-01-02 08:34:56,014+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully. 2020-01-02 08:34:56,055+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue 2020-01-02 08:34:56,056+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue

And Jira setup is present instead of login window: image

Going back to en-8.5.2 image tag worked fine and Jira recovered after restoring database (upgrade to Database build number: 806000 occurs on boot of the new image).

romancin avatar Jan 02 '20 08:01 romancin

We'll obviously the database connection does work, since otherwise the JIRA process would not even boot. Also you will be able to install JIRA with that connection.

That said, it is something on the layer like backwards compatibility of the old database layout.

Frankly, backing up in 8.2 to xml, then use the newerer image and restore / install from xml will work and continue to work.

Said all that, I have no clue what causes this incompatibility to the previous db layout or whatever that might be in the first place

EugenMayer avatar Jan 02 '20 09:01 EugenMayer

Ok, after trying with a new install (dropping old database and starting a new one from scratch), it finishes correctly and I can access Jira. After restarting container, same problem appears, the new installation screen is shown again, so I it seems the problem is with the container and not with the database.

romancin avatar Jan 02 '20 22:01 romancin

Oh that is interesting. During the Installation confluence the configuration of the Startup Script is overwritten, that is why ist is working.so there is something in the Generator config of our image

EugenMayer avatar Jan 02 '20 23:01 EugenMayer

Oh that is interesting. During the Installation confluence the configuration of the Startup Script is overwritten, that is why ist is working.so there is something in the Generator config of our image

Have you tested it and don't have this problem? Maybe it is something in my configuration.

romancin avatar Jan 03 '20 22:01 romancin

Has this issue been solved? @romancin could you find a workaround? I had the same issue and could not upgrade due to the broken database connection.

zsoi avatar Aug 04 '20 09:08 zsoi

Finally I migrated away to Atlassian Cloud, its new 10 user Free is sufficient for me.

romancin avatar Aug 04 '20 19:08 romancin