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

Reconnect issue #299

Open
vigh-barnabas opened this issue Nov 13, 2024 · 1 comment
Open

Reconnect issue #299

vigh-barnabas opened this issue Nov 13, 2024 · 1 comment

Comments

@vigh-barnabas
Copy link

Which node-red-contrib-iiot-opcua version are you using?

4.1.2

What happened?

I know that this package is no longer maintained but i have a question. If you have the time to look at it I would appreciate it.

If an OPC server is turned off for a longer time like 5-6+ hours I see it in the logs that the server closed the Session.
Server: closing SESSION active ClientSession1 because of timeout = 60000 has expired without a keep alive
But the listen node status stays in "Listen (xxx)"

And if the OPC server is turned back than a listen node doesn't reconnect automatically and i need to restart the flow to make it work.
What could be the problem?

In the logs I see warning likes this:
warning : ClientSessionKeepAliveManager#ping_server Invalid Channel after performing transaction on ReadRequest

Server

OPCUA-IIoT-Server Node

How can this be reproduced?

Turn off the OPC server for more than 6+ hours

What did you expect to happen?

No response

Other Information

No response

Copy link

This issue is stale because it has been open 60 days with no activity. It will be closed in 15 days, but can be saved by removing the stale label or commenting.

@github-actions github-actions bot added the Stale label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant