I have node-red running in a docker container and it works well for a few days. Then it crashes.
Last relevant log lines before the crash indicate that some nodes had communication problems. But that shouldn't cause the container to crash.
Any hints?
7 Sep 13:02:52 - [error] [alexa-home-conf:c05e67ac.2ebed8] Error: getaddrinfo EAI_AGAIN alexa-node-red.hardill.me.uk:8883
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
7 Sep 13:03:43 - [error] [alexa-home-conf:c05e67ac.2ebed8] Error: getaddrinfo EAI_AGAIN alexa-node-red.hardill.me.uk:8883
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
7 Sep 13:03:56 - [error] [pushover:Sende Pushover Nachricht] [57-pushover.js] Error: Error: getaddrinfo ENOTFOUND api.pushover.net api.pushover.net:443
7 Sep 13:03:56 - [red] Uncaught Exception:
7 Sep 13:03:56 - SyntaxError: Unexpected token u in JSON at position 0
at JSON.parse (<anonymous>)
at /data/node_modules/node-red-node-pushover/57-pushover.js:103:33
at ClientRequest.<anonymous> (/data/node_modules/pushover-notifications/lib/pushover.js:254:7)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at TLSSocket.socketErrorListener (_http_client.js:401:9)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at emitErrorNT (internal/streams/destroy.js:66:8)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-red-docker@1.0.0 start: `node $NODE_OPTIONS node_modules/node-red/red.js -v $FLOWS "--userDir" "/data"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-red-docker@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /usr/src/node-red/.npm/_logs/2019-09-07T13_03_58_352Z-debug.log
