How to connect Jira to remote database - PostgreSQL

[KL Kumar]

Hello,

I have a local Jira (v8.0.2) setup in my machine and I can up the Jira server (using default h2 DB) without any issues. But I want to configure remote PostgreSql and bring the Jira server up. I did the database configuration in dbconfig.xml in jira/home directory, but the jira server is failing to start. The only errors I can see is as below.

[INFO] [talledLocalContainer] 2019-06-21 17:09:27,613 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
[INFO] [talledLocalContainer] 2019-06-21 17:09:27,613 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
[INFO] [talledLocalContainer] 2019-06-21 17:09:28,528 localhost-startStop-1 INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\D-Drive\Workspace\JiraContextManager\target\jira\home\dbconfig.xml
[DEBUG] [URLDeployableMonitor] URL [http://localhost:2990/cargocpc/index.html] is not responding: -1 java.net.SocketTimeoutException: Read timed out
[DEBUG] [URLDeployableMonitor] Notifying monitor listener [org.codehaus.cargo.container.spi.deployer.DeployerWatchdog@43ef1243]
[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22:25 min
[INFO] Finished at: 2019-06-21T17:15:22+05:30
[INFO] Final Memory: 40M/164M
[INFO] ------------------------------------------------------------------------

I am able to connect to the same remote DB configuration from pgAdmin 4 (vendor software to connect to DB).

Is there any other configuration am I missing ?

Thanks!

Kumar

[KL Kumar · Accepted solution]

Okay! I found the issue. It is the schema name (public) in dbconfig.xml which was mentioned in uppercase. PostgreSQL is case sensitive and so it caused the issue. Changed the schema name to lowercase and restarted the jira. It works.

Thanks!

Kumar

[Andy Heinzer]

Hi Kumar,

It looks like you're using the atlassian SDK in order to try to connect to an external postgresql database and it doesn't look like it is working.

I took a closer look at my own Atlassian SDK and when I'm looking into my folders of both the install and home directories, I'm not seeing the postgres jdbc .jar driver file that Jira needs to be able to connect to that data type.  A non- SDK Jira install will always have this in the $JIRAINSTALL/lib/ folder.  But the SDK seems to only have the h2sql one here.

I found a related topic to this that I think will help here.  Check out Using mysql instead of HSQL db with Atlassian PDK.  It is a bit older, and it's dealing with using mysql for the SDK, but I think the steps are still going to be applicable here.  My Jira 8.1.0 version appears to be shipping with the Postgres 9.4.1212 jdbc driver.  A big list of these files can be found in https://jdbc.postgresql.org/download.html

But I think the driver you likely want for a Java 8 / JDK 8 environment would be.  https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar

Try this and see if this helps.

Andy

[KL Kumar]

Thanks for your reply @Andy Heinzer ,

I downloaded postgresql-9.1-901-1.jdbc4.jar and copied to "target\jira\webapp\WEB-INF\lib" directory and "target\container\tomcat8x\apache-tomcat-8.5.6\lib". None of them worked for me.

I don't think it is a driver issue (though I have the driver jar), because if it is a driver issue, it might have thrown no class found error or similar. All I can see is a timeout warning.

[INFO] [talledLocalContainer] 2019-06-26 22:36:59,860 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger]
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] Database configuration OK
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] ___ Database Configuration ________________
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] Loading entityengine.xml from : file:/C:/D-Drive/Workspace/JiraContextManager/target/container/tomcat8x/cargo-jira-home/webapps/jira/WEB-INF/classes/entityengine.xml
[INFO] [talledLocalContainer] Entity model field type name : postgres72
[INFO] [talledLocalContainer] Entity model schema name : public
[INFO] [talledLocalContainer] Database Version : PostgreSQL - 9.5.8
[INFO] [talledLocalContainer] Database Driver : PostgreSQL Native Driver - PostgreSQL 9.4.1212
[INFO] [talledLocalContainer] Database URL : jdbc:postgresql://xxx.xx.xx.xxx:5432/devdb
[INFO] [talledLocalContainer] Database JDBC config : postgres72 jdbc:postgresql://xxx.xx.xx.xxx:5432/devdb
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] 2019-06-26 22:37:00,226 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger]
[INFO] [talledLocalContainer]
[INFO] [talledLocalContainer] ___ Starting the JIRA Plugin System _________________
[INFO] [talledLocalContainer]
[INFO] [yer.DeployerWatchdog] Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[WARNING] [talledLocalContainer] org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:2990/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

