Unable to restart Synchrony after Confluence was not shut down gracefully
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
After Confluence crashes or when it is not stopped properly, you are unable to restart Synchrony.
When starting Synchrony, the following appears in the atlassian-confluence.log
1
2
2018-08-20 01:12:18,888 ERROR [Long running task: Restart Synchrony Task] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] startup Cannot kill the running Synchrony process although the synchrony.pid file exists
-- url: /rest/synchrony-interop/restart | referer: http://company.com:8090/admin/confluence-collaborative-editor-plugin/configure.action | traceId: 54b5b01a783we70 | userName: adminDiagnosis
Environment
Confluence 6+
This is related to the following issue with Confluence/Synchrony: CONFSERVER-54876 - Synchrony.core isn't killed with Confluence
Cause
There is a synchrony.pid file in the confluence_install/temp/ folder that makes Confluence think that Synchrony is already running.
Solution
Resolution
Steps to resolve this:
Shutdown Confluence
Manually delete the following file:
1confluence_install/temp/synchrony.pidStart Confluence
Go to Admin → General configuration → Collaborative editing
Restart Synchrony
Was this helpful?