NEWS
Telegram 1.0.8 Polling Error
-
Felhler bei update auf 1.08
! $ ./iobroker upgrade telegram
! ERROR: events.js:160 throw er; // Unhandled 'error' event
! ^
! Error: listen EADDRINUSE 127.0.0.1:9001
! at Object.exports._errnoException (util.js:1020:11)
! at exports._exceptionWithHostPort (util.js:1043:20)
! at Server._listen2 (net.js:1258:14)
! at listen (net.js:1294:10)
! at net.js:1404:9
! at _combinedTickCallback (internal/process/next_tick.js:83:11)
! at process._tickCallback (internal/process/next_tick.js:104:9)
! ERROR: process exited with code 1 -
Ich bin auf 1.0.6 zurückgestiegen,
Nach den Updates von neuen admin, web und was sonst noch alt war läft der jetzige telegram nicht mehr:
Jede Sekunde so ein Fehler:
telegram.0 2017-10-18 19:42:24.337 error polling_error:ETELEGRAM, Error: ETELEGRAM: 409 Conflict: terminated by other long poll or webhookHab's auf 2 Rechnern probiert, immer das gleiche.
-
Hi,
jetzt hat es mich auch wieder erwischt. (nach update auf 1.10)
Ich habe versucht
-
rechner neu gestartet
-
telegram neue Instance.1 und von dort probiert
-
beide instanzen gelöscht
-
adapter gelöscht
-
neu von git 1.11 installiert
ich habe node 4.8.1. Debug level ist auf debug. Alle Adaper sind auf dem aktuellen (stable Stand)
Es gibt aber keine weiteren Hinweise im log
Kann jemand helfen ?
vG Looxer
telegram.0 2018-02-03 13:29:42.127 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:40.714 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:39.353 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:37.049 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:35.749 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:33.806 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:32.269 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:30.906 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:29.478 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:28.171 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:26.790 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:25.409 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:24.024 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:22.792 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:21.495 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:20.265 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:18.715 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:17.464 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:16.112 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:14.776 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:12.531 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:11.248 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:09.975 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:08.668 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:07.362 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:06.072 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:04.766 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:03.469 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:02.198 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook telegram.0 2018-02-03 13:29:00.783 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook -
-
Sicher das nur ein Prozess vom Adapter nläuft? `
und hier ist der Telegramm prozess
root 4825 0.0 0.0 3060 1600 pts/0 S+ 15:57 0:00 grep telegram
also läuft nur einer
Sieht schon irgendwie nach einer Kollision aus. Keine Ahnung womit.
vG Looxer
-
Ne, du siehst nur das grep selbst, da läuft gar kein adapterprozess gerade … `
ups, da hast du allerdings recht. :oops:also hier ist auch der telegram:
7760 6.7 0.5 138484 48684 ? Sl 18:15 0:01 io.telegram.0
bleibt aber dabei: :D
vG Looxer
-
Hast du eine Lösung für das Problem gefunden?
Bei mir kommt zum Anfang:
` > telegram.0 2018-03-18 20:21:48.548 error at WS. (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
telegram.0 2018-03-18 20:21:48.548 error at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
telegram.0 2018-03-18 20:21:48.548 error at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
telegram.0 2018-03-18 20:21:48.548 error at Socket. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
telegram.0 2018-03-18 20:21:48.548 error at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
telegram.0 2018-03-18 20:21:48.548 error at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:246:12)
telegram.0 2018-03-18 20:21:48.548 error at Decoder.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:134:20)
telegram.0 2018-03-18 20:21:48.548 error at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
telegram.0 2018-03-18 20:21:48.548 error at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
telegram.0 2018-03-18 20:21:48.548 error at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
telegram.0 2018-03-18 20:21:48.548 error at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
telegram.0 2018-03-18 20:21:48.548 error at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:228:12)
telegram.0 2018-03-18 20:21:48.548 error at Socket.onevent (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:270:10)
telegram.0 2018-03-18 20:21:48.548 error at Socket.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
telegram.0 2018-03-18 20:21:48.548 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemClient.js:48:30)
telegram.0 2018-03-18 20:21:48.548 error at Object.change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3395:34)
telegram.0 2018-03-18 20:21:48.548 error at Adapter.emit (events.js:188:7)
telegram.0 2018-03-18 20:21:48.548 error at emitOne (events.js:96:13)
telegram.0 2018-03-18 20:21:48.548 error at Adapter. (/opt/iobroker/node_modules/iobroker.telegram/main.js:45:14)
telegram.0 2018-03-18 20:21:48.548 error at processMessage (/opt/iobroker/node_modules/iobroker.telegram/main.js:642:33)
telegram.0 2018-03-18 20:21:48.548 error at sendMessage (/opt/iobroker/node_modules/iobroker.telegram/main.js:508:22)
telegram.0 2018-03-18 20:21:48.548 error at _sendMessageHelper (/opt/iobroker/node_modules/iobroker.telegram/main.js:180:13)
telegram.0 2018-03-18 20:21:48.548 error TypeError: Cannot read property 'chatId' of undefined
telegram.0 2018-03-18 20:21:48.547 error message messagebox.system.adapter.telegram.0 [object Object] Cannot read property 'chatId' of undefined `
Wenn ich kurz aus- und wieder einschalte, kommt dann die Meldung:
telegram.0 2018-02-03 13:29:42.127 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other long poll or webhook
Habt ihr eine Lösung gefunden?
P.S. jetzt kommt folgende Meldung:
telegram.0 2018-03-18 20:28:28.037 error polling_error:ETELEGRAM, ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
-
Hi,
Da das Problem keine funktionalen Einschränkungen bedeutet habe ich einfach die Fehlermeldung im Adapter deaktiviert (im Coding) und Ruhe ist.
Bei Interesse kann ich die Stelle dokumentieren. Ich habe aber bis zum nächsten Wochenende keinen Zugriff auf sxstem.
Vg looxer
Von unterwegs
-
Hallo alle
Ich bin auf Node v8.14.0 und Nodejs v8.14.0
Der Telegramm Adapter ist V1.3.6
Das Log ist voll von polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized
host.ioBroker-Tinker 2019-01-05 14:20:07.617 info instance system.adapter.telegram.0 terminated with code 0 (OK) Caught 2019-01-05 14:20:07.617 error by controller[2]: at processImmediate [as _immediateCallback] (timers.js:745:5) Caught 2019-01-05 14:20:07.617 error by controller[2]: at tryOnImmediate (timers.js:768:5) Caught 2019-01-05 14:20:07.617 error by controller[2]: at runCallback (timers.js:810:20) Caught 2019-01-05 14:20:07.616 error by controller[2]: at Immediate.Async.drainQueues (/opt/iobroker/node_modules/bluebird/js/release/async.js:17:14) Caught 2019-01-05 14:20:07.616 error by controller[2]: at Async._drainQueues (/opt/iobroker/node_modules/bluebird/js/release/async.js:147:5) Caught 2019-01-05 14:20:07.616 error by controller[2]: at _drainQueue (/opt/iobroker/node_modules/bluebird/js/release/async.js:131:9) Caught 2019-01-05 14:20:07.616 error by controller[2]: at _drainQueueStep (/opt/iobroker/node_modules/bluebird/js/release/async.js:138:12) Caught 2019-01-05 14:20:07.615 error by controller[2]: at Promise._settlePromises (/opt/iobroker/node_modules/bluebird/js/release/promise.js:694:18) Caught 2019-01-05 14:20:07.615 error by controller[2]: at Promise._settlePromise0 (/opt/iobroker/node_modules/bluebird/js/release/promise.js:614:10) Caught 2019-01-05 14:20:07.615 error by controller[2]: at Promise._settlePromise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:569:18) Caught 2019-01-05 14:20:07.615 error by controller[2]: at Promise._settlePromiseFromHandler (/opt/iobroker/node_modules/bluebird/js/release/promise.js:512:31) Caught 2019-01-05 14:20:07.614 error by controller[2]: at tryCatcher (/opt/iobroker/node_modules/bluebird/js/release/util.js:16:23) Caught 2019-01-05 14:20:07.614 error by controller[2]: at request.then.resp (/opt/iobroker/node_modules/node-telegram-bot-api/src/telegram.js:280:15) Caught 2019-01-05 14:20:07.614 error by controller[2]: Unhandled rejection Error: ETELEGRAM: 401 Unauthorized Caught 2019-01-05 14:20:07.614 error by controller[1]: at processImmediate [as _immediateCallback] (timers.js:745:5) Caught 2019-01-05 14:20:07.613 error by controller[1]: at tryOnImmediate (timers.js:768:5) Caught 2019-01-05 14:20:07.613 error by controller[1]: at runCallback (timers.js:810:20) Caught 2019-01-05 14:20:07.613 error by controller[1]: at Immediate.Async.drainQueues (/opt/iobroker/node_modules/bluebird/js/release/async.js:17:14) Caught 2019-01-05 14:20:07.613 error by controller[1]: at Async._drainQueues (/opt/iobroker/node_modules/bluebird/js/release/async.js:147:5) Caught 2019-01-05 14:20:07.612 error by controller[1]: at _drainQueue (/opt/iobroker/node_modules/bluebird/js/release/async.js:131:9) Caught 2019-01-05 14:20:07.612 error by controller[1]: at _drainQueueStep (/opt/iobroker/node_modules/bluebird/js/release/async.js:138:12) Caught 2019-01-05 14:20:07.612 error by controller[1]: at Promise._settlePromises (/opt/iobroker/node_modules/bluebird/js/release/promise.js:694:18) Caught 2019-01-05 14:20:07.611 error by controller[1]: at Promise._settlePromise0 (/opt/iobroker/node_modules/bluebird/js/release/promise.js:614:10) Caught 2019-01-05 14:20:07.611 error by controller[1]: at Promise._settlePromise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:569:18) Caught 2019-01-05 14:20:07.611 error by controller[1]: at Promise._settlePromiseFromHandler (/opt/iobroker/node_modules/bluebird/js/release/promise.js:512:31) Caught 2019-01-05 14:20:07.611 error by controller[1]: at tryCatcher (/opt/iobroker/node_modules/bluebird/js/release/util.js:16:23) Caught 2019-01-05 14:20:07.610 error by controller[1]: at request.then.resp (/opt/iobroker/node_modules/node-telegram-bot-api/src/telegram.js:280:15) Caught 2019-01-05 14:20:07.610 error by controller[1]: Unhandled rejection Error: ETELEGRAM: 401 Unauthorized Caught 2019-01-05 14:20:07.610 error by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319\. at module.js:653:30 Caught 2019-01-05 14:20:07.609 error by controller[0]: In the future, you will have to enable it yourself. Caught 2019-01-05 14:20:07.609 error by controller[0]: Sat, 05 Jan 2019 13:19:51 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. telegram.0 2019-01-05 14:20:07.456 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized host.ioBroker-Tinker 2019-01-05 14:20:07.050 info stopInstance system.adapter.telegram.0 killing pid 16031 host.ioBroker-Tinker 2019-01-05 14:20:07.050 info stopInstance system.adapter.telegram.0 telegram.0 2019-01-05 14:20:07.052 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized host.ioBroker-Tinker 2019-01-05 14:20:07.046 info object change system.adapter.telegram.0 telegram.0 2019-01-05 14:20:06.659 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:06.281 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:05.874 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:05.464 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:05.101 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:04.716 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:04.338 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:03.737 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:03.342 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:02.958 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:02.591 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:02.248 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:01.908 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:01.519 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized tvspielfilm.0 2019-01-05 14:20:01.247 info objects written tvspielfilm.0 2019-01-05 14:20:01.217 info starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tvspielfilm, node: v8.14.0 tvspielfilm.0 2019-01-05 14:20:01.178 info States connected to redis: 127.0.0.1:6379 telegram.0 2019-01-05 14:20:01.128 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:00.730 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:20:00.344 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized host.ioBroker-Tinker 2019-01-05 14:20:00.057 info instance system.adapter.tvspielfilm.0 started with pid 16050 telegram.0 2019-01-05 14:19:59.975 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:59.614 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:59.273 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:58.869 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:58.478 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:58.099 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:57.735 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:57.325 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:56.926 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:56.538 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:56.165 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:55.808 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:55.466 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:55.056 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:54.649 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:54.290 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:53.919 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:53.509 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:53.106 error polling_error:ETELEGRAM, ETELEGRAM: 401 Unauthorized telegram.0 2019-01-05 14:19:51.841 info starting. Version 1.3.6 in /opt/iobroker/node_modules/iobroker.telegram, node: v8.14.0 telegram.0 2019-01-05 14:19:51.685 info States connected to redis: 127.0.0.1:6379Gruss Ralf
-
Habe jetzt einen neuen Bot erzeugt und eingetragen. Geht jetzt. Leider ist mir immer noch unklar warum es auf einmal nicht mehr ging, denn ich hatte an diesem Bot nie etwas geändert. Egal.
Jetzt gehts wieder.
@derrapf hatte das selbe Problem, neuer Bot + Token und alles funktioniert wider. Danke für Deinen Post
674
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge