NEWS
[gelöst] telegram adapter polling_error
-
Hallo zusammen,
ich weiß leider nicht seit wann, aber mein Log wird von telegram polling_error überschwemmt:
telegram.0 2019-01-09 11:32:13.492 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:32:06.779 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:32:00.006 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:53.284 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:46.483 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:39.768 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:33.055 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:26.340 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:19.616 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:12.898 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:31:06.179 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:30:59.461 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:30:52.747 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:30:46.032 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2019-01-09 11:30:39.318 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
Folgendes ist bei mir im Einsatz:
Telegram Adapter: 1.3.5
Node: v8.13.0
Nodejs: v8.13.0
npm: 6.4.1
Zugriff auf den Chat_bot von: 2x Smartphone und dem iobroker telegram adapter
Auch nach einem reboot gibt es keine Besserung.
Woran könnte das liegen?
Besten Dank
Michael
-
Gab hier mal einen Lösungsvorschlag: viewtopic.php?t=8326#p88429
-
Hallo,
es lag scheinbar an etwas was ich nicht genau sagen kann
Ich habe mehrere andere Fehler im Log behoben gehabt und mein Container neu erstellt, jetzt läuft alles wieder ohne Fehlermeldungen.
Danke dir trotzdem.
Beste Grüße
Michael
-
Hallo zusammen,
ich habe aktuell das gleiche Problem.
elegram.0 2022-10-23 08:54:35.060 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:54:27.511 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:54:19.828 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:54:12.274 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:54:04.725 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:57.124 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:49.538 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:41.959 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:34.424 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:26.841 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:19.285 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:11.591 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running telegram.0 2022-10-23 08:53:04.036 warn polling_error: ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
Ich habe jedoch nur eine Instanz laufen.
Telegram Adapter: 1.14.1
Node: v16.18.0
Nodejs: v18.18.0
npm: 8.19.2
Gibt es hierzu einen Lösungsvorschlag?
Vielen Dank im Voraus!
Holger -
@timtaylor sagte in [gelöst] telegram adapter polling_error:
ETELEGRAM: 409 Conflict
Seit wann hast Du diese Meldungen ?
Wenn erst seit heute wäre die einfachste Lösung den Browsercache zu leeren.
Falls dann immernoch Warnmeldungen kommen mal den Adapter neu starten und/oder die Kiste auf der Du iob nutzt rebooten. -
Danke für Deine Antwort. Die Meldungen sind schon länger da. Ich habe jetzt aber mal einen neuen API Key in Telegram generiert. Nun ist die Meldung weg.