search

st-one-io / node-red-contrib-cip-ethernet-ip

A Node-RED node to interact with Allen Bradley / Rockwell PLCs
GNU General Public License v3.0
49 stars 22 forks source link

Unused flow with eth-ip endpoints, but crashed entire Node-RED instance due to unconnectable PLC #12

Open jlancasterhmma opened 4 years ago

jlancasterhmma commented 4 years ago

Hi,

I have an unused flow with several eth-ip endpoints in my development node-red environment. I noticed this weekend that the entire node-red instance had crashed. When I started it up again, I received the error below when node-red crashed. This error repeats every time I try to bring node-red online as long as this PLC is offline. I believe that PLC is down for weekend maintenance. I wanted to bring this to your attention, because this seems to crash an entire instance. I also tried adding a catch node in the unused flow, but the behavior was the same. I can provide any details you guys might need..

14 Sep 22:11:36 - [error] [eth-ip endpoint:xxx1] Error communicating with the PLC: Error: This socket has been ended by the other party

14 Sep 22:11:41 - Error: This socket has been ended by the other party at Controller.writeAfterFIN [as write] (net.js:407:14) at Controller.destroy (/home/xxx/.node-red/node_modules/ethernet-ip/src/enip/index.js:201:14) at destroyPLC (/home/xxx/.node-red/node_modules/node-red-contrib-cip-ethernet-ip/red/ethernet-ip.js:225:27) at closeConnection (/home/xxx/.node-red/node_modules/node-red-contrib-cip-ethernet-ip/red/ethernet-ip.js:245:13) at Timeout.connect (/home/xxx/.node-red/node_modules/node-red-contrib-cip-ethernet-ip/red/ethernet-ip.js:272:17) at listOnTimeout (internal/timers.js:531:17) at processTimers (internal/timers.js:475:7)