Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE

AtomicIX

Hallo, ich habe ein Problem.
Ich nutze den ioBroker auf einen Intel NUC unter Proxmox im LXC Container.
Soweit läuft das alles super. Das Ganze steht bei mir im Schrebergarten und hängt an einer Fritzbox 6850 LTE mit einer Vodafon Sim .
Nun habe ich das Problem, das in unregelmäßigen Abständen die Adapter/Instanzen :
Alexa2.0, Cloud, Telegramm, Web, Offline gehen, bzw gelb werden.
Somit habe ich kein Kommunikation mehr zum System. Ich werde aber noch probieren, über Proxmox, auf Wireguard zu gehen.
Wenn die Instanzen gelb werden, kann ich entweder die Fritzbox oder den NUC, bzw den LXC neu starten.

Wie kann ich jetzt rausfinden, woran es hängt? Die Internet Verbinden ist die ganze Zeit stabil.

DJMarc75

@atomicix sagte in Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE:

Vodafon Sim

@atomicix sagte in Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE:

Alexa2.0, Cloud, Telegramm, Web, Offline gehen, bzw gelb werden

Sobald auch nur kurzzeitig kein Internet/Netzwerk besteht werden diese Instanzen "mindestens" neu gestartet.
Schau ins LOG wenn dies passiert und poste das hier in Codetags bitte.

@atomicix sagte in Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE:

Die Internet Verbinden ist die ganze Zeit stabil.

Das wage ich zu bezweifeln ;)

AtomicIX

@djmarc75
Es kann natürlich sein, das die Verbindung , kurzzeitig unterbrochen ist, aber ein einfacher neustart der Adapter/Instanzen bringt keine Änderung. Es muss wirklich die Fritzbox oder der ioBroker/LXC neu gestartet werden.
Da es meist nur passiert, wenn ich nicht im Garten bin, muss ich mal sehen, wie ich ein Log bekomme.
Ich kann über einen Amazon Plug den NUC neustarten aus der Ferne, ist aber halt keine schöne Sache, aber so bekomme ich das System wenigsten wieder zum laufen.

Ok,ich werde malprobieren, ob ich ein Log bekomme.

Thomas Braun

@atomicix sagte in Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE:

Ich kann über einen Amazon Plug den NUC neustarten

Das ist kein Neustart, das ist Harakiri.

AtomicIX

Ich habe jetzt ein Stück Log von heute morgen. Leider nur mit dem Handy, aber morgens ist nicht viel Zeit.

Es ist nur Telegramm offline gewesen, Alexa, Cloud , liefen noch.
@DJMarc75

