Port Conflict While Adding Sqoop2 Service in Cloudera Manager
(Doc ID 2302942.1)
Last updated on JANUARY 10, 2020
Applies to:
Big Data Appliance Integrated Software - Version 4.4.0 and laterLinux x86-64
Symptoms
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.
Adding the Sqoop2 service in Cloudera Manager, fails with the below errors:
bdanode01.example.com: Port conflict detected 8005 (Sqoop2 Admin Port) is also used by Sqoop2 Server (bdanode01)
bdanode01.example.com: Port conflict detected 8005 (Sqoop2 Admin Port) is also used by Sqoop2 Server (bdanode01)
bdanode01.example.com: Port conflict detected 12000 (Sqoop2 HTTP Port) is also used by Sqoop2 Server (bdanode01)
bdanode01.example.com: Port conflict detected 12000 (Sqoop2 HTTP Port) is also used by Sqoop2 Server (bdanode01)
bdanode01.example.com: Port conflict detected 8005 (Sqoop2 Admin Port) is also used by Sqoop2 Server (bdanode01)
bdanode01.example.com: Port conflict detected 12000 (Sqoop2 HTTP Port) is also used by Sqoop2 Server (bdanode01)
bdanode01.example.com: Port conflict detected 12000 (Sqoop2 HTTP Port) is also used by Sqoop2 Server (bdanode01)
Changes
Not known.
Cause
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
Symptoms |
Changes |
Cause |
Solution |