Services
Each container shipped with the Director is fully-integrated with the systemd
service on the host, enabling easy management using standard systemd
commands.
The logs for each container are also full-integrated with journald to simplify
troubleshooting.
In order to integrate the Podman containers with systemd
, a common prefix
of acd-
has been applied to each service name. For example the router
container is managed by the service acd-router
, and the confd
container
is managed by the service acd-confd
. These same prefixed names apply while
fetching logs via journald
. This common prefix aids in grouping the related
services as well as provides simpler filtering for tab-completion.
Starting / Stopping Services
Standard systemd commands should be used to start and stop the services.
systemctl start acd-router
- Starts therouter
container.systemctl stop acd-router
- Stops therouter
container.systemctl status acd-router
- Displays the status of therouter
container.
Due to the limitation of needing the acd-
prefix, it provides the ability to
work with all ACD services in a group. For example:
systemctl status 'acd-*'
- Display the status of all installed ACD components.systemctl start 'acd-*'
- Start all ACD components.
Logging
Each ACD component corresponds to a journal entry with the same unit name, with
the acd-
prefix. Standard journald commands can be used to view and manage the
logging.
journalctl -u acd-router
- Display the logs for therouter
container
Access Log
Refer to Access Logging.
Troubleshooting
Some additional logging may be available in the filesystem, the paths of which can
be determined by executing the ew-sysinfo
command. See
Diagnostics. for additional details.