KNOWLEDGE BASE

Multiple tabadminagent Admin Agent Processes prevent new tabadminagent Process from Starting


Published: 03 Dec 2020
Last Modified Date: 07 Aug 2021

Issue

Admin Agents generating thousands of error messages attempting to start up: 
 

com.tableausoftware.tabadmin.agent.TabadminAgent - Exception while starting process

WARN  org.springframework.context.annotation.AnnotationConfigApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDepen

dencyException: Error creating bean with name 'discoveryServerConfigChangeListener': Unsatisfied dependency expressed through field 'm_columboGrpcServer'; nested exception is org.springframework.beans.factory.

BeanCreationException: Error creating bean with name 'columboGrpcServer': Invocation of init method failed; nested exception is java.io.IOException: Failed to bind
...
ERROR org.springframework.boot.SpringApplication - Application startup failed

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'discoveryServerConfigChangeListener': Unsatisfied dependency expressed through field 'm_columboGrpcServer'; ne

sted exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'columboGrpcServer': Invocation of init method failed; nested exception is java.io.IOException: Failed to bind

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'columboGrpcServer': Invocation of init method failed; nested exception is java.io.IOException: Failed to bind

Caused by: java.io.IOException: Failed to bind

Caused by: java.net.BindException: Address already in use

Environment

  • Tableau Server 2019.4.0
  • Red Hat (RHEL) Linux 7

Resolution

To resolve the issue, try the following:
  • sudo su -l <name of unprivilieged user>
  • systemctl --user stop tabadminagent_0.service
  • ps aux | grep tabadminagent
If the above command shows a tabadminagent process still running, use “kill <PID>” to manually kill the process. That should clear any tabadminagent processes which might still have a handle on the Admin Agent port, so you can use the port check steps below to verify port <AdminAgentPort#> is open & available.
  • systemctl --user start tabadminagent_0.service

 

Cause

Multiple tabadminagent processes were running. "Ghost" or "Zombie" admin agents had a handle on the ports and were not allowing new admin agents to start.
 
Did this article resolve the issue?