ZTNA Connectors are offline
Article ID: 411201
Updated On:
Products
Issue/Introduction
ZTNA admin has defined multiple sites with each site having a minimum of two connectors as a best practice.
After a ZTNA maintenance in August, one of the ZTNA connectors reported as DOWN (access to the applications continued to work as the other connector was UP).
Restarting the connector addressed the issue, until another and separate connector went down.
None of these issue were visible prior to the recent upgrade.
Environment
ZTNA.
Connectors running in different sites.
Connector version 2.11.5.
Cause
Bug with ZTNA connector version 2.11.5, where an auto restart of the connector would occasionally fail.
Resolution
Make sure that your connectors are upgraded to 2.11.9. The service will push out the changes over the month of September but if your connector is still on 2.11.5, the following options exist:
- Identify each site where the 2.11.5 connector is running
- At that site, add a new connector. After saving the connector, copy the docker connector command reported in the ZTNA Portal
- Modify the version of the connector from 2.11.5 to 2.11.9 e.g. make sure the command includes the 'sac-docker.packages.broadcom.com/luminate/connector:2.11.9' string
- After successfully adding the new connector(s), remove the old ones running 2.11.5.
Additional Information
Looking at the connector logs, one sees the connector exiting without any successful restart.
time="2025-09-05T14:32:50Z" level=info msg="Policy Installed" Policy="{SendDebugLogs:false ApplicationPolicy:[{Id:########-####-####-####-############ Name:MyExample|https://example.comUrl:https://example.com Type:HTTP Subtype:HTTP_CUSTOM_DOMAIN Regions:[{Region:us-west1 Address:luminate-ws.example.luminatesec.com}]}] ConnectorSettings:{ProxyAddress: ProxyUsername: ProxyPassword:} Regions:[{Region:us-west1 Address:luminate-ws.example.luminatesec.com}]}" connectorVersion=2.11.5+7208 PID=12
time="2025-09-05T14:38:42Z" level=info msg="Got Keyboard Interrupt, Closing Connector" connectorVersion=2.11.5+7208 PID=12
time="2025-09-05T14:38:42Z" level=info msg="Closing on demand metric service" connectorVersion=2.11.5+7208 PID=12
time="2025-09-05T14:38:42Z" level=info msg="Exiting with code = 0" connectorVersion=2.11.5+7208 PID=12
{"id":"########-####-####-####-############","date":"2025-09-05T14:38:42.752751253Z","tenantId":"Not available","level":"INFO","message":"Process already exited, ignoring signal","requestId":"Not available","serviceName":"Not available","funcName":"bitbucket.org/accezz-io/connector/entrypoint_rpc.(*BinaryProxy).SendSignal","additionalVars":{"connectorVersion":"2.11.5+7208"}}
{"id":"########-####-####-####-############","date":"2025-09-05T14:38:42.752887571Z","tenantId":"Not available","level":"INFO","message":"No more processes to monitor, quit with 0","requestId":"Not available","serviceName":"Not available","funcName":"bitbucket.org/accezz-io/connector/entrypoint_rpc.(*EntrypointRPCServer).checkNotify","additionalVars":{"connectorVersion":"2.11.5+7208"}}
{"id":"########-####-####-####-############","date":"2025-09-05T14:38:42.753118444Z","tenantId":"Not available","level":"WARN","message":"unable to remove /tmp/entrypoint-connector-conn.sock","requestId":"Not available","serviceName":"Not available","funcName":"bitbucket.org/accezz-io/connector/entrypoint_rpc.(*EntrypointRPCServer).StopServer.func1","additionalVars":{"connectorVersion":"2.11.5+7208"}}
{"id":"########-####-####-####-############","date":"2025-09-05T14:38:42.753145294Z","tenantId":"Not available","level":"INFO","message":"Entrypoint Server Stopped","requestId":"Not available","serviceName":"Not available","funcName":"bitbucket.org/accezz-io/connector/entrypoint_rpc.(*EntrypointRPCServer).StopServer.func1","additionalVars":{"connectorVersion":"2.11.5+7208"}}
timed out waiting for input: auto-logout
Feedback
