My Oracle Support Banner

The Cloudera Agent Fails to Start with "Address already in use" (Doc ID 2348970.1)

Last updated on OCTOBER 18, 2019

Applies to:

Big Data Appliance Integrated Software - Version 4.9.0 and later
Linux x86-64


NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.


On BDCS 4.9.1/CDH 5.11 system the Cloudera agent will not start because address already in use. However further investigation shows that the address is held by a Cloudera agent process.

1. On the Cloudera Manager (CM) host, Node 3 by default. cloudera-scm-agent.log shows the error:

[11/Jan/2018 16:32:08 +0000] 122169 HTTPServer Thread-2 _cplogging ERROR [11/Jan/2018:16:32:08] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
File "/usr/lib64/cmf/agent/build/env/lib/python2.6/site-packages/CherryPy-3.2.2-py2.6.egg/cherrypy/process/", line 187, in _start_http_thread
File "/usr/lib64/cmf/agent/build/env/lib/python2.6/site-packages/CherryPy-3.2.2-py2.6.egg/cherrypy/wsgiserver/", line 1825, in start
raise socket.error(msg)
error: No socket could be created on ('', 9000) -- [Errno 98] Address already in use

2. However checking who is holding port 9000, finds it to be the Cloudera agent process:

a) Use netstat to find the process holding port 9000: 

 However the problem keeps recurring.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.