Greenplum Command Center (GPCC) is unable to start due to error "port already in use"
search cancel

Greenplum Command Center (GPCC) is unable to start due to error "port already in use"

book

Article ID: 296718

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Issue/Introduction

gpcc could not be started with error:

[gpadmin@~~~~]$ gpcc start
2022-04-12 17:26:17 Starting the gpcc agents and webserver...
2022-04-12 17:27:05 Failed to detect agent start status, please refer /usr/local/greenplum-cc-6.5.0/logs for details

[gpadmin@~~~~ logs]$ gpcc status
2022-04-12 17:29:56 GPCC webserver: running
2022-04-12 17:29:57 GPCC agents: 0/65 agents running 

 

From webserver.log, we could see the port 28080 was actually in use:

2022-04-12 17:34:42 [CRITICAL]Can't listen on port "28080": listen tcp :28080: bind: address already in use
2022-04-12 17:34:42 [CRITICAL]Can't listen on port "28080": listen tcp :28080: bind: address already in use 

 

This means that there is a process already using the port 28080 and GPCC is unable to start


Environment

Product Version: 6.17

Resolution

Firstly, check the process id with the port 28080 using the command:

netstat -anp | grep 28080 

 

After getting the process id, then check if it is possible to terminate the process and then try "gpcc start" again.