Hi all,
When trying to execute the Cassandra cluster migrator tool, it remains preparing the agents for migration, looking at the SLCCMigrator.txt found some errors about it Could not ping agent
2022-06-08T14:35:51.240|WARN |DataGateway.Migration.CC|Could not ping agent 22104 @ WIN-F9JBKVOMUHS. Retrying soon... Exception: Skyline.DataMiner.MessageBroker.Exceptions.RequestResponseTimeoutException: No responders are available for the request.
at Skyline.DataMiner.MessageBroker.SLMessageBroker.<RequestResponseInner>d__49.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SLDataGateway.Tools.CassandraCluster.Migration.UI.Messaging.NatsConnection.<RequestResponse>d__17`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SLDataGateway.Tools.CassandraCluster.Migration.UI.ViewModels.MainViewModel.<TryDiscoverAgents>d__14.MoveNext()
It's a 2 DMA's cluster, both of them are online and running Dataminer 10.2 CU3
From the troubleshooting section of the guide Cassandra Cluster Migrator - DataMiner Dojo, we tested on both agents and the cluster tag is empty
"cluster": {}
Using the Client test tool, we sent a NatsCustodianResetNatsRequest, tried to execute the SLCCMigrator tool again but nothing changes.
Both agents have the same config in the SLCloud.xml
SLMessageBroker_SLCCMigrator.txt log file always show the same messages.
2022-06-08 13:52:20.311|SLCCMigrator|New NATS connnection for WIN-F9JBKVOMUHS on nats://10.217.226.152:4222
2022-06-08 13:52:30.507|SLCCMigrator|RequestAsync request timed out.
2022-06-08 13:52:40.520|SLCCMigrator|RequestAsync request timed out.
2022-06-08 13:52:50.521|SLCCMigrator|RequestAsync request timed out.
Any idea what else could be checked to successfully execute the migration?
Hi Jens, Yes I tried and the status is the same.
Hey Edson
Try opening port 6222 (NATS clustering) and restarting both services, that should fix the problem
Regards
Hi Jaime, I did that and it worked. Thanks!
Have you tried restarting the NATS & NAS services?