problem to stop and start image

MarcelHillmann commented 6 years ago

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem.
- Checked that your issue isn't already filed.
- Filled the form.
- Included logs and system information.

Description

first of all, thank you for your prepared image.

My setup is your image with a on premise MariaDB 10, if i’m stop the image and start it without modification.

The image couldn‘t reconnect to the database, i have always to create a new schema and to setup the hole jira setup.

Steps to Reproduce

Install a setup (jira + on premis MariaDB) with following environment values
- JIRA_PROXY_SCHEMA = https
- JIRA_PROXY_HOST = example.com
- JIRA_PROXY_PORT = 44E
- DOCKER_WAIT_PORT = 3307
- DOCKER_WAIT_HOST = (on premise)
- JIRA_DATABASE_URL = mysql://jiradb@(on premise):3307/jiradb
- JIRA_DB_PASSWORD = ** finish the hole setup steps
run „docker stop (container name)“
run „docker start (container name)“

Expected behavior: my installation is reusing the setup from step 1

Actual behavior: I have to create a new mysql schema and to setup everything again and lost my data

Reproduces how often: 100 %

Versions

7.12.1.de

Logs And Environment Information

2018-10-03 20:45:07,277 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2018-10-03 20:45:07,332 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2018-10-03 20:45:07,333 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2018-10-03 20:45:08,245 JIRA-Bootstrap INFO [c.a.j.c.cache.pauser.NonClusteredReplicationPauserManager] Non-clustered mode: ReplicationPauserManager implemented by NonClusteredReplicationPauserManager 2018-10-03 20:45:09,339 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2018-10-03 20:45:09,371 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

___ Starting the JIRA Plugin System _________________

2018-10-03 20:45:09,373 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun 2018-10-03 20:45:15,313 JIRA-Bootstrap INFO [c.a.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed 2018-10-03 20:45:16,369 ThreadPoolAsyncTaskExecutor::Thread 5 WARN [c.a.p.s.scanner.util.ProductFilterUtil] Couldn't detect product, will use ProductFilter.ALL 2018-10-03 20:45:16,627 JIRA-Bootstrap INFO [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (3): [com.atlassian.soy.soy-template-plugin, com.atlassian.jira.jira-less-integration, com.atlassian.plugins.less-transformer-plugin], 299 seconds remaining 2018-10-03 20:45:18,612 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended 2018-10-03 20:45:18,909 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/jira/dbconfig.xml 2018-10-03 20:45:18,936 JIRA-Bootstrap INFO [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource] 2018-10-03 20:45:19,029 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks. 2018-10-03 20:45:19,030 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully. 2018-10-03 20:45:19,114 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 2018-10-03 20:45:19,115 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 2018-10-03 20:45:19,177 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:

  Heap memory     :  Used:  134 MiB.  Committed:  491 MiB.  Max:  747 MiB
  Non-heap memory :  Used:   68 MiB.  Committed:   71 MiB.  Max: 1264 MiB
---------------------------------------------------------------------------------
  TOTAL           :  Used:  202 MiB.  Committed:  561 MiB.  Max: 2011 MiB
---------------------------------------------------------------------------------

blacklabelops commented 6 years ago

I never tested mariadb. By default this image uses a mysql driver, if you use the protocol mysql://. MariaDB needs MariaDB drivers to function properly.

Also:

Jira does not support mariadb: https://jira.atlassian.com/browse/JRASERVER-32347 If you use mariadb, you will not get any Atlassian support for your instance.

MarcelHillmann commented 6 years ago

Hi,

Mysql and MariaDB has the same Driver, I will retest it with Mysql and send you a notice.

Thanks Marcel

MarcelHillmann commented 6 years ago

With MySQL is it working.

Thanks for you help

Marcel

teamatldocker / jira