Atlassian Confluence Synchrony launch errors using quick start cloudformation stack (2018)

[ashleyg]

We have atlassian provided quick start cloudformation stack (2018) that spins up confluence and a separate synchrony when you run the stack. For some reason the synchrony node launch config when it tries to spin up a separate synchrony node, it exits due to the below :- XPath set is empty It gets to as far as executing the /etc/init.d/atl-init-synchrony service and then under the below snippet from that entire service script, it fails with xpath set is empty

function waitForConfluenceConfigInSharedHome() {
    atl_log "=== BEGIN: Waiting for confluence.cfg.xml available in shared home folder ==="
    while [[ ! -f ${ATL_CONFLUENCE_SHARED_CONFIG_FILE} ]]; do
          sleep ${ATL_SYNCHRONY_WAITING_CONFIG_TIME}
          atl_log "====== :   Keep waiting for ${ATL_SYNCHRONY_WAITING_CONFIG_TIME} seconds ======"
        done
        SYNCHRONY_JWT_PRIVATE_KEY=$(xmllint --nocdata --xpath '//properties/property[@name="jwt.private.key"]/text()' ${ATL_CONFLUENCE_SHARED_CONFIG_FILE}) >> ${ATL_LOG} 2>&1
    SYNCHRONY_JWT_PUBLIC_KEY=$(xmllint --nocdata --xpath '//properties/property[@name="jwt.public.key"]/text()' ${ATL_CONFLUENCE_SHARED_CONFIG_FILE}) >> ${ATL_LOG} 2>&1
        while [[ -z ${SYNCHRONY_JWT_PRIVATE_KEY} ]]; do
            atl_log "====== :   Could not load value for jwt.private.key will wait for next ${ATL_SYNCHRONY_WAITING_CONFIG_TIME} seconds before reload ======"
            sleep ${ATL_SYNCHRONY_WAITING_CONFIG_TIME}
            SYNCHRONY_JWT_PRIVATE_KEY=$(echo 'cat //properties/property[@name="jwt.private.key"]/text()' | xmllint --nocdata --shell ${ATL_CONFLUENCE_SHARED_CONFIG_FILE} | sed '1d;$d')
        SYNCHRONY_JWT_PUBLIC_KEY=$(echo 'cat //properties/property[@name="jwt.public.key"]/text()' | xmllint --nocdata --shell ${ATL_CONFLUENCE_SHARED_CONFIG_FILE} | sed '1d;$d')
        done

        atl_log "=== END: Waiting for confluence.cfg.xml avalaible in shared home folder ==="
}

Since this script is auto generated by the stack and all of this is auto stack driven without any manual intervention, i am trying to figure out what is it that its doing that it can't complete the stack successfully.
Any help or suggestions will be greatly appreciated

[Fabian Lim]

Hi Ashley,

You may want to review the following troubleshooting guide to find the root cause: https://confluence.atlassian.com/doc/troubleshooting-collaborative-editing-858772087.html

Regards