search

bbindreiter / node-red-contrib-alexa-remote2-applestrudel

Node-Red Nodes for interacting with Alexa
https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel
MIT License
77 stars 21 forks source link

After updating to version 5.0.50, Node-Red restarts unexpectedly, approx. 15 - 20 times a day #202

Open italschwob opened 1 month ago

italschwob commented 1 month ago

After updating node-red-contrib-alexa-remote2-applestrudel to version 5.0.50, listening works sporadically and Node-Red restarts unexpectedly. Node-Red version 4.0.3, Node.js version: 20.17.0 Here are my error messages:

30 Sep 13:50:53 - [red] Uncaught Exception: 30 Sep 13:50:53 - [error] Error: getaddrinfo ENOTFOUND bob-dispatch-prod-eu.amazon.com at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) nodered.service: Main process exited, code=exited, status=1/FAILURE nodered.service: Failed with result 'exit-code'. nodered.service: Consumed 50.429s CPU time. nodered.service: Scheduled restart job, restart counter is at 3. Stopped nodered.service - Node-RED graphical event wiring tool. nodered.service: Consumed 50.429s CPU time. Started nodered.service - Node-RED graphical event wiring tool.

I hope someone can help me with my problem.

FW-Systeme commented 1 month ago

same issue, same Version....

tjareson commented 1 week ago

Same issue most likely here. Since update, I get to errors: Nov 12 03:41:15 server03 Node-RED[591]: 12 Nov 03:41:15 - [error] Error: read ECONNRESET Nov 12 03:41:15 server03 Node-RED[591]: at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) and: Nov 12 04:50:32 server03 Node-RED[31240]: 12 Nov 04:50:32 - [red] Uncaught Exception: Nov 12 04:50:32 server03 Node-RED[31240]: 12 Nov 04:50:32 - [error] Error: Client network socket disconnected before secure TLS connection was established

These errors are happening since upgrade to 5.0.50. applestrudel is the only node which is contacting external services via TLS connection, all other services are internal and unencrypted, which points a bit in the direction that there is an issue.

Is there a way how I can enable more detailed logs around what these nodes are doing?