This installation of Confluence has failed one or more bootstrap configuration.

[bluelight]

You cannot access Confluence at present. Look at the table below to identify the reasons.

This installation of Confluence has failed one or more bootstrap configuration checks. Please check the logs for details.

Couldn't lock file 'lock' in directory /var/atlassian/application-data/confluence
Make sure the directory is not being used by another Confluence instance.

 Tried to recreate the lock file.

root@atlassian:~# f=/var/atlassian/application-data/confluence/lock
root@atlassian:~# touch $f && chown confluence:confluence $f
root@atlassian:~# history -a; date; shutdown -r now& exit

Still the same problem persists.

Log:

2017-05-31 15:38:58,723 WARN [UpmScheduler:thread-1] [atlassian.upm.notification.PluginUpdateCheckerImpl] checkForUpdates Automatic plugin update check failed
com.atlassian.util.concurrent.RuntimeExecutionException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Connection pool shut down
...
2017-05-31 15:39:01,402 ERROR [AtlassianEvent::CustomizableThreadFactory-1] [atlassian.plugin.module.PrefixDelegatingModuleFactory] createModule Detected an error instantiating the module via Spring. This usually means that you haven't created a <component-import> for the interface you're trying to use. https://developer.atlassian.com/x/TAEr  for more details.
...
[similar repeated several times]
2017-05-31 15:39:01,800 ERROR [AtlassianEvent::CustomizableThreadFactory-1] [confluence.macro.browser.DefaultMacroMetadataManager] buildMacroMetadata Error getting data from MacroMetadataProvider,
com.atlassian.cache.CacheException: org.eclipse.gemini.blueprint.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed
...

Confluence is vacant, a call to tenanted [public abstract net.sf.hibernate.Session net.sf.hibernate.SessionFactory.openSession() throws net.sf.hibernate.HibernateException] is not allowed.[several more "service proxy has been destroyed" messages

[bluelight · Accepted solution]

Cannot reproduce, I had restarted the service yesterday, did not work, today morning, the website is available and Confluence if running perfectly. Still don't know what caused the problem, works now though!

[Nic Brough -Adaptavist-]

The lock file indicates that the system is already running.  It stops multiple starts.

However, it can be left behind if you kill Confluence improperly, or your system is shut down uncleanly (and in some cases, a simple crash in Confluence can do it)

Make sure Confluence is not running, remove the lock file, then restart Confluence.  Read the logs to find out if there are problems starting it (The snippey you have given us is too short and apparently picked randomly out of the log.  If it fails, you need to read back all of it from the bottom to where the errors start)

[bluelight]

I made sure confluence was not running, + these logs are specific, because all the other lines are just java excetion errors.

Looked in a few other sites, they say that it is a mysql bug, but postgres is being used as the database.

[Nic Brough -Adaptavist-]

If it's failing to run, you need to work through the logs to find out why. 

The logs are quite noisy or verbose, and tend to give you a little bit too much (the "debug" information that is useful to developers, but mostly useless to the rest of us), but there's no way to work out a "can not start" problem than reading through the logs to find the errors.

Please go back over the log and read back all of it from the bottom to where the errors start