Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-2443

James does not work if DNS is not available at startup

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: James Core
    • Labels:
      None

      Description

      Description

      When James starts and DNS is not available (in this case for resolving the ES nodes IP), James does not succeed to recover even when the DNS is back.
      The DNS was also set in /etc/hosts, but in a format that is maybe unsuitable (same IP on multiple lines)

      127.0.0.1       openpaas-prod.linagora.dc1 openpaas-prod
      127.0.0.1   localhost
      

      Expected result

      James should be able to recover.

      Current behaviour

      It is not.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              aduprat Antoine Duprat
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: