When the CMA Agent stays OUT_OF_SERVICE or never
completes registration to CMA Master, check
cma_gateway_url, TLS, firewalls, and the gRPC listener port on the Master.
Symptom: Agent health displays
OUT_OF_SERVICE. The agent log shows connection errors
or hangs at the
Initializing
connection to master
message
without a subsequent
Sending agent
instance
confirmation
message.
For gateway discovery and cross-cluster agent configuration, see Deploying the CMA server with parcels.
-
Confirm that cma_gateway_url points to the CMA Gateway (for example
https://<master-host>:8093), not the Master gRPC port directly.
The agent discovers the Master host, gRPC port, and Auth Server URI from the gateway
endpoint (GET /api/agent/config).
-
Ensure outbound connectivity from the agent host to the gateway URL and to the
discovered gRPC port (default
8091 for plaintext or 8891
for TLS).
From Bash on GNU/Linux you can
test
TCP reachability using
/dev/tcp.
timeout 5 bash -c 'cat < /dev/tcp/<master-host>/8091' && echo OPEN
-
If the CMA Master uses TLS, set
cma_gateway_url to
https:// and verify the agent
can reach the TLS gRPC port.
-
If the gRPC port was customized during deployment, check the configured listener properties on the Master host.
grep grpc /var/run/cloudera-scm-agent/process/*-cma_master-CMA_SERVER/conf/cma-server.properties
