Local Cassandra IP issue

Solved780 views
1
0 Comments

Hello,

Got a local DMA running on my corporate laptop, no VM.

Yesterday was all good, clean boot, DMA running well.

This morning, connecting (after 10 hours time out on the cube client), stuck to “Retrieving initial data”..

From CassandraDriver.txt, it started yesterday evening:

2023/08/23 21:39:18.016|SLDBConnection|CassandraDriver|CRU|8|31|SLDataGateway.exe Warning: 0 :
2023/08/23 21:39:18.017|SLDBConnection|CassandraDriver|CRU|8|31|02023-08-23:19-39-18.016|Warning|Connection disconnected [id=23 – – RECONNECTING]
2023/08/23 21:39:18.017|SLDBConnection|CassandraDriver|CRU|8|41|SLDataGateway.exe Warning: 0 :
2023/08/23 21:39:18.017|SLDBConnection|CassandraDriver|CRU|8|41|02023-08-23:19-39-18.016|Warning|Attempting to restore connection failed. (attempt=1)
2023/08/23 21:39:23.019|SLDBConnection|CassandraDriver|CRU|8|41|SLDataGateway.exe Warning: 0 :
2023/08/23 21:39:23.019|SLDBConnection|CassandraDriver|CRU|8|41|02023-08-23:19-39-23.018|Warning|Attempting to restore connection failed. (attempt=2)
2023/08/23 21:39:28.023|SLDBConnection|CassandraDriver|CRU|8|41|SLDataGateway.exe Warning: 0 :
2023/08/23 21:39:28.023|SLDBConnection|CassandraDriver|CRU|8|41|02023-08-23:19-39-28.022|Warning|Attempting to restore connection failed. (attempt=3)

And still going:

2023/08/24 09:19:20.005|SLDBConnection|CassandraDriver|CRU|8|41|SLDataGateway.exe Warning: 0 :
2023/08/24 09:19:20.005|SLDBConnection|CassandraDriver|CRU|8|41|02023-08-24:07-19-20.003|Warning|Attempting to restore connection failed. (attempt=8386)
**********

SLErrors.txt:

Same start time of errors:

2023/08/23 21:39:13.043|SLDataMiner.txt|SLDataMiner.exe 10.3.2321.1738|22016|10872|CIPSettings::Init|ERR|-1|Opening device failed for adapter {B7A3E195-1592-11EE-8269-806E6F6E6963} (Software Loopback Interface 1): The system cannot find the file specified. (2)
2023/08/23 21:39:19.491|SLDataMiner.txt|SLDataMiner.exe 10.3.2321.1738|22016|10872|CIPSettings::Init|ERR|-1|Opening device failed for adapter {B7A3E195-1592-11EE-8269-806E6F6E6963} (Software Loopback Interface 1): The system cannot find the file specified. (2)
2023/08/23 21:44:05.159|SLBPAManager.txt|SLNet.exe|.ctor|ERR|0|106|Error while constructing ExternalBpaProcess. (Code: 0x80131500) Skyline.DataMiner.Net.Exceptions.DataMinerException: Failed to launch SLHelper (60s)
at SLHelperTypes.HelperWrapper.Launch(HandleMessageCallback messageCallback)
at Skyline.DataMiner.Net.BPA.ExternalBpaProcess..ctor(ILoggerWrapper logger)
2023/08/23 21:44:05.755|SLBPAManager.txt|SLNet.exe|.ctor|ERR|0|74|Error while constructing ExternalBpaProcess. (Code: 0x80131500) Skyline.DataMiner.Net.Exceptions.DataMinerException: Failed to launch SLHelper (60s)
at SLHelperTypes.HelperWrapper.Launch(HandleMessageCallback messageCallback)
at Skyline.DataMiner.Net.BPA.ExternalBpaProcess..ctor(ILoggerWrapper logger)
2023/08/23 21:46:05.259|SLBPAManager.txt|SLNet.exe|CleanupHelperStatus|ERR|0|106|(Code: 0x80131500) Skyline.DataMiner.Net.Exceptions.DataMinerException: Failed to launch SLHelper (60s)
at SLHelperTypes.HelperWrapper.Launch(HandleMessageCallback messageCallback)
at SLHelperTypes.HelperWrapper.Execute(HelperActionType actionType, Object[] args)
at Skyline.DataMiner.Net.BPA.ExternalBpaProcess.CleanupHelperStatus()
Failed to cleanup external SLHelper process
2023/08/23 21:46:05.789|SLBPAManager.txt|SLNet.exe|CleanupHelperStatus|ERR|0|74|(Code: 0x80131500) Skyline.DataMiner.Net.Exceptions.DataMinerException: Failed to launch SLHelper (60s)
at SLHelperTypes.HelperWrapper.Launch(HandleMessageCallback messageCallback)
at SLHelperTypes.HelperWrapper.Execute(HelperActionType actionType, Object[] args)
at Skyline.DataMiner.Net.BPA.ExternalBpaProcess.CleanupHelperStatus()
Failed to cleanup external SLHelper process
2023/08/23 21:47:04.430|SLASPConnection.txt|SLASPConnection.exe 10.3.2321.1738|7728|1328|CServiceModule::LoadIPAddresses|ERR|-1|Error 2 while fetching IP adapter info for SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{7ED71FE3-845E-48DC-9E5B-83741DC2F717} (DHCP=1)
2023/08/23 21:47:04.430|SLASPConnection.txt|SLASPConnection.exe 10.3.2321.1738|7728|1328|CServiceModule::LoadIPAddresses|ERR|-1|Error 2 while fetching IP adapter info for SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{68D1E09B-0E00-4AD2-AB79-3F5CFD3E40C2} (DHCP=0)
2023/08/23 21:47:04.430|SLASPConnection.txt|SLASPConnection.exe 10.3.2321.1738|7728|1328|CServiceModule::LoadIPAddresses|ERR|-1|Error 2 while fetching IP adapter info for SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{84246670-86CC-4D3E-99E7-D68D2F25D7A5} (DHCP=1)
2023/08/23 21:52:05.779|SLBPAManager.txt|SLNet.exe|.ctor|ERR|0|106|Error while constructing ExternalBpaProcess. (Code: 0x80131500) Skyline.DataMiner.Net.Exceptions.DataMinerException: Failed to launch SLHelper (60s)
at SLHelperTypes.HelperWrapper.Launch(HandleMessageCallback messageCallback)
at Skyline.DataMiner.Net.BPA.ExternalBpaProcess..ctor(ILoggerWrapper logger)

