You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been experiencing an intermittent issue with the Open62541 LDS-ME server on Windows 10 Pro and don't know what is causing it. After a fresh bootup on Windows the LDS-ME server generally works fine, but after a certain point it will stop discovering servers. I do not know what is triggering it to stop discovering servers as it seems to happen randomly each time I test it. Restarting does not seem to fix this issue, however shutting my PC down, waiting for a minute, then booting my PC back to Windows does seem to temporarily fix it. This problem is only on Windows - my Ubuntu build works perfectly every time.
Background Information / Reproduction Steps
I do not know how to reproduce this issue reliably. The way I get it to trigger is by booting up Windows and running the discovery_server_lds.exe and checking if it sees the servers I know it should be able to see. If it is able to see them, then I will just repeatedly run discovery_server_lds.exe until it can no longer see them. If this does not work, I will do some other work for a while and check again after an hour or so and it will often no longer work then. Running as an administrator makes no difference.
I have also validated that discovery still is possible from my PC using the UA Foundation's official lds-me implementation (https://opcfoundation.github.io/UA-LDS/). Note that I am not running this LDS server as a service. I have disabled it as a service and only run it in debug mode to get debug messages on what servers it has found. I have provided a log of its debug messages below. The OPC Foundation's lds-me server seems to show the same logs regardless of if the intermittent issue with Open62541 is occuring.
All logs shown below are output from the example LDS-ME server (https://github.com/open62541/open62541/blob/master/examples/discovery/server_lds.c) built with Open62541 1.4. The last few entries in each log dump indicate what servers were found. Wireshark logs are packets filtered using the term 'mdns contains "opcua-tcp" and ip.src==MY_IP' which were captured starting right before starting discovery_server_lds and ending ~1minute after starting it up.
Logs from before the intermittent issue hits on Windows 10:
Console Log:
PS C:\Users\LOCALUSER\projects\open62541\build\bin\examples> .\discovery_server_lds.exe
[2024-05-03 12:23:12.401 (UTC-0700)] info/eventloop Starting the EventLoop
[2024-05-03 12:23:12.401 (UTC-0700)] warn/server AccessControl: Unconfigured AccessControl. Users have all permissions.
[2024-05-03 12:23:12.401 (UTC-0700)] info/server AccessControl: Anonymous login is enabled
[2024-05-03 12:23:12.401 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-03 12:23:12.423 (UTC-0700)] warn/userland ServerUrls already set. Overriding.
[2024-05-03 12:23:12.423 (UTC-0700)] warn/server AccessControl: Unconfigured AccessControl. Users have all permissions.
[2024-05-03 12:23:12.424 (UTC-0700)] info/server AccessControl: Anonymous login is enabled
[2024-05-03 12:23:12.424 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-03 12:23:12.424 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-03 12:23:12.425 (UTC-0700)] warn/server Maximum SecureChannels count not enough for the maximum Sessions count
[2024-05-03 12:23:12.425 (UTC-0700)] info/network TCP | Listening on all interfaces
[2024-05-03 12:23:12.431 (UTC-0700)] info/network TCP 280 | Creating listen socket for "LOCALUSER-ENG-25.BusinessName.local" (with local hostname "LOCALUSER-ENG-25") on port 4840
[2024-05-03 12:23:12.431 (UTC-0700)] info/server New DiscoveryUrl added: opc.tcp://LOCALUSER-ENG-25:4840
[2024-05-03 12:23:12.431 (UTC-0700)] info/network TCP 468 | Creating listen socket for "LOCALUSER-ENG-25.BusinessName.local" (with local hostname "LOCALUSER-ENG-25") on port 4840
[2024-05-03 12:23:12.441 (UTC-0700)] info/network UDP 464 | New listen socket for "224.0.0.251" on port 5353
[2024-05-03 12:23:12.441 (UTC-0700)] warn/network UDP 464 | No network interface defined for multicast. That means the first suitable network interface is used.
[2024-05-03 12:23:12.442 (UTC-0700)] warn/network UDP 460 | No network interface defined for multicast. That means the first suitable network interface is used.
[2024-05-03 12:23:12.443 (UTC-0700)] info/network UDP 460 | New connection to "224.0.0.251" on port 5353
[2024-05-03 12:23:12.443 (UTC-0700)] warn/discovery Cannot add mDNS Record: BadOutOfRange
[2024-05-03 12:23:14.504 (UTC-0700)] info/server Multicast DNS: found server: opc.tcp://User_1-OptiPlex-3080:4840
[2024-05-03 12:23:14.505 (UTC-0700)] info/server Multicast DNS: found server: opc.tcp://10.0.0.150:4845
Wireshark Log:
Logs from after the intermittent issue hits on Windows:
Console Log:
PS C:\Users\LOCALUSER\projects\open62541\build\bin\examples> ./discovery_server_lds.exe
[2024-05-02 12:02:44.466 (UTC-0700)] info/eventloop Starting the EventLoop
[2024-05-02 12:02:44.466 (UTC-0700)] warn/server AccessControl: Unconfigured AccessControl. Users have all permissions.
[2024-05-02 12:02:44.466 (UTC-0700)] info/server AccessControl: Anonymous login is enabled
[2024-05-02 12:02:44.466 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-02 12:02:44.482 (UTC-0700)] warn/userland ServerUrls already set. Overriding.
[2024-05-02 12:02:44.482 (UTC-0700)] warn/server AccessControl: Unconfigured AccessControl. Users have all permissions.
[2024-05-02 12:02:44.482 (UTC-0700)] info/server AccessControl: Anonymous login is enabled
[2024-05-02 12:02:44.498 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-02 12:02:44.498 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-02 12:02:44.498 (UTC-0700)] warn/server Maximum SecureChannels count not enough for the maximum Sessions count
[2024-05-02 12:02:44.498 (UTC-0700)] info/network TCP | Listening on all interfaces
[2024-05-02 12:02:44.513 (UTC-0700)] info/network TCP 280 | Creating listen socket for "LOCALUSER-ENG-25.BusinessName.local" (with local hostname "LOCALUSER-ENG-25") on port 4840
[2024-05-02 12:02:44.513 (UTC-0700)] info/server New DiscoveryUrl added: opc.tcp://LOCALUSER-ENG-25:4840
[2024-05-02 12:02:44.513 (UTC-0700)] info/network TCP 468 | Creating listen socket for "LOCALUSER-ENG-25.BusinessName.local" (with local hostname "LOCALUSER-ENG-25") on port 4840
[2024-05-02 12:02:44.513 (UTC-0700)] info/network UDP 460 | New listen socket for "224.0.0.251" on port 5353
[2024-05-02 12:02:44.513 (UTC-0700)] warn/network UDP 460 | No network interface defined for multicast. That means the first suitable network interface is used.
[2024-05-02 12:02:44.513 (UTC-0700)] warn/network UDP 456 | No network interface defined for multicast. That means the first suitable network interface is used.
[2024-05-02 12:02:44.513 (UTC-0700)] info/network UDP 456 | New connection to "224.0.0.251" on port 5353
[2024-05-02 12:02:44.513 (UTC-0700)] warn/discovery Cannot add mDNS Record: BadOutOfRange
Wireshark Log:
(There were no packets found using the filter I described above)
Logs from Linux build (works perfectly every time):
[LOCALUSER-eng-25][LOCALUSER][~/tmp/open62541/build/bin/examples][1.4]
: ./discovery_server_lds
[2024-05-03 08:32:03.184 (UTC-0700)] info/eventloop Starting the EventLoop
[2024-05-03 08:32:03.185 (UTC-0700)] warn/server AccessControl: Unconfigured AccessControl. Users have all permissions.
[2024-05-03 08:32:03.185 (UTC-0700)] info/server AccessControl: Anonymous login is enabled
[2024-05-03 08:32:03.185 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-03 08:32:03.186 (UTC-0700)] info/session TCP 0 | SC 0 | Session "Administrator" | AddNode (i=15303): No TypeDefinition. Use the default TypeDefinition for the Variable/Object
[2024-05-03 08:32:03.189 (UTC-0700)] info/session TCP 0 | SC 0 | Session "Administrator" | AddNode (i=25451): No TypeDefinition. Use the default TypeDefinition for the Variable/Object
[2024-05-03 08:32:03.193 (UTC-0700)] warn/userland ServerUrls already set. Overriding.
[2024-05-03 08:32:03.193 (UTC-0700)] warn/server AccessControl: Unconfigured AccessControl. Users have all permissions.
[2024-05-03 08:32:03.193 (UTC-0700)] info/server AccessControl: Anonymous login is enabled
[2024-05-03 08:32:03.193 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-03 08:32:03.193 (UTC-0700)] warn/server x509 Certificate Authentication configured, but no encrypting SecurityPolicy. This can leak credentials on the network.
[2024-05-03 08:32:03.193 (UTC-0700)] warn/server Maximum SecureChannels count not enough for the maximum Sessions count
[2024-05-03 08:32:03.193 (UTC-0700)] info/network TCP | Listening on all interfaces
[2024-05-03 08:32:03.193 (UTC-0700)] info/network TCP 4 | Creating listen socket for "0.0.0.0" (with local hostname "LOCALUSER-eng-25") on port 4840
[2024-05-03 08:32:03.193 (UTC-0700)] info/server New DiscoveryUrl added: opc.tcp://LOCALUSER-eng-25:4840
[2024-05-03 08:32:03.193 (UTC-0700)] info/network TCP 5 | Creating listen socket for "::" (with local hostname "LOCALUSER-eng-25") on port 4840
[2024-05-03 08:32:03.193 (UTC-0700)] info/network UDP 6 | New listen socket for "224.0.0.251" on port 5353
[2024-05-03 08:32:03.194 (UTC-0700)] warn/network UDP 6 | No network interface defined for multicast. The first suitable network interface is used.
[2024-05-03 08:32:03.194 (UTC-0700)] warn/network UDP 7 | No network interface defined for multicast. The first suitable network interface is used.
[2024-05-03 08:32:03.194 (UTC-0700)] info/network UDP 7 | New connection to "224.0.0.251" on port 5353
[2024-05-03 08:32:03.194 (UTC-0700)] warn/discovery Cannot add mDNS Record: BadOutOfRange
[2024-05-03 08:32:05.196 (UTC-0700)] info/server Multicast DNS: found server: opc.tcp://User_1-OptiPlex-3080:4840
[2024-05-03 08:32:05.196 (UTC-0700)] info/server Multicast DNS: found server: opc.tcp://10.0.0.150:4845
Wireshark Logs:
Logs from the UA Foundation's LDS-ME implementation for Windows after Open62541 intermittent issue hits:
Description
I have been experiencing an intermittent issue with the Open62541 LDS-ME server on Windows 10 Pro and don't know what is causing it. After a fresh bootup on Windows the LDS-ME server generally works fine, but after a certain point it will stop discovering servers. I do not know what is triggering it to stop discovering servers as it seems to happen randomly each time I test it. Restarting does not seem to fix this issue, however shutting my PC down, waiting for a minute, then booting my PC back to Windows does seem to temporarily fix it. This problem is only on Windows - my Ubuntu build works perfectly every time.
Background Information / Reproduction Steps
I do not know how to reproduce this issue reliably. The way I get it to trigger is by booting up Windows and running the discovery_server_lds.exe and checking if it sees the servers I know it should be able to see. If it is able to see them, then I will just repeatedly run discovery_server_lds.exe until it can no longer see them. If this does not work, I will do some other work for a while and check again after an hour or so and it will often no longer work then. Running as an administrator makes no difference.
I have also validated that discovery still is possible from my PC using the UA Foundation's official lds-me implementation (https://opcfoundation.github.io/UA-LDS/). Note that I am not running this LDS server as a service. I have disabled it as a service and only run it in debug mode to get debug messages on what servers it has found. I have provided a log of its debug messages below. The OPC Foundation's lds-me server seems to show the same logs regardless of if the intermittent issue with Open62541 is occuring.
All logs shown below are output from the example LDS-ME server (https://github.com/open62541/open62541/blob/master/examples/discovery/server_lds.c) built with Open62541 1.4. The last few entries in each log dump indicate what servers were found. Wireshark logs are packets filtered using the term 'mdns contains "opcua-tcp" and ip.src==MY_IP' which were captured starting right before starting discovery_server_lds and ending ~1minute after starting it up.
Logs from before the intermittent issue hits on Windows 10:
Console Log:
Wireshark Log:
Logs from after the intermittent issue hits on Windows:
Console Log:
Wireshark Log:
(There were no packets found using the filter I described above)
Logs from Linux build (works perfectly every time):
Wireshark Logs:
Logs from the UA Foundation's LDS-ME implementation for Windows after Open62541 intermittent issue hits:
Used CMake options:
Checklist
Please provide the following information:
UA_LOGLEVEL
set as low as necessary) attachedThe text was updated successfully, but these errors were encountered: