Member since
08-20-2023
7
Posts
2
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
783 | 08-23-2023 06:56 PM |
10-22-2024
05:11 AM
hi @Hydg "cloudera management" pods are unable to reach the "cloudera manager" address check if the service on port 7183 is available, if the service is available, if there is no internal firewall blocking it, etc. check the pods logs and "cm" logs
... View more
04-21-2024
11:44 PM
1 Kudo
Hi @Hydg you might need to reach out to your N/w team on this, you can check agent logs and look for any DNS resolution alerts and check default server logs as well for any N/w related exceptions /var/log/messages.
... View more
04-21-2024
11:40 PM
Hi @Hydg are you able to ping the node from CM host as well as telnet & SSH?
... View more
11-07-2023
09:04 AM
Hello. Make sure that hdfs_service is enabled in the Ozone configuration. By having this enabled CM agent will put the core-site.xml into the process directory and that error will be gone. Also, here is a reference to the Ozone dependency on HDFS - https://docs.cloudera.com/cdp-private-cloud-upgrade/latest/hdfs-ozone-migration/topics/hdfs-ozone-dependency.html
... View more
08-23-2023
06:56 PM
Hello, I have found a solution to my problem. It is related to firewalls and proxy, so the Internet connection is not circulated
... View more