Hello,
since i updated my Node-Red to v1.0.6 with the installer script from the page, its restarting at some random points.
The log shown in "node-red-log" shows me following:
8 Jun 22:34:43 - [red] Uncaught Exception:
8 Jun 22:34:43 - Error: connect ETIMEDOUT 192.168.2.169:49000
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service RestartSec=100ms expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 4.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
8 Jun 22:34:44 - [info]
Welcome to Node-RED
Any idea?
it seems to be timing out trying to connect to 192.168.2.169 port 49000
Do you know what that is ?
192.168.2.169 is my Fritzbox, and port 49000 is used for IOBrokers TR-064 Adapter, which is monitoring the calls on my Fritzbox.
See more here. The problem got fixed.
opened 08:46PM - 08 Jun 20 UTC
closed 08:50PM - 08 Jun 20 UTC
Please tell us about your environment:
[1.0.6] Node-RED version:
[10.20.1] Node.js version:
[6.14.4] npm version:
[Raspbian] Platform/OS:
[Firefox 76.0.1] Browser:
Hello,
my Node-Red restarts randomly after i updated...
Is it a custom node or are you using built in TCP/UDP nodes?
If its a custom node, then the developer should be made aware of his node crashing node-red (basically - no node should bring down node-red - there should be no Uncaught Exception
s)
If you can find it in the flows library, there may be a link to the developers repository where you should be able to raise an issue (if one doesnt exist already). If its not abandoned, the dev should fix it up.
Already identified -see github issue linked above
Obviously I didn't read that properly DOH!
system
Closed
8 August 2020 18:50
7
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.