About Hydg

yagoaparecidoti · ‎10-22-2024

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

Rajat_710 · ‎04-21-2024

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.

Rajat_710 · ‎04-21-2024

Hi @Hydg are you able to ping the node from CM host as well as telnet & SSH?

tomon · ‎11-07-2023

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

Hydg · ‎08-23-2023

Hello, I have found a solution to my problem. It is related to firewalls and proxy, so the Internet connection is not circulated

Online	Offline
Last Visited	‎10-31-2024 10:44 PM

Member Since	‎08-20-2023 07:40 PM
Last Visited	‎10-31-2024 10:44 PM
Posts	7
Kudos received	2

Cloudera Community

Re: Installation CM Agent failed. Failed to copy i...

Re: Unable register environment

Re: Network Interface Speed Warning

Re: Unable to connect to the server: dial tcp .......

Re: Cannot start Ozone

Re: Installation CM Agent failed. Failed to copy i...