Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Fresh Install: Switched Cloudera Manager Host from a DHCP address to a Static IP. Now, I can no longer connect to the Web UI

avatar
Explorer

Aloha!

Before, I was able to connect to the web UI via host IP and port 7180. After setting up a Static IP for the hosts in my Cluster, I seem to have broken Cloudera Manager. Should I uninstall and reinstall, or is there a simple solution that I can implement to get things working again?

1 ACCEPTED SOLUTION

avatar
New Member

no need to reinstall, few places you need to make the change to:

 

1. change the host file or dns, then access CM through hostname instead of IP address

File: /etc/hosts

 

2. make sure the DB hostname is correct if your repo is on the same server:

file: /etc/cloudera-scm-server/db.properties

 

3. change agent configuration to make sure it using hostname or new IP address

/etc/cloudera-scm-agent/config.ini

 

restart CM and CM agent.

View solution in original post

2 REPLIES 2

avatar
New Member

no need to reinstall, few places you need to make the change to:

 

1. change the host file or dns, then access CM through hostname instead of IP address

File: /etc/hosts

 

2. make sure the DB hostname is correct if your repo is on the same server:

file: /etc/cloudera-scm-server/db.properties

 

3. change agent configuration to make sure it using hostname or new IP address

/etc/cloudera-scm-agent/config.ini

 

restart CM and CM agent.

avatar
Explorer

The problem was that I did not have my database host connected. For some reason I thought that I had set up the database to be internal without the SCM host, but I was wrong! I decomissioned the database host and it prevented heartbeating from happening.