I think it started from here: SLDataminer.txt:

2023/08/23 21:39:12.969|SLDataMiner|22016|10872|CDataMiner::AddressChangeHandler|INF|-1|IPV4 change received
2023/08/23 21:39:13.043|SLDataMiner.exe 10.3.2321.1738|22016|10872|CIPSettings::Init|ERR|-1|Opening device failed for adapter {B7A3E195-1592-11EE-8269-806E6F6E6963} (Software Loopback Interface 1): The system cannot find the file specified. (2)
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 17 has name Masson Dock
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 14 has name Local Area Connection* 1
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 11 has name Local Area Connection* 2
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 13 has name Wi-Fi
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 16 has name Bluetooth Network Connection
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 1 has name Loopback Pseudo-Interface 1
2023/08/23 21:39:13.047|SLDataMiner.exe 10.3.2321.1738|22016|10872|CHardware::InitializeNetwork|CRU|-1|Interface 34 has name vEthernet (Default Switch)

I have static IPs assigned to my cabled and wifi connection. Seems that my Wifi got disconnected yesterday evening and now that I re-enabled it I got my DMA running again.

Question is, how can I clean my network settings in the DMA. At first I set it up in the office, now that I am remote (home) I had issues with ghost IPs from the office, but now I need to enable my Wifi connection on top of my wired one to get the DMA working, or say get Cassandra to use the wired IP ?

Thanks in advanced.

Yvon

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 28th August 2023

1 Answer

3
3.49K 2 Comments

A couple of things can be done:

  1. Set the order of Network Adapters. For example your cabled connection can be first followed by your Wi-Fi connection.
  2. Use hostnames instead of IPs in your DMS.xml and SLCloud.xml files. With this your agent will always be up and running if you switch between cable & Wi-Fi.
  3. Unless there is a specific reason you can leave your Cassandra running on local IP address (127.0.0.1). The agent will be able to connect to the DB you wont need to bother if your connection type changes.
Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 28th August 2023
Yvon Masson commented

Thanks Wale.

So, in Dataminer.xml I changed the MAC to my wired one (it was set to the Wifi one).

DMS.xml, I set it to “localhost”, not 127.0.0.1 and it reverted to my Wired IP

SLCLoud.xml: same, reverted from localhost th the real IP.

Nevertheless, it is now fine with my Wifi Disabled.

Thanks again.
Wale Oguntoyinbo [SLC] [DevOps Advocate] commented

Glad your issue is resolved but to clarify; In the DMS.xml and SLCloud.xml files use the actual hostname of your computer instead of localhost. You can retrieve this from command prompt using ‘hostname’ command. With that and you will not need to disable your Wi-Fi.