Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-57771

Starting Synchrony Error: Could not find or load main class <node IP address>

XMLWordPrintable

      Issue Summary

      Customer isn't able to start synchrony.
      When running start-synchrony.sh, no log is generated, and process is not shown in ps -ef command in Linux.
      If running in foreground mode, start-synchrony.sh -fg, we receive the following error message:

      Error: Could not find or load main class <node IP address>
      

      Environment

      • Confluence Data Center
      • More than 1 Synchrony Node

      Steps to Reproduce

      • Edit start-synchrony.sh
      • For the cluster.join.tcpip.members, have a space character after the comma
        Example:
        TCPIP_MEMBERS="10.10.10.1, 10.10.10.2"
         CLUSTER_JOIN_PROPERTIES="\
         -Dcluster.join.type=tcpip \
         -Dcluster.join.tcpip.members=${TCPIP_MEMBERS}"
        

        A) Try to start synchrony using ./start-synchrony.sh
        B) Try to start synchrony in foreground using ./start-synchrony.sh -fg

      Expected Results

      For both A) and B)

      • Synchrony service to start accordingly

      Actual Results

      A) Synchrony does not start
      Cannot be found in ps -ef output

      • No information in the log file atlassian-synchrony.log

      A) Synchrony does not start
      Cannot be found in ps -ef output

      • No information in the log file atlassian-synchrony.log
      • Error message is displayed (example IP address):
        Error: Could not find or load main class 10.10.10.2
        

      Workaround

      • Remove the space character from cluster.join.tcpip.members parameter
        Example:
        TCPIP_MEMBERS="10.10.10.1,10.10.10.2"
         CLUSTER_JOIN_PROPERTIES="\
         -Dcluster.join.type=tcpip \
         -Dcluster.join.tcpip.members=${TCPIP_MEMBERS}"
        

              Unassigned Unassigned
              eviana Edson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: