"Error connecting to PLC: Error: read ECONNRESET" about node-red-contrib-s7 HOT 11 CLOSED

Hi @Spawn2qc

I think the issue might be with a connection leak we're having under some circumstances. In the case we have a connection problem, we currently ask the library to connect again, but without creating a new library instance, and then the connection leaks

It might be in your case that the PLC is not accepting connections anymore because of these leaked connection, and therefore it logs these ECONNRESET errors.

I've been testing the fix for this in the past weeks, and it looks like the problem is solved. I'll publish a new version either today or tomorrow, so you can update your node and check if the problem has been fixed

from node-red-contrib-s7.

Just published 1.5.0 that might fix the issue. Could you please update and check it?

from node-red-contrib-s7.

Hi @gfcittolin
I think you are right about the PLC not accepting connections anymore.
This morning, I reboot all the system and the S7-1200 must have reset its connection because there is no more error in the debug window.
Yesterday, I reboot Node-RED only, not the S7-1200.
So, maybe, the "leaked" connection in the S7-1200 were still count.
There is 8 S7 connections limit, maybe it was bust.

I will update S7 node to 1.5.0 monday morning and let you know if something goes wrong, else it is solve.
Thank you very much for your support, it is very appreciate!

from node-red-contrib-s7.

My pleasure. Let me know if it works now so we can close this issue.

from node-red-contrib-s7.

Hi every body,
I am having exactly the same issue using the latest release of the node-red-contrib-s7 1.5.0.
Indeed, in one hand i am getting the error : "Error connecting to PLC: error: read ECONNRESET" continuously and in the other hand, i receive the data well! However, after a certain period of time, the node-red crashes.

Please find below the main configurations my architecture.

configuration:
PLC S7-1200
node red 0.18.4
node-red-contrib-s7 1.5.0
OS Ubuntu 16.0.4

Does anybody have an idea or can help!? It's an emergency ... Thanks

Best regards

from node-red-contrib-s7.

That is bad news. Could you please:

• Check the connection resources of your S7-1200 and get the available connections, to confirm our hypothesis that we're leaking connections
• Post here the stack trace of Node-RED when it crashes, so we can track down where it fails
• Enable the debug mode on the PLC config on node-red, and then try to simulate the issue. Then get the logs of node-red and post here too, so we can analyze what's wrong.

from node-red-contrib-s7.

Just released 1.5.1, there was another connection leak case I could simulate here. The leak happened when the node was trying to reconnect to the PLC, and the flow was redeployed. Could you guys please test it out?

from node-red-contrib-s7.

Thanks for your contribution, We are test it and we'll give you the result

from node-red-contrib-s7.

I tested the 1.5.1 release yesterday, and everything works fine. I no longer have the error message.
Thanks for your reactivity.

Best regards

from node-red-contrib-s7.

Thanks for testing!

from node-red-contrib-s7.

Hi,
I have descripted problem above!
But I can't get data from my plc.
The node worked fine for one week but then I get these Errors:

I do several things:
-Reset the SPS
-uninstall the node and install it new
-upgrading node-red.

• I checked the Ressources
  
  -I checked the mechanism
  

but the ERROR is still there.
What else can I do?
Thanks!

from node-red-contrib-s7.