Schmetterfliege
commented
2 years ago Sorry for the format... in short: the connection broke down at 08:15, NR started crashing constantly at 15:00, for ~ 2 hours straight
Closed Schmetterfliege closed 1 year ago
Schmetterfliege
commented
2 years ago Sorry for the format... in short: the connection broke down at 08:15, NR started crashing constantly at 15:00, for ~ 2 hours straight
windkh
commented
2 years ago Normally it should look like this:
windkh
commented
2 years ago What hardware do you use? A raspberry?
Schmetterfliege
commented
2 years ago @windkh Hi, yes, a Pi 4B 4gb
The errors are the same, but NR crashed with every one of them^^
windkh
commented
2 years ago Does the same happen when you just pull the network cable?
Schmetterfliege
commented
2 years ago I can try next week. Problem is that my iobroker is running on that raspi, so unplugging it would also disconnect everything else, and it took ~7 hours for NR to start crashing after the network was gone
windkh
commented
2 years ago Hm 7 hours …. maybe I could prolong the polling timeout as soon as this happens but then it would just crash later. Maybe you can check if the rasp ran out of memory or disk space?
Schmetterfliege
commented
2 years ago Damn, I updated my NR in IoBroker, and now I can't install this node again.... grrrrrrr
EDIT: nevermind... same "issue" as before. That stupid IoBroker Adapter is still using that damn old version -.-
windkh
commented
2 years ago Damn, I updated my NR in IoBroker, and now I can't install this node again.... grrrrrrr
What do you mean? Updated to what?
Schmetterfliege
commented
2 years ago See edit, was my fault again. Sorry! The upgrade of the IoBroker Node Red Adapter downgraded my Node Red from 2.2.0 back to 1.3.7 again....
windkh
commented
2 years ago 1.3.7 should work. What nodejs version do you use?
Schmetterfliege
commented
2 years ago v12.20
windkh
commented
2 years ago Should work, too
Schmetterfliege
commented
2 years ago Well... I don't get it. I tried fixing it by "accidentally" upgrading NR to 2.2.0 again - just like I did before. But it didn't upgrade. Now I upgraded my IoBroker itself, which also upgraded the js controller, and now it works fine with 1.3.7. Your Node was suddenly shown again. I'll just be happy and don't question it :D
windkh
commented
2 years ago Ok don‘t panic
Schmetterfliege
commented
2 years ago @windkh Today I again had no network due to Vodafone issues. However, they didn't last long. First interruption was ~ 19.30, lasted about 2 minutes or so. Another one just before 20.00, lasted for 6 minutes or so. At the second interruption, NR apparently had crashed again. Here's the log from IoBroker:
`
2022-03-11 19:29:07.152 - error: tado.0 (24567) Issue at setZoneOverlay: 'Error: No internet connection detected!'. Based on config {"setting":{"type":"HEATING","power":"OFF"},"termination":{"typeSkillBasedApp":"MANUAL","durationInSeconds":null}} -- 2022-03-11 19:29:07.181 - error: tado.0 (24567) Issue at setZoneOverlay: 'Error: No internet connection detected!'. Based on config {"setting":{"type":"HEATING","power":"OFF"},"termination":{"typeSkillBasedApp":"MANUAL","durationInSeconds":null}} 2022-03-11 19:29:28.167 - error: tado.0 (24567) Issue at state change: Error: No internet connection detected! 2022-03-11 19:29:28.198 - error: tado.0 (24567) Issue at state change: Error: No internet connection detected! 2022-03-11 19:50:35.150 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.portalstate.outgoing" has to be type "string" but received type "boolean" 2022-03-11 19:51:24.949 - info: sonoff.0 (24361) Client [Wüstenbaum-Sensor] reconnected. Old secret 1647013288237_842. New secret 1647024684938_8880 2022-03-11 19:52:12.918 - info: sonoff.0 (24361) Client [Wüstenbaum-Sensor] reconnected. Old secret 1647024684938_8880. New secret 1647024732917_1716 2022-03-11 19:52:21.782 - info: sonoff.0 (24361) Client [Büro Schreibtisch] reconnected. Old secret 1647013286127_5932. New secret 1647024741781_8711 2022-03-11 19:52:28.109 - info: sonoff.0 (24361) Client [Steckdose Fritzbox] reconnected. Old secret 1647013280504_1031. New secret 1647024748108_4063 2022-03-11 19:52:28.395 - info: sonoff.0 (24361) Client [Pflanzenlicht] reconnected. Old secret 1647013278753_1544. New secret 1647024748394_7846 2022-03-11 19:52:28.929 - info: sonoff.0 (24361) Client [Aquarium Licht] reconnected. Old secret 1647013279997_4164. New secret 1647024748929_5217 2022-03-11 19:52:29.302 - info: sonoff.0 (24361) Client [Wohnzimmer Sideboard] reconnected. Old secret 1647013302626_5013. New secret 1647024749302_5729 2022-03-11 19:52:31.555 - info: sonoff.0 (24361) Client [Vitrinenlicht] reconnected. Old secret 1647013291801_1654. New secret 1647024751554_411 2022-03-11 19:52:31.849 - info: sonoff.0 (24361) Client [Aquarium CO2] reconnected. Old secret 1647013303127_29. New secret 1647024751848_1081 2022-03-11 19:52:34.767 - info: sonoff.0 (24361) Client [Aquarium Filter] reconnected. Old secret 1647013295079_4322. New secret 1647024754766_7202 2022-03-11 19:52:39.844 - info: sonoff.0 (24361) Client [Schlafzimmer_TV] reconnected. Old secret 1647013292144_2076. New secret 1647024759843_6615 2022-03-11 19:52:42.534 - info: sonoff.0 (24361) Client [Nachttisch Tamara] reconnected. Old secret 1647013289856_3080. New secret 1647024762529_9408 2022-03-11 19:53:32.795 - info: sonoff.0 (24361) Client [Aquarium Filter] reconnected. Old secret 1647024754766_7202. New secret 1647024812794_2993 2022-03-11 19:53:41.683 - info: sonoff.0 (24361) Client [Wohnwand] connection closed: timeout 2022-03-11 19:56:04.236 - error: info.0 (24525) Error: getaddrinfo EAI_AGAIN raw.githubusercontent.com 2022-03-11 20:00:05.048 - error: tado.0 (24567) Issue at setTemperatureOffset: 'Error: No internet connection detected!'. Based on body {"celsius":0.15} 2022-03-11 20:00:05.097 - error: tado.0 (24567) Issue at setTemperatureOffset: 'Error: No internet connection detected!'. Based on body {"celsius":0.1} 2022-03-11 20:00:05.140 - error: tado.0 (24567) Issue at setTemperatureOffset: 'Error: No internet connection detected!'. Based on body {"celsius":-1.97} 2022-03-11 20:00:05.232 - error: tado.0 (24567) Issue at setTemperatureOffset: 'Error: No internet connection detected!'. Based on body {"celsius":-0.14} 2022-03-11 20:00:05.285 - error: tado.0 (24567) Issue at setTemperatureOffset: 'Error: No internet connection detected!'. Based on body {"celsius":-0.78} 2022-03-11 20:00:05.294 - error: tado.0 (24567) Issue at setTemperatureOffset: 'Error: No internet connection detected!'. Based on body {"celsius":-1.89} 2022-03-11 20:00:10.310 - error: node-red.0 (24368) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:00:10.331 - error: node-red.0 (24368) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:00:10.332 - error: node-red.0 (24368) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:00:10.332 - error: node-red.0 (24368) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:00:10.841 - info: node-red.0 (24368) terminating 2022-03-11 20:00:10.844 - warn: node-red.0 (24368) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:00:11.436 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:00:16.454 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:00:23.704 - warn: node-red.0 (24341) 11 Mar 20:00:23 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:00:25.861 - error: node-red.0 (24341) 11 Mar 20:00:25 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:00:35.461 - error: node-red.0 (27016) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:00:35.464 - error: node-red.0 (27016) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:00:35.465 - error: node-red.0 (27016) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:00:35.465 - error: node-red.0 (27016) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:00:35.714 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:00:35.721 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:00:36.202 - info: node-red.0 (27016) terminating 2022-03-11 20:00:36.203 - warn: node-red.0 (27016) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:00:37.205 - info: node-red.0 (27016) terminating with timeout 2022-03-11 20:00:37.237 - warn: node-red.0 (27016) redis get zigbee.0.00158d000163f2bc.available, error - Connection is closed. 2022-03-11 20:00:37.240 - warn: node-red.0 (27016) redis get zigbee.0.00158d000163f2bc.voltage, error - Connection is closed. 2022-03-11 20:00:37.242 - warn: node-red.0 (27016) redis get zigbee.0.00158d00019f3736.available, error - Connection is closed. 2022-03-11 20:00:37.245 - warn: node-red.0 (27016) redis get zigbee.0.00158d00019f3736.voltage, error - Connection is closed. 2022-03-11 20:00:37.247 - warn: node-red.0 (27016) redis get zigbee.0.00158d0001e4e9e3.available, error - Connection is closed. 2022-03-11 20:00:37.249 - warn: node-red.0 (27016) redis get zigbee.0.00158d0001e4e9e3.voltage, error - Connection is closed. 2022-03-11 20:00:37.251 - warn: node-red.0 (27016) redis get zigbee.0.00158d000282eec7.available, error - Connection is closed. 2022-03-11 20:00:37.253 - warn: node-red.0 (27016) redis get zigbee.0.00158d000282eec7.voltage, error - Connection is closed. 2022-03-11 20:00:37.255 - warn: node-red.0 (27016) redis get zigbee.0.00158d000283e64e.available, error - Connection is closed. 2022-03-11 20:00:37.257 - warn: node-red.0 (27016) redis get zigbee.0.00158d000283e64e.voltage, error - Connection is closed. 2022-03-11 20:00:37.259 - warn: node-red.0 (27016) redis get zigbee.0.00158d000283e67b.available, error - Connection is closed. 2022-03-11 20:00:37.260 - warn: node-red.0 (27016) redis get zigbee.0.00158d000283e67b.voltage, error - Connection is closed. 2022-03-11 20:00:37.262 - warn: node-red.0 (27016) redis get zigbee.0.00158d000309a45a.available, error - Connection is closed. 2022-03-11 20:00:37.262 - warn: node-red.0 (27016) redis get zigbee.0.00158d000309a45a.voltage, error - Connection is closed. 2022-03-11 20:00:37.263 - warn: node-red.0 (27016) redis get zigbee.0.00158d0003f0f373.available, error - Connection is closed. 2022-03-11 20:00:37.263 - warn: node-red.0 (27016) redis get zigbee.0.00158d0003f0f373.voltage, error - Connection is closed. 2022-03-11 20:00:37.264 - warn: node-red.0 (27016) redis get zigbee.0.00158d000410e87b.available, error - Connection is closed. 2022-03-11 20:00:37.264 - warn: node-red.0 (27016) redis get zigbee.0.00158d000410e87b.voltage, error - Connection is closed. 2022-03-11 20:00:37.265 - warn: node-red.0 (27016) redis get zigbee.0.00158d000410e8ca.available, error - Connection is closed. 2022-03-11 20:00:37.265 - warn: node-red.0 (27016) redis get zigbee.0.00158d000410e8ca.voltage, error - Connection is closed. 2022-03-11 20:00:37.266 - warn: node-red.0 (27016) redis get zigbee.0.00158d000411103a.available, error - Connection is closed. 2022-03-11 20:00:37.266 - warn: node-red.0 (27016) redis get zigbee.0.00158d000411103a.voltage, error - Connection is closed. 2022-03-11 20:00:37.267 - warn: node-red.0 (27016) redis get zigbee.0.00158d000412fc1e.available, error - Connection is closed. 2022-03-11 20:00:37.267 - warn: node-red.0 (27016) redis get zigbee.0.00158d000412fc1e.voltage, error - Connection is closed. 2022-03-11 20:00:37.268 - warn: node-red.0 (27016) redis get zigbee.0.00158d00041d8697.available, error - Connection is closed. 2022-03-11 20:00:37.268 - warn: node-red.0 (27016) redis get zigbee.0.00158d00041d8697.voltage, error - Connection is closed. 2022-03-11 20:00:37.268 - warn: node-red.0 (27016) redis get zigbee.0.00158d00051dfd12.available, error - Connection is closed. 2022-03-11 20:00:37.269 - warn: node-red.0 (27016) redis get zigbee.0.00158d00051dfd12.voltage, error - Connection is closed. 2022-03-11 20:00:37.269 - warn: node-red.0 (27016) redis get zigbee.0.00158d00051e1633.available, error - Connection is closed. 2022-03-11 20:00:37.270 - warn: node-red.0 (27016) redis get zigbee.0.00158d00051e1633.voltage, error - Connection is closed. 2022-03-11 20:00:37.270 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005221c37.available, error - Connection is closed. 2022-03-11 20:00:37.270 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005221c37.voltage, error - Connection is closed. 2022-03-11 20:00:37.271 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005221c38.available, error - Connection is closed. 2022-03-11 20:00:37.271 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005221c38.voltage, error - Connection is closed. 2022-03-11 20:00:37.272 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005221fbe.available, error - Connection is closed. 2022-03-11 20:00:37.272 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005221fbe.voltage, error - Connection is closed. 2022-03-11 20:00:37.272 - warn: node-red.0 (27016) redis get zigbee.0.00158d00052debfb.available, error - Connection is closed. 2022-03-11 20:00:37.273 - warn: node-red.0 (27016) redis get zigbee.0.00158d00052debfb.voltage, error - Connection is closed. 2022-03-11 20:00:37.273 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005cf8b49.available, error - Connection is closed. 2022-03-11 20:00:37.273 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005cf8b49.voltage, error - Connection is closed. 2022-03-11 20:00:37.274 - warn: node-red.0 (27016) redis get zigbee.0.00178801089de95e.available, error - Connection is closed. 2022-03-11 20:00:37.274 - warn: node-red.0 (27016) redis get zigbee.0.00178801089de95e.voltage, error - Connection is closed. 2022-03-11 20:00:37.275 - warn: node-red.0 (27016) redis get zigbee.0.00178801089def32.available, error - Connection is closed. 2022-03-11 20:00:37.275 - warn: node-red.0 (27016) redis get zigbee.0.00178801089def32.voltage, error - Connection is closed. 2022-03-11 20:00:37.275 - warn: node-red.0 (27016) redis get zigbee.0.00158d00076565a1.available, error - Connection is closed. 2022-03-11 20:00:37.276 - warn: node-red.0 (27016) redis get zigbee.0.00158d00076565a1.voltage, error - Connection is closed. 2022-03-11 20:00:37.276 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f35a.available, error - Connection is closed. 2022-03-11 20:00:37.277 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f35a.voltage, error - Connection is closed. 2022-03-11 20:00:37.277 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f34a.available, error - Connection is closed. 2022-03-11 20:00:37.277 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f34a.voltage, error - Connection is closed. 2022-03-11 20:00:37.278 - warn: node-red.0 (27016) redis get zigbee.0.00158d00077dce53.available, error - Connection is closed. 2022-03-11 20:00:37.278 - warn: node-red.0 (27016) redis get zigbee.0.00158d00077dce53.voltage, error - Connection is closed. 2022-03-11 20:00:37.278 - warn: node-red.0 (27016) redis get zigbee.0.00158d00075f6607.available, error - Connection is closed. 2022-03-11 20:00:37.279 - warn: node-red.0 (27016) redis get zigbee.0.00158d00075f6607.voltage, error - Connection is closed. 2022-03-11 20:00:37.279 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f31c.available, error - Connection is closed. 2022-03-11 20:00:37.280 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f31c.voltage, error - Connection is closed. 2022-03-11 20:00:37.280 - warn: node-red.0 (27016) redis get zigbee.0.00158d00077dce21.available, error - Connection is closed. 2022-03-11 20:00:37.280 - warn: node-red.0 (27016) redis get zigbee.0.00158d00077dce21.voltage, error - Connection is closed. 2022-03-11 20:00:37.281 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f2c9.available, error - Connection is closed. 2022-03-11 20:00:37.281 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f2c9.voltage, error - Connection is closed. 2022-03-11 20:00:37.282 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f2cb.available, error - Connection is closed. 2022-03-11 20:00:37.282 - warn: node-red.0 (27016) redis get zigbee.0.00158d000774f2cb.voltage, error - Connection is closed. 2022-03-11 20:00:37.282 - warn: node-red.0 (27016) redis get zigbee.0.00158d00073c0c65.available, error - Connection is closed. 2022-03-11 20:00:37.283 - warn: node-red.0 (27016) redis get zigbee.0.00158d00073c0c65.voltage, error - Connection is closed. 2022-03-11 20:00:37.283 - warn: node-red.0 (27016) redis get zigbee.0.00158d00044eefbe.available, error - Connection is closed. 2022-03-11 20:00:37.283 - warn: node-red.0 (27016) redis get zigbee.0.00158d00044eefbe.voltage, error - Connection is closed. 2022-03-11 20:00:37.284 - warn: node-red.0 (27016) redis get zigbee.0.84fd27fffe245425.available, error - Connection is closed. 2022-03-11 20:00:37.284 - warn: node-red.0 (27016) redis get zigbee.0.84fd27fffe245425.voltage, error - Connection is closed. 2022-03-11 20:00:37.285 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005cf4ea4.available, error - Connection is closed. 2022-03-11 20:00:37.285 - warn: node-red.0 (27016) redis get zigbee.0.00158d0005cf4ea4.voltage, error - Connection is closed. 2022-03-11 20:00:37.286 - warn: node-red.0 (27016) redis get zigbee.0.804b50fffef8cf51.available, error - Connection is closed. 2022-03-11 20:00:37.286 - warn: node-red.0 (27016) redis get zigbee.0.804b50fffef8cf51.voltage, error - Connection is closed. 2022-03-11 20:00:37.286 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe77b835.available, error - Connection is closed. 2022-03-11 20:00:37.287 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe77b835.voltage, error - Connection is closed. 2022-03-11 20:00:37.287 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe77b200.available, error - Connection is closed. 2022-03-11 20:00:37.287 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe77b200.voltage, error - Connection is closed. 2022-03-11 20:00:37.288 - warn: node-red.0 (27016) redis get zigbee.0.84fd27fffe1f8f5d.available, error - Connection is closed. 2022-03-11 20:00:37.288 - warn: node-red.0 (27016) redis get zigbee.0.84fd27fffe1f8f5d.voltage, error - Connection is closed. 2022-03-11 20:00:37.289 - warn: node-red.0 (27016) redis get zigbee.0.84fd27fffe1f8f8c.available, error - Connection is closed. 2022-03-11 20:00:37.289 - warn: node-red.0 (27016) redis get zigbee.0.84fd27fffe1f8f8c.voltage, error - Connection is closed. 2022-03-11 20:00:37.289 - warn: node-red.0 (27016) redis get zigbee.0.b4e3f9fffeaae8c8.available, error - Connection is closed. 2022-03-11 20:00:37.290 - warn: node-red.0 (27016) redis get zigbee.0.b4e3f9fffeaae8c8.voltage, error - Connection is closed. 2022-03-11 20:00:37.290 - warn: node-red.0 (27016) redis get zigbee.0.842e14fffe89313a.available, error - Connection is closed. 2022-03-11 20:00:37.290 - warn: node-red.0 (27016) redis get zigbee.0.842e14fffe89313a.voltage, error - Connection is closed. 2022-03-11 20:00:37.291 - warn: node-red.0 (27016) redis get zigbee.0.842e14fffe285173.available, error - Connection is closed. 2022-03-11 20:00:37.291 - warn: node-red.0 (27016) redis get zigbee.0.842e14fffe285173.voltage, error - Connection is closed. 2022-03-11 20:00:37.292 - warn: node-red.0 (27016) redis get zigbee.0.804b50fffe606093.available, error - Connection is closed. 2022-03-11 20:00:37.292 - warn: node-red.0 (27016) redis get zigbee.0.804b50fffe606093.voltage, error - Connection is closed. 2022-03-11 20:00:37.292 - warn: node-red.0 (27016) redis get zigbee.0.540f57fffe8971d1.available, error - Connection is closed. 2022-03-11 20:00:37.293 - warn: node-red.0 (27016) redis get zigbee.0.540f57fffe8971d1.voltage, error - Connection is closed. 2022-03-11 20:00:37.293 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe80c9ba.available, error - Connection is closed. 2022-03-11 20:00:37.293 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe80c9ba.voltage, error - Connection is closed. 2022-03-11 20:00:37.294 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe77b282.available, error - Connection is closed. 2022-03-11 20:00:37.294 - warn: node-red.0 (27016) redis get zigbee.0.84ba20fffe77b282.voltage, error - Connection is closed. 2022-03-11 20:00:37.294 - warn: node-red.0 (27016) redis get zigbee.0.group_901.available, error - Connection is closed. 2022-03-11 20:00:37.295 - warn: node-red.0 (27016) redis get zigbee.0.group_901.voltage, error - Connection is closed. 2022-03-11 20:00:37.295 - warn: node-red.0 (27016) redis mget 0 607, err: Connection is closed. 2022-03-11 20:00:37.296 - warn: node-red.0 (27016) redis mget 0 13, err: Connection is closed. 2022-03-11 20:00:37.296 - warn: node-red.0 (27016) redis mget 0 13, err: Connection is closed. 2022-03-11 20:00:37.296 - warn: node-red.0 (27016) redis mget 0 13, err: Connection is closed. 2022-03-11 20:00:37.297 - warn: node-red.0 (27016) redis mget 0 6, err: Connection is closed. 2022-03-11 20:00:37.297 - warn: node-red.0 (27016) redis mget 0 6, err: Connection is closed. 2022-03-11 20:00:37.298 - warn: node-red.0 (27016) redis mget 0 21, err: Connection is closed. 2022-03-11 20:00:37.298 - warn: node-red.0 (27016) redis mget 0 21, err: Connection is closed. 2022-03-11 20:00:37.299 - warn: node-red.0 (27016) redis mget 0 8, err: Connection is closed. 2022-03-11 20:00:37.299 - warn: node-red.0 (27016) redis mget 0 8, err: Connection is closed. 2022-03-11 20:00:37.299 - warn: node-red.0 (27016) redis mget 0 8, err: Connection is closed. 2022-03-11 20:00:37.300 - warn: node-red.0 (27016) redis mget 0 8, err: Connection is closed. 2022-03-11 20:00:37.300 - warn: node-red.0 (27016) redis mget 0 8, err: Connection is closed. 2022-03-11 20:00:37.301 - warn: node-red.0 (27016) redis mget 0 8, err: Connection is closed. 2022-03-11 20:00:37.301 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.301 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.302 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.302 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.515 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.516 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.517 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.518 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.522 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.523 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.524 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.525 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.526 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.527 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.528 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.528 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.529 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.530 - warn: node-red.0 (27016) redis mget 0 9, err: Connection is closed. 2022-03-11 20:00:37.531 - warn: node-red.0 (27016) redis mget 0 11, err: Connection is closed. 2022-03-11 20:00:37.532 - warn: node-red.0 (27016) redis mget 0 11, err: Connection is closed. 2022-03-11 20:00:37.589 - warn: node-red.0 (27016) redis mget 0 47, err: Connection is closed. 2022-03-11 20:00:38.007 - warn: node-red.0 (27016) redis get zigbee.0.00158d000163f2bc.humidity, error - Connection is closed. 2022-03-11 20:00:46.278 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:00:51.279 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:00:58.901 - warn: node-red.0 (24341) 11 Mar 20:00:58 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:01:00.902 - error: node-red.0 (24341) 11 Mar 20:01:00 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:01:10.355 - error: node-red.0 (27035) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:01:10.360 - error: node-red.0 (27035) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:01:10.361 - error: node-red.0 (27035) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:01:10.361 - error: node-red.0 (27035) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:01:10.866 - info: node-red.0 (27035) terminating 2022-03-11 20:01:10.869 - warn: node-red.0 (27035) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:01:20.639 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:01:25.640 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:01:32.961 - warn: node-red.0 (24341) 11 Mar 20:01:32 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:01:34.927 - error: node-red.0 (24341) 11 Mar 20:01:34 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:01:43.281 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:01:43.282 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:01:44.329 - error: node-red.0 (27054) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:01:44.334 - error: node-red.0 (27054) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:01:44.335 - error: node-red.0 (27054) RequestError: Error: getaddrinfo EAI_AGAIN api.telegram.org at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:01:44.336 - error: node-red.0 (27054) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org 2022-03-11 20:01:44.840 - info: node-red.0 (27054) terminating 2022-03-11 20:01:44.841 - warn: node-red.0 (27054) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:01:49.705 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:01:54.707 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:02:01.876 - warn: node-red.0 (24341) 11 Mar 20:02:01 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:02:03.426 - error: node-red.0 (27097) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:02:03.429 - error: node-red.0 (27097) unhandled promise rejection: EFATAL: Error: connect ENETUNREACH 149.154.167.220:443 2022-03-11 20:02:03.430 - error: node-red.0 (27097) RequestError: Error: connect ENETUNREACH 149.154.167.220:443 at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:02:03.431 - error: node-red.0 (27097) Exception-Code: EFATAL: EFATAL: Error: connect ENETUNREACH 149.154.167.220:443 2022-03-11 20:02:03.947 - info: node-red.0 (27097) terminating 2022-03-11 20:02:03.948 - warn: node-red.0 (27097) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:02:04.000 - error: node-red.0 (24341) 11 Mar 20:02:04 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:02:04.949 - info: node-red.0 (27097) terminating with timeout 2022-03-11 20:02:08.596 - warn: node-red.0 (27097) redis get tado.0.580325.Rooms.5.setting.temperature.celsius, error - Connection is closed. 2022-03-11 20:02:08.597 - warn: node-red.0 (27097) redis get tado.0.580325.Rooms.3.setting.temperature.celsius, error - Connection is closed. 2022-03-11 20:02:09.708 - warn: node-red.0 (27097) Cannot get view: Connection is closed. 2022-03-11 20:02:09.780 - info: node-red.0 (24341) node-red exited with 1 2022-03-11 20:02:14.782 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:02:16.495 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:02:16.496 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:02:22.260 - warn: node-red.0 (24341) 11 Mar 20:02:22 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:02:24.218 - error: node-red.0 (24341) 11 Mar 20:02:24 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:02:38.731 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:02:38.732 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:02:41.836 - error: node-red.0 (27164) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:02:41.848 - error: node-red.0 (27164) unhandled promise rejection: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:02:41.849 - error: node-red.0 (27164) RequestError: Error: connect EHOSTUNREACH 149.154.167.220:443 at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:02:41.850 - error: node-red.0 (27164) Exception-Code: EFATAL: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:02:42.358 - info: node-red.0 (27164) terminating 2022-03-11 20:02:42.359 - warn: node-red.0 (27164) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:02:47.178 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:02:52.179 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:02:59.415 - warn: node-red.0 (24341) 11 Mar 20:02:59 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:03:01.994 - error: node-red.0 (24341) 11 Mar 20:03:01 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:03:12.147 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:03:12.148 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:03:18.955 - error: node-red.0 (27183) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:03:18.967 - error: node-red.0 (27183) unhandled promise rejection: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:03:18.968 - error: node-red.0 (27183) RequestError: Error: connect EHOSTUNREACH 149.154.167.220:443 at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:03:18.969 - error: node-red.0 (27183) Exception-Code: EFATAL: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:03:19.477 - info: node-red.0 (27183) terminating 2022-03-11 20:03:19.478 - warn: node-red.0 (27183) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:03:24.303 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:03:29.304 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:03:36.814 - warn: node-red.0 (24341) 11 Mar 20:03:36 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:03:38.904 - error: node-red.0 (24341) 11 Mar 20:03:38 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:03:56.300 - error: node-red.0 (27203) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:03:56.306 - error: node-red.0 (27203) unhandled promise rejection: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:03:56.307 - error: node-red.0 (27203) RequestError: Error: connect EHOSTUNREACH 149.154.167.220:443 at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:03:56.308 - error: node-red.0 (27203) Exception-Code: EFATAL: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:03:56.812 - info: node-red.0 (27203) terminating 2022-03-11 20:03:56.814 - warn: node-red.0 (27203) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:04:01.650 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:04:06.651 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:04:14.146 - warn: node-red.0 (24341) 11 Mar 20:04:14 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:04:16.092 - error: node-red.0 (24341) 11 Mar 20:04:16 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:04:33.679 - error: node-red.0 (27223) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2022-03-11 20:04:33.690 - error: node-red.0 (27223) unhandled promise rejection: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:04:33.691 - error: node-red.0 (27223) RequestError: Error: connect EHOSTUNREACH 149.154.167.220:443 at new RequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/errors.js:14:15) at Request.plumbing.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:87:29) at Request.RP$callback [as _callback] (/opt/iobroker/iobroker-data/node-red/node_modules/request-promise-core/lib/plumbing.js:46:31) at self.callback (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:185:22) at Request.emit (events.js:314:20) at Request.onRequestError (/opt/iobroker/iobroker-data/node-red/node_modules/request/request.js:877:8) at ClientRequest.emit (events.js:314:20) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) 2022-03-11 20:04:33.692 - error: node-red.0 (27223) Exception-Code: EFATAL: EFATAL: Error: connect EHOSTUNREACH 149.154.167.220:443 2022-03-11 20:04:34.198 - info: node-red.0 (27223) terminating 2022-03-11 20:04:34.201 - warn: node-red.0 (27223) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-03-11 20:04:42.831 - info: sonoff.0 (24361) Client [Wüstenbaum-Sensor] reconnected. Old secret 1647024732917_1716. New secret 1647025482831_3153 2022-03-11 20:04:44.061 - info: node-red.0 (24341) node-red exited with 6 2022-03-11 20:04:49.062 - info: node-red.0 (24341) Starting node-red: --max-old-space-size=512 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2022-03-11 20:04:52.796 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:04:52.798 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:04:56.655 - warn: node-red.0 (24341) 11 Mar 20:04:56 - [warn] Projekte deaktiviert: editorTheme.projects.enabled=false 2022-03-11 20:04:58.785 - error: node-red.0 (24341) 11 Mar 20:04:58 - [error] [hue-group:Bad Kevin] The group in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid.. 2022-03-11 20:05:04.080 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate.checkforupdate" has to be type "string" but received type "boolean" 2022-03-11 20:05:04.081 - info: hue-extended.0 (24465) State value to set for "hue-extended.0.config.swupdate2.checkforupdate" has to be type "string" but received type "boolean"`
Schmetterfliege
commented
2 years ago Remark: you can copy-paste the log and filter for "node-red.0" to only see log messages from the node red instance.
windkh
commented
2 years ago I just had a quick look... the only thing I can see in the callstack is that request-promise was involved... not seeing who called it. If I interrupt my internet connection this error does not occur... are you sure that this comes from the telegram nodes?
Schmetterfliege
commented
2 years ago Well, I don't know what is causing it. I'm just making the conclusion :D Since nore-red is crashing after telegram throws these errors, I am assuming it is caused by telegram and/or node-red. Nothing else was causing any issues or showing any signs of issues in my whole setup, everything behaved perfectly fine.
However, my whole smart home setup is currently stored in some boxes since I was moving and will be moving again soon (hopefully). Once I found a new home I will set up everything again and play a bit with it. If you have any requests for tests I should do, please feel free to let me know! :)
(can't give a date by when it will happen, but I'm trying to get out of this place ASAP^^)
windkh
commented
2 years ago Any news?
Schmetterfliege
commented
2 years ago Will be moving on August 1st. I'll then try to set up the core smart home stuff to be able to test it
Schmetterfliege
commented
2 years ago Hey,
my DSL got activated yesterday, I'm currently busy with connecting my network stuff again, updating IoBroker and all the adapters etc. Should be able to test this again within a few days!
windkh
commented
2 years ago Any news?
Schmetterfliege
commented
2 years ago Sorry, took a bit longer since via Cable I couldn't get network here and I had to wait for my DSL to be activated. Will be doing one last test tomorrow: disconnect my router before leaving for work. If there's no error when I come back home, I'll close it :)
Schmetterfliege
commented
2 years ago Okay, got it reproduced. Network cut tonight at 06:08, node red got into a crash loop at 12 (woke up at 12.20 hehe). Logs from my IoBroker are in debug mode, so you should see everything that is happening on my iobroker (and as you can see, nothing is doing anything).
Here's a onedrive link to the logs: https://1drv.ms/t/s!AjHX7wy1Hl8LgRO-S8PlRIuhH-7R?e=aRsKe9
Schmetterfliege
commented
2 years ago In NR I have a node that is checking the availability of a datapoint and sending me a notification via Telegram, every day at 12.00. This is the exact moment NR crashed. There's nothing else that is happening automatically between 06.08 and 12. So my assumption is that NR crashes if it is trying to send something via Telegram while there is no network.
windkh
commented
2 years ago Hm... passiert das gleiche wenn man das Netzwerkabel zieht?
Schmetterfliege
commented
2 years ago Ich versuche das mal eben. Stecker ziehen, 1 Minute warten und dann versuchen über NR eine Nachricht zu schicken
Schmetterfliege
commented
2 years ago Ja. Hab den Stecker gezogen, ne Minute oder zwei gewartet und dann eine Aktion getriggert die mir über NR via Telegram eine Benachrichtigung schicken würde. Da kam dann ca 5 Sekunden später direkt der Error und der Crash
windkh
commented
2 years ago Scheint sich anders zu verhalten wie bei Windows. Du nutzt die nodes ganz normal ohne webhook ohne socks usw?
Schmetterfliege
commented
2 years ago 
Hab hier mal 2 Beispiele, im erste drücke ich einen Tradfri Knopf (Daten kommen über IoBroker, da habe ich nen Zigbee Adapter, es werden einfach nur die Datenpunkte im IoBroker gelesen). Sobald der Knopf gedrückt wird, bekomme ich eine Nachricht in Telegram dass die Herdplatte bzw. die Steckdose jetzt eingeschalten ist. Im Zweiten ist meine Daily Notification für den Feuchtigkeitssensor in einer Pflanze. Da wird jeden Tag um 12 der Wert gelesen und mir per Telegram der Status mitgeteilt.
Für mich ist der Aufbau "normal" :D Datenpunkt lesen, in einer Funktion den Content der Message definieren und dann per Telegram Node verschicken.
windkh
commented
2 years ago Ja ok, wollte nur ausschliessen dass noch was spezielles im config node verwendet wird was das netzwerk beeinflussen könnte
Schmetterfliege
commented
2 years ago Wie gesagt, falls ich irgendwas spezielles für dich testen kann, gib bescheid. Jetzt wo ich weiß wie ich es aktiv reproduzieren kann innerhalb einer Minute, sollte das ja kein Problem mehr sein :D
windkh
commented
1 year ago Ich habe mir das Log nochmal angeschaut. Alles was ich sehen kann kommt aus IoBroker. Kann es sein dass IO Broker auch Telegram nutzt?
Läuft node-red aus IoBroker heraus?
Schmetterfliege
commented
1 year ago Also im IoBroker habe ich Telegram zwar "installiert", es ist aber deaktiviert. Also nicht aktiv und wird auch nicht benutzt. Die Telegram Instanz die benutzt wird, läuft in NR direkt.
NR läuft allerdings aus IoBroker heraus, das ist richtig.
windkh
commented
1 year ago Kannst TG in IoBroker mal entfernen auch wenn es deaktiviert ist?Nur um sicher zu gehenGesendet mit der WEB.DE iPad AppAm 15.10.22 um 20:01 schrieb Schmetterfliege
Von: "Schmetterfliege" ***@***.***>Datum: 15. Oktober 2022An: "windkh/node-red-contrib-telegrambot" ***@***.***>Cc: "Karl-Heinz Wind" ***@***.***>,"Mention" ***@***.***>Betreff: Re: [windkh/node-red-contrib-telegrambot] node red crashes if network is not available (Issue #234)Also im IoBroker habe ich Telegram zwar "installiert", es ist aber deaktiviert. Also nicht aktiv und wird auch nicht benutzt.
Die Telegram Instanz die benutzt wird, läuft in NR direkt.
NR läuft allerdings aus IoBroker heraus, das ist richtig.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Schmetterfliege
commented
1 year ago what the.... Ich kann es tatsächlich nur reproduzieren wenn in IoB telegram installiert ist auch wenn es deaktiviert ist. Wenn im IoB kein Telegram existiert, crasht NR nicht. Ich hab Telegram dann nochmal installiert, NICHT konfiguriert und kanns wieder reproduzieren. Telegram gelöscht -> kanns nicht mehr reproduzieren.
Also ich behaupte mal, das ist kein Problem mit deiner Integration^^ Ich checks nicht.. aber egal, Telegram in IoB hab ich ja eh nicht benutzt also kann ichs auch deinstalliert lassen. Sorry für den unnötigen Aufwand den ich dir bereitet habe! :(
windkh
commented
1 year ago Ich kann mir vorstellen dass es in iobroker halt nicht 100% deaktiviert ist. Hab mir nur gedacht dass der callstack so überhaupt keinen Sinn macht... falls es nun passt kannst den Issue zumachen. Vg
Schmetterfliege
commented
1 year ago Super strange auf jeden Fall. Vielen Dank für deine Mühe!
windkh
commented
1 year ago Gern
This week my internet provider had an issue, killing my cable connection for ~ 10 hours. After it was back, I noticed that my NR crashed many times due to telegram api not having a connection.
I do have a catch node in the same flow, but it didn't prevent NR from crashing constantly.
Line 107: 2022-02-07 15:00:10.316 - error: node-red.0 (6588) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 121: 2022-02-07 15:00:10.317 - error: node-red.0 (6588) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 129: 2022-02-07 15:00:43.316 - error: node-red.0 (9290) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 143: 2022-02-07 15:00:43.317 - error: node-red.0 (9290) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 155: 2022-02-07 15:01:18.296 - error: node-red.0 (9309) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 169: 2022-02-07 15:01:18.297 - error: node-red.0 (9309) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 179: 2022-02-07 15:01:53.739 - error: node-red.0 (9331) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 193: 2022-02-07 15:01:53.740 - error: node-red.0 (9331) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 201: 2022-02-07 15:02:28.981 - error: node-red.0 (9351) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 215: 2022-02-07 15:02:28.982 - error: node-red.0 (9351) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 223: 2022-02-07 15:03:04.238 - error: node-red.0 (9371) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 237: 2022-02-07 15:03:04.239 - error: node-red.0 (9371) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 245: 2022-02-07 15:03:39.607 - error: node-red.0 (9390) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 259: 2022-02-07 15:03:39.608 - error: node-red.0 (9390) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 269: 2022-02-07 15:04:14.589 - error: node-red.0 (9409) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 283: 2022-02-07 15:04:14.591 - error: node-red.0 (9409) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 295: 2022-02-07 15:04:49.328 - error: node-red.0 (9429) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 309: 2022-02-07 15:04:49.329 - error: node-red.0 (9429) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 321: 2022-02-07 15:05:24.447 - error: node-red.0 (9448) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 335: 2022-02-07 15:05:24.449 - error: node-red.0 (9448) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 345: 2022-02-07 15:05:59.452 - error: node-red.0 (9467) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 359: 2022-02-07 15:05:59.455 - error: node-red.0 (9467) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 367: 2022-02-07 15:06:34.585 - error: node-red.0 (9486) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 381: 2022-02-07 15:06:34.586 - error: node-red.0 (9486) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 389: 2022-02-07 15:07:09.774 - error: node-red.0 (9540) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 403: 2022-02-07 15:07:09.775 - error: node-red.0 (9540) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 411: 2022-02-07 15:07:45.145 - error: node-red.0 (9560) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 425: 2022-02-07 15:07:45.146 - error: node-red.0 (9560) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 435: 2022-02-07 15:08:20.153 - error: node-red.0 (9579) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 449: 2022-02-07 15:08:20.154 - error: node-red.0 (9579) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 461: 2022-02-07 15:08:54.865 - error: node-red.0 (9598) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 475: 2022-02-07 15:08:54.867 - error: node-red.0 (9598) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 487: 2022-02-07 15:09:29.915 - error: node-red.0 (9617) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 501: 2022-02-07 15:09:29.916 - error: node-red.0 (9617) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 515: 2022-02-07 15:10:05.223 - error: node-red.0 (9638) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 529: 2022-02-07 15:10:05.224 - error: node-red.0 (9638) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 539: 2022-02-07 15:10:40.244 - error: node-red.0 (9657) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 553: 2022-02-07 15:10:40.246 - error: node-red.0 (9657) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 561: 2022-02-07 15:11:15.374 - error: node-red.0 (9676) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 575: 2022-02-07 15:11:15.375 - error: node-red.0 (9676) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 583: 2022-02-07 15:11:50.844 - error: node-red.0 (9695) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 597: 2022-02-07 15:11:50.845 - error: node-red.0 (9695) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 607: 2022-02-07 15:12:25.743 - error: node-red.0 (9716) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 621: 2022-02-07 15:12:25.744 - error: node-red.0 (9716) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 634: 2022-02-07 15:13:00.790 - error: node-red.0 (9736) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 648: 2022-02-07 15:13:00.791 - error: node-red.0 (9736) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 661: 2022-02-07 15:13:36.110 - error: node-red.0 (9755) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 675: 2022-02-07 15:13:36.111 - error: node-red.0 (9755) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 685: 2022-02-07 15:14:11.443 - error: node-red.0 (9774) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 699: 2022-02-07 15:14:11.445 - error: node-red.0 (9774) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 707: 2022-02-07 15:14:46.720 - error: node-red.0 (9793) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 721: 2022-02-07 15:14:46.721 - error: node-red.0 (9793) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 729: 2022-02-07 15:15:21.910 - error: node-red.0 (9813) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 743: 2022-02-07 15:15:21.911 - error: node-red.0 (9813) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 751: 2022-02-07 15:15:57.288 - error: node-red.0 (9856) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 765: 2022-02-07 15:15:57.289 - error: node-red.0 (9856) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 777: 2022-02-07 15:16:31.959 - error: node-red.0 (9875) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 791: 2022-02-07 15:16:31.960 - error: node-red.0 (9875) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 803: 2022-02-07 15:17:06.726 - error: node-red.0 (9896) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 817: 2022-02-07 15:17:06.727 - error: node-red.0 (9896) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 829: 2022-02-07 15:17:41.858 - error: node-red.0 (9925) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 843: 2022-02-07 15:17:41.860 - error: node-red.0 (9925) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 853: 2022-02-07 15:18:17.021 - error: node-red.0 (9944) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 867: 2022-02-07 15:18:17.022 - error: node-red.0 (9944) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 875: 2022-02-07 15:18:52.219 - error: node-red.0 (9965) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 889: 2022-02-07 15:18:52.221 - error: node-red.0 (9965) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 897: 2022-02-07 15:19:27.344 - error: node-red.0 (9984) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 911: 2022-02-07 15:19:27.345 - error: node-red.0 (9984) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 919: 2022-02-07 15:20:02.636 - error: node-red.0 (10004) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 933: 2022-02-07 15:20:02.637 - error: node-red.0 (10004) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 943: 2022-02-07 15:20:37.636 - error: node-red.0 (10024) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 957: 2022-02-07 15:20:37.637 - error: node-red.0 (10024) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 969: 2022-02-07 15:21:12.322 - error: node-red.0 (10044) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 983: 2022-02-07 15:21:12.323 - error: node-red.0 (10044) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 995: 2022-02-07 15:21:47.383 - error: node-red.0 (10063) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1009: 2022-02-07 15:21:47.384 - error: node-red.0 (10063) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1023: 2022-02-07 15:22:22.937 - error: node-red.0 (10082) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1037: 2022-02-07 15:22:22.938 - error: node-red.0 (10082) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1045: 2022-02-07 15:22:58.052 - error: node-red.0 (10103) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1059: 2022-02-07 15:22:58.054 - error: node-red.0 (10103) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1067: 2022-02-07 15:23:33.317 - error: node-red.0 (10122) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1081: 2022-02-07 15:23:33.319 - error: node-red.0 (10122) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1089: 2022-02-07 15:24:08.613 - error: node-red.0 (10142) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1103: 2022-02-07 15:24:08.615 - error: node-red.0 (10142) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1113: 2022-02-07 15:24:43.669 - error: node-red.0 (10161) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1127: 2022-02-07 15:24:43.670 - error: node-red.0 (10161) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1139: 2022-02-07 15:25:18.307 - error: node-red.0 (10204) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1153: 2022-02-07 15:25:18.308 - error: node-red.0 (10204) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1165: 2022-02-07 15:25:53.118 - error: node-red.0 (10225) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1179: 2022-02-07 15:25:53.119 - error: node-red.0 (10225) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1193: 2022-02-07 15:26:28.525 - error: node-red.0 (10246) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1207: 2022-02-07 15:26:28.528 - error: node-red.0 (10246) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1215: 2022-02-07 15:27:03.438 - error: node-red.0 (10266) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1229: 2022-02-07 15:27:03.439 - error: node-red.0 (10266) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1239: 2022-02-07 15:27:38.705 - error: node-red.0 (10286) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1253: 2022-02-07 15:27:38.706 - error: node-red.0 (10286) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1261: 2022-02-07 15:28:14.100 - error: node-red.0 (10307) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1275: 2022-02-07 15:28:14.101 - error: node-red.0 (10307) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1285: 2022-02-07 15:28:49.215 - error: node-red.0 (10326) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1299: 2022-02-07 15:28:49.216 - error: node-red.0 (10326) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1311: 2022-02-07 15:29:24.047 - error: node-red.0 (10345) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1325: 2022-02-07 15:29:24.048 - error: node-red.0 (10345) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1337: 2022-02-07 15:29:58.887 - error: node-red.0 (10364) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1351: 2022-02-07 15:29:58.888 - error: node-red.0 (10364) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1365: 2022-02-07 15:30:34.109 - error: node-red.0 (10383) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1379: 2022-02-07 15:30:34.111 - error: node-red.0 (10383) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1387: 2022-02-07 15:31:09.218 - error: node-red.0 (10426) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1401: 2022-02-07 15:31:09.219 - error: node-red.0 (10426) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1409: 2022-02-07 15:31:44.277 - error: node-red.0 (10446) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1423: 2022-02-07 15:31:44.278 - error: node-red.0 (10446) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1431: 2022-02-07 15:32:19.548 - error: node-red.0 (10466) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1445: 2022-02-07 15:32:19.549 - error: node-red.0 (10466) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1455: 2022-02-07 15:32:54.764 - error: node-red.0 (10487) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1469: 2022-02-07 15:32:54.765 - error: node-red.0 (10487) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1481: 2022-02-07 15:33:29.653 - error: node-red.0 (10507) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1495: 2022-02-07 15:33:29.655 - error: node-red.0 (10507) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1507: 2022-02-07 15:34:04.482 - error: node-red.0 (10526) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1521: 2022-02-07 15:34:04.483 - error: node-red.0 (10526) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1535: 2022-02-07 15:34:39.684 - error: node-red.0 (10545) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1549: 2022-02-07 15:34:39.686 - error: node-red.0 (10545) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1557: 2022-02-07 15:35:14.683 - error: node-red.0 (10565) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1571: 2022-02-07 15:35:14.684 - error: node-red.0 (10565) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1579: 2022-02-07 15:35:49.981 - error: node-red.0 (10584) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1593: 2022-02-07 15:35:49.983 - error: node-red.0 (10584) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1601: 2022-02-07 15:36:25.253 - error: node-red.0 (10603) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1615: 2022-02-07 15:36:25.254 - error: node-red.0 (10603) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1623: 2022-02-07 15:37:00.506 - error: node-red.0 (10631) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1637: 2022-02-07 15:37:00.508 - error: node-red.0 (10631) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1647: 2022-02-07 15:37:35.211 - error: node-red.0 (10650) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1661: 2022-02-07 15:37:35.213 - error: node-red.0 (10650) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1673: 2022-02-07 15:38:09.870 - error: node-red.0 (10669) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1687: 2022-02-07 15:38:09.871 - error: node-red.0 (10669) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1701: 2022-02-07 15:38:45.191 - error: node-red.0 (10715) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1715: 2022-02-07 15:38:45.194 - error: node-red.0 (10715) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1723: 2022-02-07 15:39:20.315 - error: node-red.0 (10734) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1737: 2022-02-07 15:39:20.316 - error: node-red.0 (10734) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1745: 2022-02-07 15:39:55.263 - error: node-red.0 (10753) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1759: 2022-02-07 15:39:55.264 - error: node-red.0 (10753) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1767: 2022-02-07 15:40:30.552 - error: node-red.0 (10772) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1781: 2022-02-07 15:40:30.553 - error: node-red.0 (10772) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1791: 2022-02-07 15:41:05.731 - error: node-red.0 (10791) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1805: 2022-02-07 15:41:05.732 - error: node-red.0 (10791) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1817: 2022-02-07 15:41:40.518 - error: node-red.0 (10810) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1831: 2022-02-07 15:41:40.519 - error: node-red.0 (10810) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1843: 2022-02-07 15:42:15.199 - error: node-red.0 (10830) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1857: 2022-02-07 15:42:15.200 - error: node-red.0 (10830) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1872: 2022-02-07 15:42:50.431 - error: node-red.0 (10849) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1886: 2022-02-07 15:42:50.435 - error: node-red.0 (10849) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1894: 2022-02-07 15:43:25.547 - error: node-red.0 (10869) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1908: 2022-02-07 15:43:25.550 - error: node-red.0 (10869) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1916: 2022-02-07 15:44:00.568 - error: node-red.0 (10890) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1930: 2022-02-07 15:44:00.569 - error: node-red.0 (10890) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1938: 2022-02-07 15:44:35.838 - error: node-red.0 (10909) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1952: 2022-02-07 15:44:35.839 - error: node-red.0 (10909) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1960: 2022-02-07 15:45:11.138 - error: node-red.0 (10928) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1974: 2022-02-07 15:45:11.139 - error: node-red.0 (10928) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1984: 2022-02-07 15:45:45.962 - error: node-red.0 (10947) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 1998: 2022-02-07 15:45:45.963 - error: node-red.0 (10947) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2010: 2022-02-07 15:46:20.679 - error: node-red.0 (10966) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2024: 2022-02-07 15:46:20.680 - error: node-red.0 (10966) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2036: 2022-02-07 15:46:55.649 - error: node-red.0 (10988) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2050: 2022-02-07 15:46:55.650 - error: node-red.0 (10988) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2060: 2022-02-07 15:47:31.189 - error: node-red.0 (11032) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2074: 2022-02-07 15:47:31.191 - error: node-red.0 (11032) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2082: 2022-02-07 15:48:06.260 - error: node-red.0 (11051) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2096: 2022-02-07 15:48:06.261 - error: node-red.0 (11051) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2104: 2022-02-07 15:48:41.650 - error: node-red.0 (11072) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2118: 2022-02-07 15:48:41.651 - error: node-red.0 (11072) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2128: 2022-02-07 15:49:17.110 - error: node-red.0 (11092) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2142: 2022-02-07 15:49:17.111 - error: node-red.0 (11092) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2154: 2022-02-07 15:49:51.992 - error: node-red.0 (11111) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2168: 2022-02-07 15:49:51.993 - error: node-red.0 (11111) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2180: 2022-02-07 15:50:27.296 - error: node-red.0 (11130) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2194: 2022-02-07 15:50:27.297 - error: node-red.0 (11130) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2204: 2022-02-07 15:51:02.359 - error: node-red.0 (11149) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2218: 2022-02-07 15:51:02.361 - error: node-red.0 (11149) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2226: 2022-02-07 15:51:37.363 - error: node-red.0 (11169) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2240: 2022-02-07 15:51:37.364 - error: node-red.0 (11169) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2248: 2022-02-07 15:52:12.486 - error: node-red.0 (11188) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2262: 2022-02-07 15:52:12.487 - error: node-red.0 (11188) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2270: 2022-02-07 15:52:47.837 - error: node-red.0 (11209) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2284: 2022-02-07 15:52:47.838 - error: node-red.0 (11209) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2294: 2022-02-07 15:53:22.961 - error: node-red.0 (11228) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2308: 2022-02-07 15:53:22.962 - error: node-red.0 (11228) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2320: 2022-02-07 15:53:57.856 - error: node-red.0 (11249) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2334: 2022-02-07 15:53:57.859 - error: node-red.0 (11249) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2346: 2022-02-07 15:54:32.776 - error: node-red.0 (11270) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2360: 2022-02-07 15:54:32.777 - error: node-red.0 (11270) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2370: 2022-02-07 15:55:08.026 - error: node-red.0 (11289) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2384: 2022-02-07 15:55:08.028 - error: node-red.0 (11289) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2392: 2022-02-07 15:55:42.923 - error: node-red.0 (11332) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2406: 2022-02-07 15:55:42.924 - error: node-red.0 (11332) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2414: 2022-02-07 15:56:18.148 - error: node-red.0 (11351) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2428: 2022-02-07 15:56:18.149 - error: node-red.0 (11351) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2436: 2022-02-07 15:56:53.389 - error: node-red.0 (11371) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2450: 2022-02-07 15:56:53.390 - error: node-red.0 (11371) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2460: 2022-02-07 15:57:28.567 - error: node-red.0 (11390) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2474: 2022-02-07 15:57:28.568 - error: node-red.0 (11390) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2486: 2022-02-07 15:58:03.468 - error: node-red.0 (11409) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2500: 2022-02-07 15:58:03.470 - error: node-red.0 (11409) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2512: 2022-02-07 15:58:38.686 - error: node-red.0 (11430) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2526: 2022-02-07 15:58:38.688 - error: node-red.0 (11430) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2540: 2022-02-07 15:59:13.829 - error: node-red.0 (11450) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2554: 2022-02-07 15:59:13.830 - error: node-red.0 (11450) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2562: 2022-02-07 15:59:48.987 - error: node-red.0 (11470) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2576: 2022-02-07 15:59:48.988 - error: node-red.0 (11470) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2584: 2022-02-07 16:00:24.339 - error: node-red.0 (11489) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2598: 2022-02-07 16:00:24.341 - error: node-red.0 (11489) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2606: 2022-02-07 16:00:59.762 - error: node-red.0 (11508) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2620: 2022-02-07 16:00:59.763 - error: node-red.0 (11508) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2630: 2022-02-07 16:01:34.865 - error: node-red.0 (11528) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2644: 2022-02-07 16:01:34.866 - error: node-red.0 (11528) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2656: 2022-02-07 16:02:09.746 - error: node-red.0 (11549) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2670: 2022-02-07 16:02:09.747 - error: node-red.0 (11549) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2682: 2022-02-07 16:02:44.812 - error: node-red.0 (11568) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2696: 2022-02-07 16:02:44.813 - error: node-red.0 (11568) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2706: 2022-02-07 16:03:19.855 - error: node-red.0 (11588) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2720: 2022-02-07 16:03:19.857 - error: node-red.0 (11588) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2728: 2022-02-07 16:03:54.962 - error: node-red.0 (11609) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2742: 2022-02-07 16:03:54.964 - error: node-red.0 (11609) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2750: 2022-02-07 16:04:30.251 - error: node-red.0 (11641) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2764: 2022-02-07 16:04:30.252 - error: node-red.0 (11641) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2772: 2022-02-07 16:05:05.314 - error: node-red.0 (11661) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2786: 2022-02-07 16:05:05.315 - error: node-red.0 (11661) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2796: 2022-02-07 16:05:40.458 - error: node-red.0 (11680) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2810: 2022-02-07 16:05:40.459 - error: node-red.0 (11680) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2822: 2022-02-07 16:06:15.535 - error: node-red.0 (11699) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2836: 2022-02-07 16:06:15.536 - error: node-red.0 (11699) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2848: 2022-02-07 16:06:50.862 - error: node-red.0 (11719) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2862: 2022-02-07 16:06:50.864 - error: node-red.0 (11719) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2872: 2022-02-07 16:07:25.984 - error: node-red.0 (11745) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2886: 2022-02-07 16:07:25.987 - error: node-red.0 (11745) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2894: 2022-02-07 16:08:01.180 - error: node-red.0 (11765) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2908: 2022-02-07 16:08:01.181 - error: node-red.0 (11765) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2916: 2022-02-07 16:08:36.482 - error: node-red.0 (11785) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2930: 2022-02-07 16:08:36.483 - error: node-red.0 (11785) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2938: 2022-02-07 16:09:11.721 - error: node-red.0 (11806) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2952: 2022-02-07 16:09:11.723 - error: node-red.0 (11806) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2962: 2022-02-07 16:09:46.650 - error: node-red.0 (11825) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2976: 2022-02-07 16:09:46.652 - error: node-red.0 (11825) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 2988: 2022-02-07 16:10:21.740 - error: node-red.0 (11846) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3002: 2022-02-07 16:10:21.742 - error: node-red.0 (11846) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3016: 2022-02-07 16:10:57.262 - error: node-red.0 (11865) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3030: 2022-02-07 16:10:57.264 - error: node-red.0 (11865) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3038: 2022-02-07 16:11:32.158 - error: node-red.0 (11884) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3052: 2022-02-07 16:11:32.159 - error: node-red.0 (11884) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3060: 2022-02-07 16:12:07.246 - error: node-red.0 (11904) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3074: 2022-02-07 16:12:07.248 - error: node-red.0 (11904) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3082: 2022-02-07 16:12:42.575 - error: node-red.0 (11924) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3096: 2022-02-07 16:12:42.576 - error: node-red.0 (11924) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3107: 2022-02-07 16:13:17.689 - error: node-red.0 (11967) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3121: 2022-02-07 16:13:17.690 - error: node-red.0 (11967) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3133: 2022-02-07 16:13:52.735 - error: node-red.0 (11986) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3147: 2022-02-07 16:13:52.736 - error: node-red.0 (11986) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3159: 2022-02-07 16:14:27.622 - error: node-red.0 (12007) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3173: 2022-02-07 16:14:27.623 - error: node-red.0 (12007) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3187: 2022-02-07 16:15:03.026 - error: node-red.0 (12028) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3201: 2022-02-07 16:15:03.027 - error: node-red.0 (12028) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3209: 2022-02-07 16:15:38.104 - error: node-red.0 (12047) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3223: 2022-02-07 16:15:38.105 - error: node-red.0 (12047) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3231: 2022-02-07 16:16:13.282 - error: node-red.0 (12066) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3245: 2022-02-07 16:16:13.283 - error: node-red.0 (12066) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3253: 2022-02-07 16:16:48.383 - error: node-red.0 (12087) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3267: 2022-02-07 16:16:48.384 - error: node-red.0 (12087) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3277: 2022-02-07 16:17:23.578 - error: node-red.0 (12115) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3291: 2022-02-07 16:17:23.579 - error: node-red.0 (12115) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3303: 2022-02-07 16:17:58.333 - error: node-red.0 (12134) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3317: 2022-02-07 16:17:58.334 - error: node-red.0 (12134) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3329: 2022-02-07 16:18:33.229 - error: node-red.0 (12154) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3343: 2022-02-07 16:18:33.230 - error: node-red.0 (12154) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3357: 2022-02-07 16:19:08.352 - error: node-red.0 (12173) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3371: 2022-02-07 16:19:08.353 - error: node-red.0 (12173) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3379: 2022-02-07 16:19:43.471 - error: node-red.0 (12194) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3393: 2022-02-07 16:19:43.472 - error: node-red.0 (12194) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3401: 2022-02-07 16:20:18.757 - error: node-red.0 (12215) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3415: 2022-02-07 16:20:18.758 - error: node-red.0 (12215) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3423: 2022-02-07 16:20:54.236 - error: node-red.0 (12234) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3437: 2022-02-07 16:20:54.237 - error: node-red.0 (12234) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3447: 2022-02-07 16:21:29.091 - error: node-red.0 (12253) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3461: 2022-02-07 16:21:29.092 - error: node-red.0 (12253) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3473: 2022-02-07 16:22:03.961 - error: node-red.0 (12272) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3487: 2022-02-07 16:22:03.962 - error: node-red.0 (12272) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3499: 2022-02-07 16:22:39.397 - error: node-red.0 (12316) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3513: 2022-02-07 16:22:39.398 - error: node-red.0 (12316) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3541: 2022-02-07 16:23:14.708 - error: node-red.0 (12336) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3555: 2022-02-07 16:23:14.710 - error: node-red.0 (12336) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3563: 2022-02-07 16:23:49.851 - error: node-red.0 (12355) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3577: 2022-02-07 16:23:49.853 - error: node-red.0 (12355) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3585: 2022-02-07 16:24:25.408 - error: node-red.0 (12374) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3599: 2022-02-07 16:24:25.409 - error: node-red.0 (12374) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3607: 2022-02-07 16:25:00.432 - error: node-red.0 (12394) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3621: 2022-02-07 16:25:00.433 - error: node-red.0 (12394) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3631: 2022-02-07 16:25:35.344 - error: node-red.0 (12416) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3645: 2022-02-07 16:25:35.347 - error: node-red.0 (12416) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3657: 2022-02-07 16:26:10.216 - error: node-red.0 (12435) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3671: 2022-02-07 16:26:10.217 - error: node-red.0 (12435) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3685: 2022-02-07 16:26:45.606 - error: node-red.0 (12456) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3699: 2022-02-07 16:26:45.607 - error: node-red.0 (12456) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3707: 2022-02-07 16:27:20.876 - error: node-red.0 (12475) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3721: 2022-02-07 16:27:20.877 - error: node-red.0 (12475) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3729: 2022-02-07 16:27:55.999 - error: node-red.0 (12494) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3743: 2022-02-07 16:27:56.001 - error: node-red.0 (12494) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3751: 2022-02-07 16:28:31.016 - error: node-red.0 (12514) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3765: 2022-02-07 16:28:31.017 - error: node-red.0 (12514) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3775: 2022-02-07 16:29:06.149 - error: node-red.0 (12533) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3789: 2022-02-07 16:29:06.151 - error: node-red.0 (12533) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3801: 2022-02-07 16:29:40.939 - error: node-red.0 (12552) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3815: 2022-02-07 16:29:40.940 - error: node-red.0 (12552) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3827: 2022-02-07 16:30:15.764 - error: node-red.0 (12572) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3841: 2022-02-07 16:30:15.765 - error: node-red.0 (12572) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3855: 2022-02-07 16:30:51.210 - error: node-red.0 (12593) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3869: 2022-02-07 16:30:51.211 - error: node-red.0 (12593) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3877: 2022-02-07 16:31:26.263 - error: node-red.0 (12638) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3891: 2022-02-07 16:31:26.265 - error: node-red.0 (12638) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3899: 2022-02-07 16:32:01.527 - error: node-red.0 (12658) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3913: 2022-02-07 16:32:01.528 - error: node-red.0 (12658) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3921: 2022-02-07 16:32:37.032 - error: node-red.0 (12677) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3935: 2022-02-07 16:32:37.033 - error: node-red.0 (12677) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3945: 2022-02-07 16:33:11.933 - error: node-red.0 (12697) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3959: 2022-02-07 16:33:11.934 - error: node-red.0 (12697) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3973: 2022-02-07 16:33:46.687 - error: node-red.0 (12717) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3987: 2022-02-07 16:33:46.688 - error: node-red.0 (12717) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 3999: 2022-02-07 16:34:21.587 - error: node-red.0 (12736) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4013: 2022-02-07 16:34:21.588 - error: node-red.0 (12736) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4027: 2022-02-07 16:34:56.805 - error: node-red.0 (12755) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4041: 2022-02-07 16:34:56.807 - error: node-red.0 (12755) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4049: 2022-02-07 16:35:32.081 - error: node-red.0 (12774) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4063: 2022-02-07 16:35:32.083 - error: node-red.0 (12774) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4071: 2022-02-07 16:36:07.094 - error: node-red.0 (12794) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4085: 2022-02-07 16:36:07.095 - error: node-red.0 (12794) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4093: 2022-02-07 16:36:42.236 - error: node-red.0 (12816) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4107: 2022-02-07 16:36:42.237 - error: node-red.0 (12816) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4115: 2022-02-07 16:37:17.352 - error: node-red.0 (12842) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4129: 2022-02-07 16:37:17.353 - error: node-red.0 (12842) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4139: 2022-02-07 16:37:52.185 - error: node-red.0 (12861) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4153: 2022-02-07 16:37:52.187 - error: node-red.0 (12861) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4165: 2022-02-07 16:38:27.178 - error: node-red.0 (12881) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4179: 2022-02-07 16:38:27.179 - error: node-red.0 (12881) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4193: 2022-02-07 16:39:02.224 - error: node-red.0 (12900) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4207: 2022-02-07 16:39:02.225 - error: node-red.0 (12900) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4215: 2022-02-07 16:39:37.216 - error: node-red.0 (12920) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4229: 2022-02-07 16:39:37.218 - error: node-red.0 (12920) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4237: 2022-02-07 16:40:12.457 - error: node-red.0 (12940) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4251: 2022-02-07 16:40:12.458 - error: node-red.0 (12940) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4259: 2022-02-07 16:40:47.783 - error: node-red.0 (12971) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4273: 2022-02-07 16:40:47.784 - error: node-red.0 (12971) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4283: 2022-02-07 16:41:23.235 - error: node-red.0 (12991) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4297: 2022-02-07 16:41:23.236 - error: node-red.0 (12991) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4309: 2022-02-07 16:41:58.235 - error: node-red.0 (13023) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4323: 2022-02-07 16:41:58.237 - error: node-red.0 (13023) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4334: 2022-02-07 16:42:33.052 - error: node-red.0 (13055) unhandled promise rejection: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org Line 4348: 2022-02-07 16:42:33.053 - error: node-red.0 (13055) Exception-Code: EFATAL: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org