Chapter 5. Troubleshooting remote host configuration issues

The complete remote host configuration solution currently relies on existing clients; your system will be communicating with Red Hat in different ways.

mkdir -p /etc/systemd/system/rhcd.service.d
cat /etc/systemd/system/rhcd.service.d/proxy.conf
systemctl daemon-reload
systemctl restart rhcd

# mkdir -p /etc/systemd/system/rhcd.service.d
# cat /etc/systemd/system/rhcd.service.d/proxy.conf
[Service]
Environment=HTTPS_PROXY=http://proxy.corp.com:8888
# systemctl daemon-reload
# systemctl restart rhcd

The communication technology behind the rhc daemon, rhcd, is MQTT. The client establishes a connection to the Red Hat message broker and waits for new messages. The new messages are then read and converted into playbook execution. While the messages are consumed almost instantaneously, the communication is always established by the client. There is no communication initiated from the Red Hat services to your environment.

Troubleshooting an issue often starts by looking at the logs to see what happened during a given event.

journalctl -u rhcd

# journalctl -u rhcd

journalctl -u rhcd -f

# journalctl -u rhcd -f