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
2024-08-27T13:33:29: 27 Aug 13:33:29 - [error] [OpcUa-Client:Filo2] Client node error on: Filo2 error: ["Client not yet created & connected, cannot getEndpoints!"]
os --> Microsoft Windows Server 2022 Standard
nodejs --> 20.15
node-red --> 4.0.1
node-red-contrib-opcua --> 0.2.329
Good afternoon , my opc-ua client is giving the above error that occurs after a couple of hours of machine downtime.
More precisely the error occurs when the machine comes back online, the opc-ua client connection restores correctly after a while (15/20) by itself, during this time the client is unable to connect to the opc server and throw the above error alternating with recconect attempts.
thank you in advance
The text was updated successfully, but these errors were encountered:
I expect this is some timing problem as client object is created then it will list all available endpoints before creating session and activating it.
Perhaps server cannot provide endpoints always as client seems to give error.
I should update node-opcua package as it could contain improvements to this...
error
2024-08-27T13:33:29: 27 Aug 13:33:29 - [error] [OpcUa-Client:Filo2] Client node error on: Filo2 error: ["Client not yet created & connected, cannot getEndpoints!"]
os --> Microsoft Windows Server 2022 Standard
nodejs --> 20.15
node-red --> 4.0.1
node-red-contrib-opcua --> 0.2.329
Good afternoon , my opc-ua client is giving the above error that occurs after a couple of hours of machine downtime.
More precisely the error occurs when the machine comes back online, the opc-ua client connection restores correctly after a while (15/20) by itself, during this time the client is unable to connect to the opc server and throw the above error alternating with recconect attempts.
thank you in advance
The text was updated successfully, but these errors were encountered: