Issue with LDS when more than on UA Server is registering with LDS on same system|OPC UA Implementation: Stacks, Tools, and Samples|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
Issue with LDS when more than on UA Server is registering with LDS on same system
Avatar
Mohammad Areef
Member
Members
Forum Posts: 3
Member Since:
04/15/2015
sp_UserOfflineSmall Offline
1
10/26/2022 - 10:31
sp_Permalink sp_Print

Hello,
I am using LDS V1.04.403.476. We have 2 OPC UA Servers installed on the same system.
When I install the first OPC UA Server, during installation we exchange the certificates with LDS and restart LDS, Bonjour and our OPC UA Server at the end of the installation process. After this, when we try connecting to LDS from any UA Client, we can see our UA Server showing up under LDS.
Now, I install my second UA Server and we repeat the same process of certificate exchanges and services restart. However, after this LDS Server does not return any of the UA Servers when queried from UA Client. Some time it works by restarting the services again, but >90% of time, nothing works and we end up always discovering services manually.

In opcualds log file, we see the error as "[6512]: ualds_findserversonnetwork_socketEventCallback: DNSServiceProcessResult returned error -65541". Checked the mDNSResponder service and it shows as running properly. Checked the Bonjour browser and can see LDS showing up in there. Attached screenshot shows multiple windows related to this.

Any suggestion what is going wrong here?

Screenshot

Avatar
Randy Armstrong
Admin
Forum Posts: 1564
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
10/26/2022 - 15:00
sp_Permalink sp_Print

There are three ways to discover servers FindServers, FindServersOnNetwork and using mDNS directly.

Which ways have you tried and what are the results?

Avatar
Mohammad Areef
Member
Members
Forum Posts: 3
Member Since:
04/15/2015
sp_UserOfflineSmall Offline
3
11/07/2022 - 13:42
sp_Permalink sp_Print

We are using mDNS based discovery.

Avatar
Randy Armstrong
Admin
Forum Posts: 1564
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
4
11/08/2022 - 03:14
sp_Permalink sp_Print

you should be able to monitor mDNS traffic with a generic client.

1) start the LDS;

2) start server A and confirm the mDNS announce messages are sent for server A;

3) start server B and confirm the mDNS announce messages are sent for server B;

repeat with server B first.

repeat by stop server A and server B but do not restart the LDS.

In the last test if you do not get the messages it may be because the LDS has not cleared its cache so it does not see the servers as new and does not send a new mDNS announce (parameters passed to the LDS by the server control this).

I will have more suggestions once I see the result of those tests.

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 30
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1435
Posts: 4855