Troubleshoot issue with DNSResolver using 'localhost' (#14)

Wojciech Kapcia (Tigase) opened 8 years ago

wojtek@atlantiscity.local ~/dev/tmps/tigase-server-dists/tigase-server-8.0.0-SNAPSHOT-b5030 $ hostname
atlantiscity.local
wojtek@atlantiscity.local ~/dev/tmps/tigase-server-dists/tigase-server-8.0.0-SNAPSHOT-b5030 $ hostname -f
atlantiscity.local

yet DNSResolver detects localhost:

Oct 26, 2017 6:06:33 PM tigase.util.DNSResolverDefault <init>
ADVERTENCIA: Resolving default host name: localhost took: 10




  =============================================================================
  ERROR! Tigase is running in Clustered Mode yet the hostname
  of the machine was resolved to *localhost* which will cause
  malfunctioning of Tigase in clustered environment!

  To prevent further issues with the clustering Tigase will be shutdown.

  Please make sure that FQDN hostname of the machine is set correctly
  and restart the server.
  =============================================================================

Which prevents running @upgrade-schema@...

Activities

Wojciech Kapcia (Tigase) commented 8 years ago
Messed up /etc/hosts file, original on MacOS looks like this:

127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost
Login to comment

Type	Task
Priority	Normal
Assignee	Wojciech Kapcia (Tigase)
RedmineID	6258

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/tigase-utils#14