Debugging Connect
Find Axual-Connect’s configuration
The effective configuration of Axual-Connect can be seen by inspecting the Axual-Connect docker container.
docker inspect $tenant-$instance-axual-connect | less
The configuration files can be found at:
<Configuration Base>/<TENANT NAME>/instances/<INSTANCE NAME>/axual_connect.sh.
Acquire Axual-Connect’s Logs
The most recent logs can be seen by using docker
command line:
docker logs -f --tail 2000 $tenant-$instance-axual-connect
Information on acquiring historical logging can be found at Connect Logging.
Check Axual-Connect’s API endpoint
The port on which the API is hosted can be seen via docker ps
and docker inspect
.
The port is configurable in the configuration files.
You can check the endpoint in the browser or via command line.
The endpoint is not secured, it’s rather kept unreachable outside the secure network.
Debugging
Now that you know how to check the configuration, logs and the API, you can debug connect.
Note that runtime configuration, such as customer connect-application definitions, are stored in the MGMT-API database.
The "AOM" (axual operations manager) is a middle-man between MGMT-API and Connect.
Sometimes it’s worth checking the AOM logs, as well.
As we’ll identify common problems, we’ll list them here.
-
Connect-Application certificate files must be saved using Linux/Unix line breaks, not Windows Line Feeds.
Please do not alter the certificate using standard Windows tools as this can cause corruption.