[Andy Heinzer]

Thanks for that info.  It might not be a driver issue.  But if we're seeing a timeout, then Jira is getting hung up somewhere.

I would want to test this database connection outside of the SDK itself.  If you were to use a standard Jira server install, you could utilize the Jira config tool as a means to both setup the database connection and test your settings outside of the Java application that actually loads Jira.

I searched on this error some more and came across this page: https://developer.atlassian.com/server/framework/atlassian-sdk/product-fails-to-start-within-timeout-period/

It would seem that there can be lots of general problems that could cause this error.  But that antivirus scanning tends to be the most likely cause.  Perhaps you can try to disable the antivirus temporarily to see if you can complete this build that way.

[KL Kumar]

@Andy Heinzer thanks for the information. I am not using a jira server install. I am trying to develop a jira plugin and followed atlas commands to create it and hence it created a tomcat in my target directory. All the changes related to DB (updating dbconfig.xml) was done in the target directory only.

[KL Kumar]

Hi @Andy Heinzer , I have upgraded jira to 8.2.3 and I am able to resolve the build issues with the help of below references.

https://community.atlassian.com/t5/Jira-questions/Unknown-lifecycle-phase-error/qaq-p/1006922

https://ecosystem.atlassian.net/browse/ATLASSDK-163

I tried with different postgresql driver versions, but still the server starts with an error page. I looked at the logs and the logs has full of PSQLExceptions as below. Not sure what is causing the issue to connect to remote database.

