KNOWLEDGE BASE

When adding an additional node "An error occurred during installation. Unable to install services in parallel"


Published: 21 Jul 2020
Last Modified Date: 13 Aug 2021

Issue

When initializing additional node with bootstrap the following error is observed:

sudo ./initialize-tsm -b ~/bootstrap.json --accepteula

Creating 'tsmadmin' group for TSM admin authorization
Creating 'tableau' unprivileged user account
Creating environment file...
Creating directories and setting permissions...
Using '/var/opt/tableau/tableau_server' as the data directory.
Adding user 'admin' to group 'tableau'...
Adding user 'admin' to group 'tsmadmin'...
Added. Note: These group membership changes do not take effect in shells already open. For these to take effect, log out of the shell and log back in.
Calling node installer...
Operation failed.
An error occurred during installation.
Unable to install services in parallel:
ERROR: installer returned status InternalError

In the logs control_tabadminagent_nodeN-0.log the following errors are observed:

INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost.localdomain/127.0.0.1:8755. Will not attempt to authenticate using SASL (unknown error)
2020-06-09 17:37:12.639 +0100 ZKWorker-ScheduledTask-0-SendThread(localhost.localdomain:8755) : WARN org.apache.zookeeper.ClientCnxn - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused




 

Environment

  • Tableau Server on Linux platform

Resolution

Change the coordinationservice.hosts key to the correct hostname, and generating a new bootstrap

1. Run the command to check the existing setting:

tsm configuration get -k coordinationservice.hosts

Expected result (NNNN will be a port number):

localhost.localdomain:NNNN

2. Run the command to set the correct hostname (keeping the NNNN port number from previous output, where hostname is the primary server hostname):

tsm configuration set -k coordinationservice.hosts -v hostname:NNNN

3. Run the command to check the pending setting is applied:

tsm pending-changes list

Expected result:

Configuration
Key: coordinationservice.hosts
Old Value: localhost.localdomain:8755
New Value: hostname:8755
Topology
There are no pending topology changes.


4. Apply pending changes

tsm pending-changes apply

5. Generate a new bootstrap file, try and add the new node.

Cause

tsm configuration key coordinationservice.hosts is not correct.   It should be the hostname of the initial node, not localhost.
Did this article resolve the issue?