amp-manager socket errno 111

[d-linko]

amp-manager will ocassionally enter into an error state where it cant read the socket file in sockdir

docker compose -p anms logs -f amp-manager reveals

amp-manager-1  | 2025-09-24T13:32:17.386674 T:4096C4D8147F0000 <INFO> [proxy_cli.c:79:cace_amp_proxy_cli_real_connect] Connecting to socket
amp-manager-1  | 2025-09-24T13:32:17.386724 T:4096C4D8147F0000 <ERROR> [proxy_cli.c:83:cace_amp_proxy_cli_real_connect] Failed to connect socket  with errno 111

restarting with
docker compose -p anms restart amp-manager and readding the agents in the ui returns to a normal state

[DavidEdell]

On a similar vein, if amp-manager and ion-manager are started in the wrong order, or if the ion-manager is restarted, the amp-manager also needs to be restarted.

All of these conditions can be resolved if amp-manager detects socket errors and automatically retries after a short [configurable] delay.

[d-linko]

handled by #269 updating to latest dtnma-tools