2019-07-23 00:11:44,379 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2019-07-23 00:11:44,379 localhost-startStop-1 INFO [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2019-07-23 00:11:45,057 localhost-startStop-1 INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\D-Drive\Workspace_ProAction\asopCustomFieldManager\target\jira\home\dbconfig.xml
2019-07-23 00:11:51,665 localhost-startStop-1 INFO [o.o.c.entity.jdbc.DatabaseUtil] Database Product Name is PostgreSQL
2019-07-23 00:11:51,665 localhost-startStop-1 INFO [o.o.c.entity.jdbc.DatabaseUtil] Database Product Version is 9.5.8
2019-07-23 00:11:51,665 localhost-startStop-1 INFO [o.o.c.entity.jdbc.DatabaseUtil] Database Driver Name is PostgreSQL JDBC Driver
2019-07-23 00:11:51,665 localhost-startStop-1 INFO [o.o.c.entity.jdbc.DatabaseUtil] Database Driver Version is 42.2.6
2019-07-23 00:11:52,008 localhost-startStop-1 WARN [o.o.c.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database
2019-07-23 00:11:52,353 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Could not create table "PUBLIC.jiraaction"
2019-07-23 00:11:52,353 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE PUBLIC.jiraaction (ID BIGINT NOT NULL, issueid BIGINT, AUTHOR VARCHAR, actiontype VARCHAR, actionlevel VARCHAR, rolelevel BIGINT, actionbody VARCHAR, CREATED TIMESTAMP, UPDATEAUTHOR VARCHAR, UPDATED TIMESTAMP, actionnum BIGINT, CONSTRAINT PK_jiraaction PRIMARY KEY (ID))
Error was: org.postgresql.util.PSQLException: ERROR: relation "jiraaction" already exists
2019-07-23 00:11:52,354 localhost-startStop-1 WARN [o.o.c.entity.jdbc.DatabaseUtil] Entity "Application" has no table in the database
2019-07-23 00:11:52,640 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Could not create table "PUBLIC.cwd_application"
2019-07-23 00:11:52,641 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE PUBLIC.cwd_application (ID BIGINT NOT NULL, application_name VARCHAR, lower_application_name VARCHAR, created_date TIMESTAMP, updated_date TIMESTAMP, active INTEGER, description VARCHAR, application_type VARCHAR, credential VARCHAR, CONSTRAINT PK_cwd_application PRIMARY KEY (ID))
Error was: org.postgresql.util.PSQLException: ERROR: relation "cwd_application" already exists
2019-07-23 00:11:52,642 localhost-startStop-1 WARN [o.o.c.entity.jdbc.DatabaseUtil] Entity "ApplicationUser" has no table in the database
2019-07-23 00:11:52,926 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] Could not create table "PUBLIC.app_user"
2019-07-23 00:11:52,927 localhost-startStop-1 ERROR [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE PUBLIC.app_user (ID BIGINT NOT NULL, user_key VARCHAR, lower_user_name VARCHAR, CONSTRAINT PK_app_user PRIMARY KEY (ID))
Error was: org.postgresql.util.PSQLException: ERROR: relation "app_user" already exists
2019-07-23 00:11:52,927 localhost-startStop-1 WARN [o.o.c.entity.jdbc.DatabaseUtil] Entity "AuditChangedValue" has no table in the database

..and many more similar errors.

[INFO] [talledLocalContainer] 2019-07-23 00:17:01,849 localhost-startStop-1 ERROR [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked.
[INFO] [talledLocalContainer] com.atlassian.jira.InfrastructureException: Error occurred while starting component 'com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor'.
[INFO] [talledLocalContainer] at com.atlassian.jira.component.pico.ComponentManager.startStartableComponents(ComponentManager.java:339)
[INFO] [talledLocalContainer] at com.atlassian.jira.component.pico.ComponentManager.earlyStartPluginSystem(ComponentManager.java:252)
[INFO] [talledLocalContainer] at com.atlassian.jira.upgrade.PluginSystemLauncher.start(PluginSystemLauncher.java:45)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:145)
[INFO] [talledLocalContainer] at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301)
[INFO] [talledLocalContainer] at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104)
[INFO] [talledLocalContainer] at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.LauncherContextListener.initSlowStuffInBackground(LauncherContextListener.java:139)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:101)
[INFO] [talledLocalContainer] ... 8 filtered
[INFO] [talledLocalContainer] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[INFO] [talledLocalContainer] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[INFO] [talledLocalContainer] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[INFO] [talledLocalContainer] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[INFO] [talledLocalContainer] at java.lang.Thread.run(Thread.java:745)
[INFO] [talledLocalContainer] Caused by: java.lang.RuntimeException: com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,jobRunnerKey=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Tue Jul 23 01:16:29 IST 2019,intervalInMillis=3600000]],nextRunTime=Tue Jul 23 01:16:29 IST 2019,version=1,rawParameters=(null)]
[INFO] [talledLocalContainer] at com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor.scheduleCleanup(DefaultTemporaryWebAttachmentsMonitor.java:75)
[INFO] [talledLocalContainer] at com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor.start(DefaultTemporaryWebAttachmentsMonitor.java:61)
[INFO] [talledLocalContainer] at com.atlassian.jira.component.pico.ComponentManager.startStartableComponents(ComponentManager.java:335)
[INFO] [talledLocalContainer] ... 25 more
[INFO] [talledLocalContainer] Caused by: com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,jobRunnerKey=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Tue Jul 23 01:16:29 IST 2019,intervalInMillis=3600000]],nextRunTime=Tue Jul 23 01:16:29 IST 2019,version=1,rawParameters=(null)]
[INFO] [talledLocalContainer] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleClusteredJob(CaesiumSchedulerService.java:188)
[INFO] [talledLocalContainer] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:136)
[INFO] [talledLocalContainer] at com.atlassian.scheduler.core.DelegatingSchedulerService.scheduleJob(DelegatingSchedulerService.java:62)
[INFO] [talledLocalContainer] at com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor.scheduleCleanup(DefaultTemporaryWebAttachmentsMonitor.java:73)
[INFO] [talledLocalContainer] ... 27 more
[INFO] [talledLocalContainer] 2019-07-23 00:17:04,052 localhost-startStop-1 ERROR [c.a.j.upgrade.util.UpgradeUtils] JDBC get version number failed. SQL: SELECT ps.null FROM PUBLIC.propertyentry pe, PUBLIC.propertystring ps WHERE pe.null='jira.version.patched' AND pe.null=ps.null
[INFO] [talledLocalContainer] org.postgresql.util.PSQLException: ERROR: column ps.null does not exist
[INFO] [talledLocalContainer] Position: 8
[INFO] [talledLocalContainer] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468)
[INFO] [talledLocalContainer] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211)
[INFO] [talledLocalContainer] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309)
[INFO] [talledLocalContainer] at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446)
[INFO] [talledLocalContainer] at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:370)
[INFO] [talledLocalContainer] at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:311)
[INFO] [talledLocalContainer] at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:297)
[INFO] [talledLocalContainer] at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:274)
[INFO] [talledLocalContainer] at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:225)
[INFO] [talledLocalContainer] at org.apache.commons.dbcp2.DelegatingStatement.executeQuery(DelegatingStatement.java:207)
[INFO] [talledLocalContainer] at org.apache.commons.dbcp2.DelegatingStatement.executeQuery(DelegatingStatement.java:207)
[INFO] [talledLocalContainer] at com.atlassian.jira.upgrade.util.UpgradeUtils.getJIRABuildVersionNumber(UpgradeUtils.java:262)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.checks.database.MinimumUpgradableVersionHealthCheck.doPerform(MinimumUpgradableVersionHealthCheck.java:49)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.HealthCheckTemplate.perform(HealthCheckTemplate.java:23)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.DefaultHealthCheckExecutor.runCheck(DefaultHealthCheckExecutor.java:74)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.DefaultHealthCheckExecutor.lambda$applyAndCollectExceptions$1(DefaultHealthCheckExecutor.java:53)
[INFO] [talledLocalContainer] at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
[INFO] [talledLocalContainer] at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
[INFO] [talledLocalContainer] at java.util.Iterator.forEachRemaining(Iterator.java:116)
[INFO] [talledLocalContainer] at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
[INFO] [talledLocalContainer] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
[INFO] [talledLocalContainer] at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
[INFO] [talledLocalContainer] at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
[INFO] [talledLocalContainer] at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
[INFO] [talledLocalContainer] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
[INFO] [talledLocalContainer] at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.DefaultHealthCheckExecutor.applyAndCollectExceptions(DefaultHealthCheckExecutor.java:53)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.DefaultHealthCheckExecutor.performHealthChecks(DefaultHealthCheckExecutor.java:42)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.HealthChecks.executeChecksAndRecordResults(HealthChecks.java:164)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:154)
[INFO] [talledLocalContainer] at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:66)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:163)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:146)
[INFO] [talledLocalContainer] at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301)
[INFO] [talledLocalContainer] at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104)
[INFO] [talledLocalContainer] at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.LauncherContextListener.initSlowStuffInBackground(LauncherContextListener.java:139)
[INFO] [talledLocalContainer] at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:101)
[INFO] [talledLocalContainer] ... 8 filtered
[INFO] [talledLocalContainer] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[INFO] [talledLocalContainer] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[INFO] [talledLocalContainer] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[INFO] [talledLocalContainer] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[INFO] [talledLocalContainer] at java.lang.Thread.run(Thread.java:745)
[INFO] [talledLocalContainer] 2019-07-23 00:17:04,074 localhost-startStop-1 ERROR [c.a.jira.startup.DefaultJiraLauncher] 
JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: startup-unexpected) , Desc = We couldn't start JIRA , Exception = An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.<br/>See our documentation for more information on contacting our support team and creating a support zip.)]

This seems, my jira setup in my local machine is trying to create all the relations on my remote database and hence throwing errors as they already exist. 

Any help can be greatly appreciated.

Thanks!

Kumar

[KL Kumar]

Okay! I found the issue. It is the schema name (public) in dbconfig.xml which was mentioned in uppercase. PostgreSQL is case sensitive and so it caused the issue. Changed the schema name to lowercase and restarted the jira. It works.

Thanks!

Kumar