Cluster acquisition is stuck in progress with AIQUM 9.14 or newer
- Views:
- 2,406
- Visibility:
- Public
- Votes:
- 0
- Category:
- active-iq-unified-manager
- Specialty:
- OM
- Last Updated:
- 3/25/2025, 1:58:40 PM
Applies to
- Active IQ Unified Manager (AIQUM) 9.14+
- Ontap 9.14+
Issue
- Cluster acquisition is stuck in progress for hours:
Cluster discovery failed. Rediscover the cluster after resolving the issue
Unable to add cluster datasource. This can occur if the clocks on the systems are not synchronized and the Active IQ Unified Manager HTTPS certificate start date is later than the date on the cluster, or if the cluster has reached the maximum number of EMS notification destinations.
- Cluster acquisition fails,
au.log
:
ERROR [Thread-4] o.a.q.j.JmsConnection (JmsConnection.java:165) - Failed to connect to remote at: amqp://localhost:56072
WARN [Thread-4] c.n.a.d.a.DataCollectorTrigger (DataCollectorTrigger.java:210) - Failed to connect to Broker, will retry shortly
- Acquisition fails on particular times on a day which is temporarily fixed after a reboot/restart of a server only to be failed again
- Reported in
server_acq.log:
2024-05-21 10:55:23,416 ERROR [QpidJMS Connection Executor: ID:d5f45294-5f41-4e89-8a0c-45a91bcebd67:1] c.n.s.m.JmsBase (JmsBase.java:238) - Disconnected from Broker, retrying to connect
2024-05-21 10:55:23,406 ERROR [QpidJMS Connection Executor: ID:a3dc0377-2513-45f9-814a-9a0f9d239ac5:1] c.n.s.m.JmsBase (JmsBase.java:236) - Linked Exception: org.apache.qpid.jms.provider.exceptions.ProviderConnectionRemotelyClosedException: Connection closed by external action [condition = amqp:connection:forced]
2024-05-21 10:55:23,416 ERROR [QpidJMS Connection Executor: ID:a3dc0377-2513-45f9-814a-9a0f9d239ac5:1] c.n.s.m.JmsBase (JmsBase.java:238) - Disconnected from Broker, retrying to connect
2024-05-21 10:55:23,421 INFO [Thread-184] c.n.s.m.JmsBase (JmsBase.java:103) - Trying to connect to Broker