@Anitha-1599
Hi, could you try redeploying execution node by following step-by-step instruction?
- On execution node, remove incorrect
sshd
configuration- Make your
sshd
to stop using27199
- Ensure
27199
is NOT used by any process:netstat -tlpn | grep 27199
- Make your
- On execution node, stop and remove existing Receptor configuration
- Stop Receptor:
sudo systemctl stop receptor
- Remove configuration files including certs:
sudo rm -rf /etc/receptor
- Stop Receptor:
- On execution node, allow inbound TCP traffic
sudo firewall-cmd --add-port=27199/tcp --permanent
,sudo firewall-cmd --reload
- On AWX, remove your execution node
- On AWX, add new execution node
- Name has to be resolvable by DNS and reachable from AWX
- Select
execution
as node type - Explicitly specify port number:
27199
- Check the Peers from control nodes
- On AWX, download install bundle for your execution node
- On execution node, install receptor using this bundle
- On execution node, restart Receptor:
sudo systemctl restart receptor
Then check the status on AWX. If it is not in Ready
, check following configuration:
- On execution node, ensure your configuration file contains
tcp-listener
:sudo cat /etc/receptor/receptor.conf
- On execution node, ensure Receptor is up and running:
sudo systemctl status receptor
- On execution node, check the logs:
sudo tail -n 100 /var/log/receptor/receptor.log
- On K8s, ensure the configuration file contains
tcp-peer
:kubectl -n <namespace> exec -it deployment/<awx-name>-task -c <awx-name>-ee -- cat /etc/receptor/receptor.conf
- On K8s, check the logs:
kubectl -n <namespace> logs deployment/<awx-name>-task -c <awx-name>-ee --tail=100