2023-05-15 00:01:05.451 - error: telegram.2 (70633) getMe (reconnect #320) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:01:22.710 - info: netatmo.0 (88204) API Warning: getStationsDataError error: No response
2023-05-15 00:01:46.188 - error: telegram.0 (234) getMe (reconnect #360) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:04:35.632 - error: telegram.2 (70633) getMe (reconnect #330) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:05:16.358 - error: telegram.0 (234) getMe (reconnect #370) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:08:05.804 - error: telegram.2 (70633) getMe (reconnect #340) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:08:46.535 - error: telegram.0 (234) getMe (reconnect #380) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:11:22.711 - info: netatmo.0 (88204) API Warning: getStationsDataError error: No response
2023-05-15 00:11:35.987 - error: telegram.2 (70633) getMe (reconnect #350) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:12:16.710 - error: telegram.0 (234) getMe (reconnect #390) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:12:48.370 - error: telegram.2 (70633) getMe (reconnect) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:15:14.495 - error: telegram.2 (70633) getMe (reconnect #360) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:15:46.886 - error: telegram.0 (234) getMe (reconnect #400) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:18:44.683 - error: telegram.2 (70633) getMe (reconnect #370) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:19:17.060 - error: telegram.0 (234) getMe (reconnect #410) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:19:37.074 - error: telegram.0 (234) getMe (reconnect) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:20:35.659 - error: info.0 (478) Error: getaddrinfo EAI_AGAIN raw.githubusercontent.com
2023-05-15 00:21:22.710 - info: netatmo.0 (88204) API Warning: getStationsDataError error: No response
2023-05-15 00:22:14.854 - error: telegram.2 (70633) getMe (reconnect #380) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:22:50.998 - error: telegram.0 (234) getMe (reconnect #420) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:25:45.022 - error: telegram.2 (70633) getMe (reconnect #390) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:26:21.179 - error: telegram.0 (234) getMe (reconnect #430) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:29:15.194 - error: telegram.2 (70633) getMe (reconnect #400) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:29:51.360 - error: telegram.0 (234) getMe (reconnect #440) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:31:22.710 - info: netatmo.0 (88204) API Warning: getStationsDataError error: No response
2023-05-15 00:32:45.366 - error: telegram.2 (70633) getMe (reconnect #410) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:33:21.549 - error: telegram.0 (234) getMe (reconnect #450) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:36:15.538 - error: telegram.2 (70633) getMe (reconnect #420) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:36:51.718 - error: telegram.0 (234) getMe (reconnect #460) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:39:45.704 - error: telegram.2 (70633) getMe (reconnect #430) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:40:21.890 - error: telegram.0 (234) getMe (reconnect #470) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:41:22.710 - info: netatmo.0 (88204) API Warning: getStationsDataError error: No response
2023-05-15 00:43:15.875 - error: telegram.2 (70633) getMe (reconnect #440) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:43:52.066 - error: telegram.0 (234) getMe (reconnect #480) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:46:46.031 - error: telegram.2 (70633) getMe (reconnect #450) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:47:22.247 - error: telegram.0 (234) getMe (reconnect #490) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:50:16.226 - error: telegram.2 (70633) getMe (reconnect #460) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:50:35.658 - error: info.0 (478) Error: getaddrinfo EAI_AGAIN raw.githubusercontent.com
2023-05-15 00:50:38.275 - error: alexa2.0 (418) 48f6ee71637d460688d6785b847dd071 Error getting aux controller state: Error: Timeout
2023-05-15 00:50:52.426 - error: telegram.0 (234) getMe (reconnect #500) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:50:58.280 - error: alexa2.0 (418) G2T0T00480440M0R Error getting aux controller state: Error: Timeout
2023-05-15 00:51:18.283 - error: alexa2.0 (418) G090U509917528CQ Error getting equalizer enabled: Error: Timeout
2023-05-15 00:51:22.710 - info: netatmo.0 (88204) API Warning: getStationsDataError error: No response
2023-05-15 00:51:38.287 - error: alexa2.0 (418) G090U509917528CQ Error getting aux controller state: Error: Timeout
2023-05-15 00:51:58.291 - error: alexa2.0 (418) G090XG0894222DC6 Error getting equalizer enabled: Error: Timeout
2023-05-15 00:52:18.295 - error: alexa2.0 (418) G090XG0894222DC6 Error getting aux controller state: Error: Timeout
2023-05-15 00:52:38.297 - error: alexa2.0 (418) b2d17c8032a1433397eb093609852c96 Error getting aux controller state: Error: Timeout
2023-05-15 00:52:58.300 - error: alexa2.0 (418) G070RQ13921500B3 Error getting equalizer enabled: Error: Timeout
2023-05-15 00:53:18.304 - error: alexa2.0 (418) G070RQ13921500B3 Error getting aux controller state: Error: Timeout
2023-05-15 00:53:38.308 - error: alexa2.0 (418) G091GG10145300VR Error getting equalizer enabled: Error: Timeout
2023-05-15 00:53:46.398 - error: telegram.2 (70633) getMe (reconnect #470) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:53:58.311 - error: alexa2.0 (418) G091GG10145300VR Error getting aux controller state: Error: Timeout
2023-05-15 00:54:18.314 - error: alexa2.0 (418) G090U610918622K8 Error getting equalizer enabled: Error: Timeout
2023-05-15 00:54:22.610 - error: telegram.0 (234) getMe (reconnect #510) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:54:38.316 - error: alexa2.0 (418) G090U610918622K8 Error getting aux controller state: Error: Timeout
2023-05-15 00:54:58.319 - error: alexa2.0 (418) G0911M0894260B1E Error getting equalizer enabled: Error: Timeout
2023-05-15 00:55:18.322 - error: alexa2.0 (418) G0911M0894260B1E Error getting aux controller state: Error: Timeout
2023-05-15 00:55:38.325 - error: alexa2.0 (418) GCC19D06217601PW Error getting aux controller state: Error: Timeout
2023-05-15 00:55:58.328 - error: alexa2.0 (418) G091JJ14216309R1 Error getting equalizer enabled: Error: Timeout
2023-05-15 00:56:18.330 - error: alexa2.0 (418) G091JJ14216309R1 Error getting aux controller state: Error: Timeout
2023-05-15 00:56:38.332 - error: alexa2.0 (418) G091JJ14216309R1 Error getting display enabled setting: Error: Timeout
2023-05-15 00:56:58.334 - error: alexa2.0 (418) G091JJ14216309R1 Error getting display brightness setting: Error: Timeout
2023-05-15 00:57:16.570 - error: telegram.2 (70633) getMe (reconnect #480) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:57:18.337 - error: alexa2.0 (418) G091JJ14216309R1 Error getting display adaptive brightness setting: Error: Timeout
2023-05-15 00:57:33.660 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":20}
2023-05-15 00:57:33.661 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":20,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:57:36.661 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":21}
2023-05-15 00:57:36.661 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":21,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:57:38.340 - error: alexa2.0 (418) G071CQ052462076F Error getting aux controller state: Error: Timeout
2023-05-15 00:57:48.662 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":20}
2023-05-15 00:57:48.662 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":20,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:57:51.662 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":21}
2023-05-15 00:57:51.662 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":21,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:57:52.782 - error: telegram.0 (234) getMe (reconnect #520) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 00:57:54.664 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":20}
2023-05-15 00:57:54.664 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":20,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:57:58.344 - error: alexa2.0 (418) G0911M0894260B6R Error getting equalizer enabled: Error: Timeout
2023-05-15 00:58:12.672 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":21}
2023-05-15 00:58:12.672 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":21,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:58:15.668 - info: gree_aircon.0 (1822) ClientPollUpdate: updatesProperties:{"currentTemperature":20}
2023-05-15 00:58:15.668 - info: gree_aircon.0 (1822) ClientPollUpdate: nowProperties:{"power":"off","mode":"fan_only","temperatureUnit":"celsius","temperature":26,"currentTemperature":20,"fanSpeed":"low","air":"off","blow":"off","health":"off","sleep":"off","lights":"on","swingHor":"default","swingVert":"default","quiet":"off","turbo":"off","powerSave":"off","safetyHeating":"off"}
2023-05-15 00:58:18.348 - error: alexa2.0 (418) G0911M0894260B6R Error getting aux controller state: Error: Timeout
2023-05-15 00:58:38.351 - error: alexa2.0 (418) G0922K0724840J8B Error getting equalizer enabled: Error: Timeout
2023-05-15 00:58:58.354 - error: alexa2.0 (418) G0922K0724840J8B Error getting aux controller state: Error: Timeout
2023-05-15 00:59:18.357 - error: alexa2.0 (418) G090LF0965150CE4 Error getting equalizer enabled: Error: Timeout
2023-05-15 00:59:38.359 - error: alexa2.0 (418) G090LF0965150CE4 Error getting aux controller state: Error: Timeout
2023-05-15 00:59:58.362 - error: alexa2.0 (418) G090LF1072571W8X Error getting equalizer enabled: Error: Timeout
2023-05-15 01:00:00.006 - info: netatmo.0 (88204) Scheduled restart.
2023-05-15 01:00:00.007 - info: netatmo.0 (88204) cleaned everything up...
2023-05-15 01:00:00.042 - info: netatmo.0 (88204) terminating
2023-05-15 01:00:00.043 - info: netatmo.0 (88204) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-05-15 01:00:00.584 - info: host.ioBroker instance system.adapter.netatmo.0 scheduled normal terminated and will be restarted on schedule.
2023-05-15 01:00:00.586 - info: host.ioBroker Restart adapter system.adapter.netatmo.0 because enabled
2023-05-15 01:00:01.637 - info: host.ioBroker instance system.adapter.netatmo.0 started with pid 111069
2023-05-15 01:00:02.306 - info: netatmo.0 (111069) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.netatmo, node: v18.16.0, js-controller: 4.0.24
2023-05-15 01:00:02.349 - info: netatmo.0 (111069) Using stored tokens to initialize ... {"access_token":"5f44af303450c76dd4597a68|597e1d21c25f8b195e9e4c1d28ef19ae","refresh_token":"5f44af303450c76dd4597a68|e9ca1cba4fe7d0737cf48ec138247b34","scope":"read_station","client_id":"574ddd152baa3cf9598b46cd"}
2023-05-15 01:00:02.350 - warn: netatmo.0 (111069) Invalid check interval "10", fallback to 10 minutes
2023-05-15 01:00:02.350 - info: netatmo.0 (111069) Authenticating with Netatmo using general ioBroker client
2023-05-15 01:00:18.364 - error: alexa2.0 (418) G090LF1072571W8X Error getting aux controller state: Error: Timeout
2023-05-15 01:00:22.405 - info: netatmo.0 (111069) API Warning: Authenticate refresh error: No response
2023-05-15 01:00:22.406 - info: netatmo.0 (111069) Successfully authenticated with Netatmo with general ioBroker client
2023-05-15 01:00:38.369 - error: alexa2.0 (418) G090L91072041UNM Error getting equalizer enabled: Error: Timeout
2023-05-15 01:00:46.738 - error: telegram.2 (70633) getMe (reconnect #490) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 01:00:58.372 - error: alexa2.0 (418) G090L91072041UNM Error getting aux controller state: Error: Timeout
2023-05-15 01:01:00.009 - info: netatmo.0 (111069) Scheduled restart.
2023-05-15 01:01:00.009 - info: netatmo.0 (111069) cleaned everything up...
2023-05-15 01:01:00.046 - info: netatmo.0 (111069) terminating
2023-05-15 01:01:00.047 - info: netatmo.0 (111069) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-05-15 01:01:00.586 - info: host.ioBroker instance system.adapter.netatmo.0 scheduled normal terminated and will be restarted on schedule.
2023-05-15 01:01:00.586 - info: host.ioBroker Restart adapter system.adapter.netatmo.0 because enabled
2023-05-15 01:01:05.989 - info: host.ioBroker instance system.adapter.netatmo.0 started with pid 111183
2023-05-15 01:01:06.772 - info: netatmo.0 (111183) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.netatmo, node: v18.16.0, js-controller: 4.0.24
2023-05-15 01:01:06.828 - info: netatmo.0 (111183) Using stored tokens to initialize ... {"access_token":"5f44af303450c76dd4597a68|597e1d21c25f8b195e9e4c1d28ef19ae","refresh_token":"5f44af303450c76dd4597a68|e9ca1cba4fe7d0737cf48ec138247b34","scope":"read_station","client_id":"574ddd152baa3cf9598b46cd"}
2023-05-15 01:01:06.828 - warn: netatmo.0 (111183) Invalid check interval "10", fallback to 10 minutes
2023-05-15 01:01:06.829 - info: netatmo.0 (111183) Authenticating with Netatmo using general ioBroker client
2023-05-15 01:01:18.375 - error: alexa2.0 (418) G0922K0724840L11 Error getting equalizer enabled: Error: Timeout
2023-05-15 01:01:22.961 - error: telegram.0 (234) getMe (reconnect #530) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 01:01:26.890 - info: netatmo.0 (111183) API Warning: Authenticate refresh error: No response
2023-05-15 01:01:26.891 - info: netatmo.0 (111183) Successfully authenticated with Netatmo with general ioBroker client
2023-05-15 01:01:38.377 - error: alexa2.0 (418) G0922K0724840L11 Error getting aux controller state: Error: Timeout
2023-05-15 01:01:58.379 - error: alexa2.0 (418) G090LF0965221HVF Error getting equalizer enabled: Error: Timeout
2023-05-15 01:02:18.380 - error: alexa2.0 (418) G090LF0965221HVF Error getting aux controller state: Error: Timeout
2023-05-15 01:02:38.384 - error: alexa2.0 (418) G090LF11842701AU Error getting equalizer enabled: Error: Timeout
2023-05-15 01:02:58.386 - error: alexa2.0 (418) G090LF11842701AU Error getting aux controller state: Error: Timeout
2023-05-15 01:03:18.390 - error: alexa2.0 (418) G0723H0824820AV8 Error getting aux controller state: Error: Timeout
2023-05-15 01:03:38.393 - error: alexa2.0 (418) 428ce2eeba1243afbc717d5735fbeda9 Error getting aux controller state: Error: Timeout
2023-05-15 01:03:58.395 - error: alexa2.0 (418) G090L90964351BUH Error getting equalizer enabled: Error: Timeout
2023-05-15 01:04:16.910 - error: telegram.2 (70633) getMe (reconnect #500) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 01:04:18.397 - error: alexa2.0 (418) G090L90964351BUH Error getting aux controller state: Error: Timeout
2023-05-15 01:04:38.401 - error: alexa2.0 (418) 815fcfa49d9c4cbbaa0c88b2888b0e40 Error getting aux controller state: Error: Timeout
2023-05-15 01:04:53.126 - error: telegram.0 (234) getMe (reconnect #540) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 01:04:58.403 - error: alexa2.0 (418) 133e9d4024aa40b5863fcba0389f8f72 Error getting aux controller state: Error: Timeout
2023-05-15 01:05:18.406 - error: alexa2.0 (418) 129e7a677d214096b47d77433eb9c706 Error getting aux controller state: Error: Timeout
2023-05-15 01:05:38.408 - error: alexa2.0 (418) ab8cd1e6f6484b2199b31daa29f171e0 Error getting aux controller state: Error: Timeout
2023-05-15 01:06:02.314 - error: alexa2.0 (418) d8a0fd8ed23140489659ad918334c1f0 Error getting aux controller state: Error: Timeout
2023-05-15 01:06:02.321 - warn: modbus.0 (294) Error: undefined
2023-05-15 01:06:02.332 - error: modbus.0 (294) Request timed out.
2023-05-15 01:06:02.332 - error: modbus.0 (294) Client in error state.
2023-05-15 01:06:02.333 - warn: modbus.0 (294) Poll error count: 1 code: {"err":"timeout","timeout":5000}
2023-05-15 01:06:03.333 - info: modbus.0 (294) Disconnected from slave 192.168.222.200
2023-05-15 01:06:22.320 - error: alexa2.0 (418) 35f9258ea4f74aabb9db5f57ef6fc568 Error getting aux controller state: Error: Timeout
2023-05-15 01:06:42.324 - error: alexa2.0 (418) 3d9f00a17d004da7a5d55938a5420ba8 Error getting aux controller state: Error: Timeout
2023-05-15 01:07:02.327 - error: alexa2.0 (418) b2b8adb9f98b4cf3abd8a58a6e4990e1 Error getting aux controller state: Error: Timeout
2023-05-15 01:07:03.335 - info: modbus.0 (294) Connected to slave 192.168.222.200
2023-05-15 01:07:22.330 - error: alexa2.0 (418) 67f22ada662d4400a3740daec10adf5c Error getting aux controller state: Error: Timeout
2023-05-15 01:07:42.334 - error: alexa2.0 (418) fa21f65529724fbda617be7340264e97 Error getting aux controller state: Error: Timeout
2023-05-15 01:07:57.412 - error: telegram.2 (70633) getMe (reconnect #510) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 01:08:02.338 - error: alexa2.0 (418) 38d4fad5b88b4b2a85ae9c9b271a216f Erro

Thomas Braun

@atomicix
Da funktioniert die Adress-Auflösung nicht.

2023-05-15 01:00:46.738 - error: telegram.2 (70633) getMe (reconnect #490) Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org

AtomicIX

@thomas-braun und das bedeutet was? Bzw was könnte man daran ändern? Hängt das damit zusammen, das ich das über Mobilfunk betreibe?

Thomas Braun

@atomicix sagte in Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE:

Hängt das damit zusammen, das ich das über Mobilfunk betreibe?

Möglicherweise.

AtomicIX

Hier noch mal ein aktueller Log.
Habe den NUC und die Fritzbox mal komplett neu gestartet.
Leider bekomme ich die Instanzen jetzt gar nicht mehr auf Grün.
Wie kann ich denn jetzt weiter machen. ?

2023-05-15 17:47:37.757 - error: telegram.0 (1217) setWebHook Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 17:47:38.951 - error: telegram.2 (1232) setWebHook Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 17:47:41.760 - info: host.ioBroker "system.adapter.alexa2.0" disabled
2023-05-15 17:47:42.446 - error: iot.0 (562) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2023-05-15 17:47:42.446 - error: iot.0 (562) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2023-05-15 17:47:42.447 - info: iot.0 (562) Connection changed: disconnect
2023-05-15 17:47:43.695 - info: host.ioBroker "system.adapter.alexa2.0" enabled
2023-05-15 17:47:43.776 - info: host.ioBroker instance system.adapter.alexa2.0 started with pid 1263
2023-05-15 17:47:44.431 - info: alexa2.0 (1263) starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.16.0, js-controller: 4.0.24
2023-05-15 17:47:44.450 - info: alexa2.0 (1263) Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
2023-05-15 17:47:44.451 - info: alexa2.0 (1263) Proxy IP not set, use first network interface (192.168.222.210) instead
2023-05-15 17:47:45.698 - info: host.ioBroker "system.adapter.cloud.0" disabled
2023-05-15 17:47:45.698 - info: host.ioBroker stopInstance system.adapter.cloud.0 (force=false, process=true)
2023-05-15 17:47:45.703 - info: cloud.0 (1247) Got terminate signal TERMINATE_YOURSELF
2023-05-15 17:47:45.704 - info: cloud.0 (1247) terminating
2023-05-15 17:47:45.705 - info: cloud.0 (1247) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-05-15 17:47:45.742 - info: host.ioBroker stopInstance system.adapter.cloud.0 send kill signal
2023-05-15 17:47:46.242 - info: host.ioBroker instance system.adapter.cloud.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-05-15 17:47:46.547 - error: javascript.0 (207) Request error: Error: connect EHOSTUNREACH 192.168.222.233:80
2023-05-15 17:47:46.547 - error: javascript.0 (207) script.js.Garten.Telegram.Überwachung.Solarbatterie-Steuerung: {'errno':-113,'code':'EHOSTUNREACH','syscall':'connect','address':'192.168.222.233','port':80}
2023-05-15 17:47:47.871 - info: host.ioBroker "system.adapter.cloud.0" enabled
2023-05-15 17:47:47.951 - info: host.ioBroker instance system.adapter.cloud.0 started with pid 1279
2023-05-15 17:47:48.687 - info: cloud.0 (1279) starting. Version 4.3.0 in /opt/iobroker/node_modules/iobroker.cloud, node: v18.16.0, js-controller: 4.0.24
2023-05-15 17:47:48.708 - info: cloud.0 (1279) Connecting with https://iobroker.pro:10555 with "@pro_elbschrauber.christian@gmail.com_5920e7d0-46d1-11eb-b2c7-27"
2023-05-15 17:47:48.778 - info: cloud.0 (1279) Trying to connect as system.user.admin to cloud
2023-05-15 17:47:52.057 - info: host.ioBroker "system.adapter.iot.0" disabled
2023-05-15 17:47:52.057 - info: host.ioBroker stopInstance system.adapter.iot.0 (force=false, process=true)
2023-05-15 17:47:52.059 - info: iot.0 (562) Got terminate signal TERMINATE_YOURSELF
2023-05-15 17:47:52.060 - info: iot.0 (562) terminating
2023-05-15 17:47:52.060 - info: iot.0 (562) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-05-15 17:47:52.108 - info: host.ioBroker stopInstance system.adapter.iot.0 send kill signal
2023-05-15 17:47:53.108 - info: host.ioBroker stopInstance system.adapter.iot.0 killing pid 562
2023-05-15 17:47:53.716 - info: host.ioBroker "system.adapter.iot.0" enabled
2023-05-15 17:47:53.793 - info: host.ioBroker instance system.adapter.iot.0 started with pid 1388
2023-05-15 17:47:54.251 - error: iot.0 (1388) iot.0 already running
2023-05-15 17:47:54.253 - warn: iot.0 (1388) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-15 17:47:54.795 - error: host.ioBroker instance system.adapter.iot.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-15 17:47:54.795 - info: host.ioBroker Restart adapter system.adapter.iot.0 because enabled
2023-05-15 17:47:57.549 - info: telegram.0 (1217) Adapter is disabled => stop
2023-05-15 17:47:57.553 - info: host.ioBroker "system.adapter.telegram.0" disabled
2023-05-15 17:47:57.553 - info: host.ioBroker stopInstance system.adapter.telegram.0 (force=false, process=true)
2023-05-15 17:47:57.565 - info: telegram.0 (1217) Got terminate signal TERMINATE_YOURSELF
2023-05-15 17:47:57.598 - info: host.ioBroker stopInstance system.adapter.telegram.0 send kill signal
2023-05-15 17:47:57.768 - error: telegram.0 (1217) getMe Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 17:47:58.058 - info: telegram.0 (1217) terminating
2023-05-15 17:47:58.058 - info: telegram.0 (1217) Terminated (NO_ERROR): Without reason
2023-05-15 17:47:58.594 - info: telegram.2 (1232) Adapter is disabled => stop
2023-05-15 17:47:58.594 - info: host.ioBroker "system.adapter.telegram.2" disabled
2023-05-15 17:47:58.594 - info: host.ioBroker stopInstance system.adapter.telegram.2 (force=false, process=true)
2023-05-15 17:47:58.599 - info: host.ioBroker stopInstance system.adapter.telegram.0 killing pid 1217
2023-05-15 17:47:58.600 - info: telegram.2 (1232) Got terminate signal TERMINATE_YOURSELF
2023-05-15 17:47:58.642 - info: host.ioBroker stopInstance system.adapter.telegram.2 send kill signal
2023-05-15 17:47:58.770 - error: cloud.0 (1279) Error while connecting to cloud: timeout
2023-05-15 17:47:58.961 - error: telegram.2 (1232) getMe Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 17:47:59.100 - info: telegram.2 (1232) terminating
2023-05-15 17:47:59.101 - info: telegram.2 (1232) Terminated (NO_ERROR): Without reason
2023-05-15 17:47:59.504 - info: host.ioBroker "system.adapter.telegram.0" enabled
2023-05-15 17:47:59.603 - info: host.ioBroker instance system.adapter.telegram.0 started with pid 1399
2023-05-15 17:47:59.642 - info: host.ioBroker stopInstance system.adapter.telegram.2 killing pid 1232
2023-05-15 17:48:00.450 - info: telegram.0 (1399) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.0, js-controller: 4.0.24
2023-05-15 17:48:01.447 - info: host.ioBroker "system.adapter.telegram.2" enabled
2023-05-15 17:48:01.488 - info: host.ioBroker instance system.adapter.telegram.2 started with pid 1417
2023-05-15 17:48:02.254 - info: telegram.2 (1417) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.0, js-controller: 4.0.24
2023-05-15 17:48:04.580 - error: alexa2.0 (1263) Error:
2023-05-15 17:48:04.580 - error: alexa2.0 (1263) Error: You can try to get the cookie manually by opening http://192.168.222.210:36775/ with your browser.
2023-05-15 17:48:12.497 - error: host.ioBroker instance system.adapter.iot.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2023-05-15 17:48:12.497 - info: host.ioBroker Do not restart adapter system.adapter.iot.0 because desired by instance
2023-05-15 17:48:16.563 - error: javascript.0 (207) Request error: Error: connect EHOSTUNREACH 192.168.222.233:80
2023-05-15 17:48:16.563 - error: javascript.0 (207) script.js.Garten.Telegram.Überwachung.Solarbatterie-Steuerung: {'errno':-113,'code':'EHOSTUNREACH','syscall':'connect','address':'192.168.222.233','port':80}
2023-05-15 17:48:17.813 - info: host.ioBroker instance system.adapter.telegram.0 terminated with code 0 (NO_ERROR)
2023-05-15 17:48:17.813 - info: host.ioBroker Restart adapter system.adapter.telegram.0 because enabled
2023-05-15 17:48:18.716 - info: cloud.0 (1279) Trying to connect as system.user.admin to cloud
2023-05-15 17:48:19.013 - info: host.ioBroker instance system.adapter.telegram.2 terminated with code 0 (NO_ERROR)
2023-05-15 17:48:19.013 - info: host.ioBroker Restart adapter system.adapter.telegram.2 because enabled
2023-05-15 17:48:20.630 - error: telegram.0 (1399) setWebHook Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 17:48:22.442 - error: telegram.2 (1417) setWebHook Error:Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
2023-05-15 17:48:24.834 - info: host.ioBroker instance system.adapter.iot.0 started with pid 1433
2023-05-15 17:48:25.547 - info: iot.0 (1433) starting. Version 1.14.2 in /opt/iobroker/node_modules/iobroker.iot, node: v18.16.0, js-controller: 4.0.24
2023-05-15 17:48:25.582 - info: iot.0 (1433) Connecting with a18wym7vjdl22g.iot.eu-west-1.amazonaws.com
2023-05-15 17:48:28.713 - error: cloud.0 (1279) Error while connecting to cloud: timeout

Community Forum

NEWS

Web, Alexa, Telegramm zeitweise Gelb Fritzbox 6850 LTE

Support us

462

32.8k

82.9k

1.3m