systemctl list-units flex-gateway*
Troubleshooting Linux Services
When installing and running Anypoint Flex Gateway on Linux, you might encounter issues with specific services. Review the list of Flex Gateway services:
The following topics provide possible causes for service issues and describe how to troubleshoot:
After installing and running Flex Gateway, you can determine which services are running with the following command:
You should see a list of services. Each is described in the following example output.
UNIT LOAD ACTIVE SUB DESCRIPTION flex-gateway-fluent-reloader.path loaded active waiting flex-gateway-fluent-reloader.path (1) flex-gateway-agent.service loaded active running flex-gateway-agent.service (2) flex-gateway-envoy.service loaded active running flex-gateway-envoy.service (3) flex-gateway-fluent.service loaded active running flex-gateway-fluent.service (4) flex-gateway.service loaded active exited Application
Component that monitors the Fluentbit configuration and extends it for reloading capabilities.
Component that configures Envoy.
The Envoy service that is used internally as a high performance proxy designed for single services and applications. Extended through WebAssembly filters.
The Fluentbit service that is used internally to forward logs, meters, and metrics into Anypoint Platform. It is also used to forward third party tools configured by the user, and local log files.
flex-gateway-agent.service status displays
failed after running the
systemctl list-units flex-gateway* command.
To diagnose the service failure, run the following command:
journalctl -u flex-gateway-*
If the output of the
journalctl command includes this line:
/lib/systemd/system/flex-gateway-fluent-reloader.service:9: Executable path is not absolute: sudo /usr/bin/systemctl restart flex-gateway-fluent.service
The problem can be resolved by running this command:
sudo systemctl daemon-reload & sudo systemctl restart flex-gateway