Installing Aria Automation Config / Saltstack: the master cannot reach PostgreSQL, RaaS, Redis hosts when refreshing grains/pillar or running highstates
Article ID: 393427
Updated On:
Products
VCF Operations/Automation (formerly VMware Aria Suite)
Issue/Introduction
- Failure to reach Postgres (in raas log):
raas[#####]: [CRITICAL] Failed to connect to the storage backend. Trying again in a bit.
- Failure to reach RaaS:
- "
Failed to save events" "no route to host"
- "
- Failure to reach salt hosts in general (salt command output):
Salt request timed out. The master is not responding. You may need to run your command with --async in order to bypass the congested event bus.
Environment
- VMware Aria Automation Config / Tanzu Guardrails / Saltstack Enterprise
Cause
- Relevant ports need to be opened on each of these hosts: PostgreSQL, RaaS, Redis
- You must open ports at both the host and network level for salt (all hosts) and for psql, https, redis respectively for PostgreSQL, RaaS, Redis.
Resolution
As a first check, make sure that the Postgres and Redis services are running on these hosts.
These services can typically be checked and restarted with systemctl.
Opening ports
This resolution assumes each host is running the firewalld service, which comes with RHEL and blocks ports by default.
For other firewalls, you will need to adapt the commands to open the same ports.
This also assumes we are using the public (default) zone. Otherwise, specify the zone with --zone=<ZONE>
- Salt (needed on salt masters):
sudo firewall-cmd --permanent --add-port=4505-4506/tcp - RaaS host:
sudo firewall-cmd --permanent --add-port=443/tcp - Redis host:
sudo firewall-cmd --permanent --add-service=redis - PSQL host:
sudo firewall-cmd --permanent --add-port=5432/tcp - and after opening these ports as above on any host, run this to apply the change:
sudo firewall-cmd --reload
Additional Information
Please see the following documentation regarding network ports for Salt:
Feedback
Yes
No
Powered by
