I'm running a DMA on a laptop, so my IP address changes depending on whether I'm working from home or in the office. Normally I update the values in:
- C:\Skyline DataMiner\Configurations\ClusterEndpoints.json
- C:\Program Files\Skyline Communications\DataMiner BrokerGateway\appsettings.runtime.json
After updating those files and restarting the DataMiner BrokerGateway process (via Task Manager), everything usually works fine.
However, this time the DataMiner Agent no longer starts. I get the message: "The DataMiner Agent did not respond in time. The server might be rebooting or the DataMiner software might be restarting."
In the BrokerGateway logs I see repeated errors indicating that it's still trying to connect to a wrong/outdated address (even though I updated all the usual files): "A connection attempt failed because the connected party did not properly respond... (xxx.xxx.xxx.xxx:xxx) SocketException (10060)".
Is there anywhere else DataMiner or BrokerGateway might be storing the old IP address that I need to update? Or anything else I can do to resolve this issue?
Thanks in advance!
There's a document on changing the IP address of a DataMiner Agent here: Changing the IP of a DMA | DataMiner Docs
For BrokerGateway, you'll need the parts about "nats-server" (skip any instructions on NATS service)
As follow up: eventually the root cause for this problem ended up being an expired STaaS service token rather than a NATS/BrokerGateway configuration issue ( https://docs.dataminer.services/dataminer/Troubleshooting/Procedures/STaaS_Error_messages.html#the-session-token-has-expired )
Thanks a lot for getting to the bottom of this, Wouter! I’ve updated the “Troubleshooting – Startup issues” page to include the issue and its resolution: https://docs.dataminer.services/dataminer/Troubleshooting/Troubleshooting_Flowcharts/Troubleshooting_Startup_Issues.html
Hi Wouter, thank you for the suggestion! I followed the steps on this page, but to no avail. The files mentioned on the page (appsettings.runtime.json, DMS.xml, ClusterEndpoints.json, and nats-server.config) contained no references to the old IP address.