Get the App
SLTechnology News&Howtos  ›  Servers  › 

Why the CloudFoundry component Job cannot parse the machine Address

Shulou Source: shulou.com Published: 2022-05-31 19:53:19 09月22日 Update

Why the CloudFoundry component Job can not parse the machine Address? I believe many inexperienced people don't know what to do about it. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

[problem phenomenon]

Cf component ccng failed to start, prompting the following message:-STARTING cloud_controller_ng_ctl at Thu Sep 11 07:33:05 UTC 2014-restart: Unknown instance: mount.nfs: DNS resolution failed for 0.nfs-server.default.cf-180.microbosh: Name or service not known

[cause of the problem]

Cf component Job virtual machine parses the address of the machine where other components are located from the powerdns of MicroBosh. From / etc/resolv.conf, you can see that nameserver points to the virtual machine where MicroBosh resides. However, the virtual machine did not get the machine IP from PowerDNS. The reason is that the MicroBosh firewall is set and the DNS port 53 is opened.

After reading the above, do you understand why the CloudFoundry component Job cannot parse the machine Address? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Tags: Machines components problems causes content location methods more helpless to this end information address this skills pointing phenomena ports articles experience industry Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno macOS MariaDB Redmi NVidia MySQL