Overview
This article details how to retrieve logs for Aembit Edge Components running as systemd services on a Linux host. In VM environments, logs are managed via journalctl.
Relates To
Deployment Type: Linux VM
Components:
aembit-agent-controller,aembit-agent-proxy
Cause (Symptom)
You should use this guide if:
The
aembit-agent-controlleroraembit-agent-proxyservices fail to start.You observe
os error 111(Connection Refused) in your application.You need to verify local inter-process communication on ports 5000/5443.
Solution
1. Retrieve Agent Controller Logs Use journalctl to view the service-level output.
sudo journalctl -u aembit-agent-controller -f2. Retrieve Agent Proxy Logs
sudo journalctl -u aembit-agent-proxy -f3. View Combined Aembit Logs To see how the two components are interacting in real-time:
sudo journalctl -u aembit-agent-controller -u aembit-agent-proxy -f