I have installed environment like described in example below:
Only configuration change that i have done is adding
I have configured and started synchrony as explained in:
2. Setup Synchrony
in atlassian-confluence.log i have this info related to synchrony:
2017-08-02 14:44:55,450 INFO [ThreadPoolAsyncTaskExecutor::Thread 67] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] <init> synchrony-proxy healthcheck url: http://127.0.0.1:8090/synchrony-proxy/healthcheck
2017-08-02 14:44:59,210 INFO [lifecycle:thread-11] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] startup Starting Synchrony and enabling Collaborative Editing
2017-08-02 14:44:59,267 WARN [lifecycle:thread-11] [plugins.synchrony.bootstrap.SynchronyInteropBootstrap] onStart An exception occurred while waiting for Synchrony to start: java.lang.NullPointerException
2017-08-02 14:45:37,687 ERROR [Caesium-1-4] [scheduler.caesium.impl.CaesiumSchedulerService] executeClusteredJobWithRecoveryGuard Unhandled exception during the attempt to execute job 'synchronyStatusCheck'; will attempt recovery in 60 seconds
com.atlassian.scheduler.SchedulerRuntimeException: The parameters cannot be accessed: com.atlassian.scheduler.core.JobRunnerNotRegisteredException: No job runner registered for job runner key 'com.atlassian.confluence.plugins.synchrony-interop:synchronyStatusCheckJob'
Caused by: com.atlassian.scheduler.core.JobRunnerNotRegisteredException: No job runner registered for job runner key 'com.atlassian.confluence.plugins.synchrony-interop:synchronyStatusCheckJob'
jvmInputArguments = -Djava.util.logging.config.file=/opt/atlassian/confluence/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dsynchrony.service.url=http://192.168.0.1:8091/synchrony/v1 -Dsynchrony.proxy.enabled=true -Dconfluence.context.path= -Datlassian.plugins.startup.options= -Dorg.apache.tomcat.websocket.DEFAULT_BUFFER_SIZE=32768 -Dsynchrony.enable.xhr.fallback=true -Xms1024m -Xmx1024m -XX:+UseG1GC -Datlassian.plugins.enable.wait=300 -Djava.awt.headless=true -XX:G1ReservePercent=20 -Xloggc:/opt/atlassian/confluence/logs/gc-2017-08-02_14-43-25.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -XX:-PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintTenuringDistribution -Djava.endorsed.dirs=/opt/atlassian/confluence/endorsed -Dcatalina.base=/opt/atlassian/confluence -Dcatalina.home=/opt/atlassian/confluence -Djava.io.tmpdir=/opt/atlassian/confluence/temp
Synchrony Interop Bootstrap Plugin (com.atlassian.confluence.plugins.synchrony-interop, Version: 6.3.1, Installed: bundled)
In admin/confluence-collaborative-editor-plugin/configure.action site i have error:
We couldn't connect to your Synchrony cluster from this Confluence node
and synchrony URL
Can someone point me in right direction how to fix this.
I assume that synchrony url should be http://192.168.0.1/synchrony/v1 but i don't know where to change this.
Thank you all.
Please let us know more about what you are setting up. You linked documentation for Confluence Data Center, but the diagram you posted from Administering Collaborative Editing is standalone server architecture. If you are installing a standalone instance please see Troubleshooting Collaborative Editing.
If you need to set up Synchrony for Data Center, please follow: Configuring Synchrony for Data Center. The synchrony proxy does not work with Data Center.
I look forward to hearing how it goes with these guides.
i have managed to setup Synchrony without internal proxy as suggested following Install Confluence Data Center.
I'm running both Synchrony and Confluence on same nodes. Now i have issues with F5 because whenewer i have both nodes working i can't enter /admin site and i can't create pages.
i will open a new Question if i will need help.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community, Jessica here from the Confluence Product Marketing team! July’s community challenge is all about sharing pictures — and as an extension of our first post on what ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs