Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client not yet created & connected, cannot getEndpoints! #724

Open
PLCs7 opened this issue Aug 27, 2024 · 1 comment
Open

Client not yet created & connected, cannot getEndpoints! #724

PLCs7 opened this issue Aug 27, 2024 · 1 comment

Comments

@PLCs7
Copy link

PLCs7 commented Aug 27, 2024

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

@mikakaraila
Copy link
Owner

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants