BlueXP connector install fails with "Error: getaddrinfo ENOTFOUND"
- Views:
- 44
- Visibility:
- Public
- Votes:
- 0
- Category:
- cloud-manager
- Specialty:
- bluexp
- Last Updated:
- 3/13/2025, 3:42:18 PM
Applies to
- BlueXP connector
- RHEL 9.x
- Podman 4.x
- Aardvark
- DNS port 53 being used by host
- All endpoints reachable from connector and browser console
- All endpoints FQDN resolvable to IP
Issue
BlueXP connector install fails with below error, though all pre-requisites met and all endpoints reachable and resolvable from connector and browser console :
service-manager.log:
{"level":"error","message":"Error checking tenancy health: Error: getaddrinfo ENOTFOUND cloudmanager.cloud.netapp.com","timestamp":"2025-02-26T13:55:12.048Z"}
{"level":"error","message":"Failedrequest /occm/api/occm/system/about error: Request failed: connect ECONNREFUSED127.0.0.1:3001","timestamp":"2025-02-26T13:55:18.917Z"}
journalctl -u netapp-service-manager.service -u aardvark-dns:
Feb 26 14:55:09 BlueXPconnector aardvark-dns[1765]: Unable to start server unable to start CoreDnsserver: Address already in use (os error 98)
Feb 26 14:55:12 BlueXPconnector sm2[1244]: 2025-02-26T13:55:12.048Z error:Error checking tenancy health: Error: getaddrinfo ENOTFOUND cloudmanager.cloud.netapp.com
Feb 26 14:55:18 BlueXPconnector sm2[1244]: 2025-02-26T13:55:18.917Z error:Failed request /occm/api/occm/system/about error: Request failed: connect ECONNREFUSED 127.0.0.1:3001