Node Red Fail Service

#1

Hi folks,

I'm running the red node in Linux (raspbian) and am experiencing some problems.

It constantly restarts unexpectedly by displaying the following log messages:

25 Jul 02:35:47 - [red] Uncaught Exception: 25 Jul 02:35:47 - Error
[ERR_SOCKET_CANNOT_SEND]: Unable to send data
at Socket.onListenError (dgram.js:362:22) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at Socket.emit
(events.js:211:7) at _handle.lookup (dgram.js:267:14) at
_combinedTickCallback (internal/process/next_tick.js:141:11) at process._tickCallback (internal/process/next_tick.js:180:9)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state. nodered.service: Failed
with result 'exit-code'. nodered.service: Service hold-off time over,
scheduling restart. Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.

I have already removed several components but I could not identify something that is causing tautomation

This behavior is hurting my automations a lot.

Any help would be appreciated!

Thank you

0 Likes

Fail Service Node Red
#2

What nodes are you using that do something in the local network? One of them is not handling this error properly and needs to be fixed. But first you have to identify which node is causing it.

0 Likes

#3

Also post what you see at the start of the node-red log so we can see all the versions etc.

0 Likes