KNOWLEDGE BASE

Error "Initialization terminated at step 25 of 28: Finalizing the topology failed." During Install or Ask Data Does Not Start


Published: 27 Feb 2019
Last Modified Date: 31 Jan 2020

Issue

During initialization of Tableau Server 2019.1.1 on a Linux host, the following message may occur:
 
Initialization Error
This job failed due to an error.
Initialization terminated at step 25 of 28: Finalizing the topology failed.
You can try the following troubleshooting methods to resolve the problem:
Re-enter information in the previous setup step
Try initializing server again

The "initialization terminated" error may also occur at step  22 of 25.

tsm status -v  returns a result of DEGRADED, with Elastic Server and Ask Data in an error state:
 
Tableau Server Elastic Server 0' is in an error state.
Tableau Server Ask Data 0' is in an error state.

Sometimes, installation is successful, but Ask Data and Elastic Server are in an error state. 

Confirm if you've encountered this error by scanning the logs for the following message:
 
[o.e.b.ElasticsearchUncaughtExceptionHandler] [] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: BindTransportException[Failed to bind to [port]]; nested: SocketException[Protocol family unavailable];
at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:125) ~[elasticsearch-6.2.3.jar:6.2.3]

Environment

  • Tableau Server 2019.1.1 with IPv6 disabled
  • Linux

Resolution

Upgrade to Tableau Server 2019.1.2 or a newer version.  Click here for downloads of current and previous versions of Tableau Server: Tableau Server Downloads and Release Notes. For more information on current releases, see Upgrade Tableau Server and Server Upgrade.

NOTE: Confirm if the system has IPv6 disabled by entering in bash:

Option 1:

ifconfig  OR ip a - this will only return IPv4 addresses
 
Option 2: 
ifconfig | grep inet6 is empty

Cause

This behavior is related to known issue ID 880068 and was resolved in the 2019.1.2 release of Tableau Server, and all more recent versions.

 

Did this article resolve the issue?