I installed confluence and when running through the setup wizard whenever I try to setup the connection to my PostgreSQL server it asks for the details. When I click the test button it says everything is fine but then when I continue it keeps going back to the database setup screen. I was not able to find any logs showing an error.
When I select to use the H2 DB everthing works. I know that the PostgreSQL Server is working properly as all other products (Crowd, Bitbucket, Jira and Bamboo) run on the same server and work fine.
Any idea how I can fix this?
Could you confirm with me your Confluence and PostgreSQL versions?
Despite the logs not having errors do they have any messages about what it might be doing in the background when this occurs?
thanks for looking into this.
PostgreSQL Version is: 9.5.10
Confluence Version is: 6.6.1
To be honest I was not able to find any log file with output besides:
That's odd; can you confirm the name of the log file it is that you're looking at?
All startup and installation logs should go to <confluence-home>/logs/atlassian-confluence.log by default.
in fact the file is the same. It just does not contain any notable content.
Here is the complete content of the file:
root@h2757808:/var/atlassian/application-data/confluence/logs# cat atlassian-confluence.log
2018-01-17 17:56:20,531 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.6.1 [build 7502 based on commit hash 85262de2dab440f060366aadca149a69d65c1f59] - synchrony version 2.1.0-release-confluence_6.5-1a01ab2d
2018-01-17 17:56:30,386 WARN [localhost-startStop-1] [com.atlassian.config.ApplicationConfig] setApplicationHome Application home does not exist. Creating directory: /var/atlassian/application-data/confluence/shared-home
2018-01-17 17:56:30,420 INFO [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Populating setup configuration if running with Cluster mode...
2018-01-17 17:56:30,424 WARN [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Could not find shared config file.
2018-01-17 17:56:38,340 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] earlyStartup Plugin system earlyStartup begun
2018-01-17 17:56:49,073 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system earlyStartup ended
2018-01-17 17:56:49,086 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] lateStartup Plugin system lateStartup begun
2018-01-17 17:56:51,641 INFO [localhost-startStop-1] [atlassian.plugin.manager.DefaultPluginManager] logTime Plugin system lateStartup ended
2018-01-17 17:56:54,535 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
I've spoken to my colleagues and they mentioned this could also be a browser caching issue.
Can you confirm the same behavior occurs in other browsers and also when clearing your cache?
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
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