Failed to setup Synchrony, turn on debug for stack trace
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
Collaborative Editing cannot be enabled as the Synchrony process cannot start.
The following appears in the atlassian-confluence.log
WARN [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] lambda$startProcess$1 Failed to setup Synchrony, turn on debug for stack trace: /opt/atlassian/confluence/temp/2.1.0-release-confluence_6.5-1a01ab2d.jar (Permission denied)The filesystem path in the above message will vary, but is the <confluence-install>/temp directory.
Diagnosis
Environment
- Confluence Server or Data Center
Cause
Confluence does not have the proper permissions to access or execute the Synchrony jar file, or the jar file is missing (if install directory was copied from elsewhere):
<confluence-install>/temp/2.1.0-release-confluence_6.5-1a01ab2d.jarResolution
If the jar file is missing, replace it in the above location. Otherwise, correct filesystem permissions using the following steps:
Do not run Confluence as root, and ensure that the user running Confluence has full read and write access to both the home and install directories. This can be set by running chmod -R with the appropriate permissions, to apply them recursively to each sub folder. An example of the right permissions would be:
chown -R confluence.confluence <confluence-install-folder>
chown -R confluence.confluence <confluence-home-folder>
chmod -R u=rwx,go-rwx <confluence-install-folder>
chmod -R u=rwx,go-rwx <confluence-home-folder>
After fixing permissions, restart Confluence and enable Collaborative Editing.