Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Telegram 1.0.8 Polling Error

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Telegram 1.0.8 Polling Error

    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pix last edited by

      Bin auf 1.0.6 gegangen, noch mehr Fehler. ioBroker Neustart (killall.sh hat nicht gegriffen, also Rechner neu gestartet), telegram update auf 1.0.8 gemacht, jetzt läuft alles wieder :lol:

      Pix

      1 Reply Last reply Reply Quote 0
      • Bluefox
        Bluefox last edited by

        @looxer01:

        Hi,

        ich habe gerade den Adapter auf 1.08. gebracht und erhalte den folgenden Fehler:

        Laut change log ist ein log Eintrag hinzugekommen, um den polling error anzuzeigen. Sieht aber so aus, dass der error immer angezeigt wird, auch wenn keiner vorliegt ?

        Caught	2017-10-04 15:55:03.794	error	by controller[14]: 2017-10-04 15:55:03.549 - telegram.0 polling_error:ETELEGRAM, Error: ETELEGRAM: 409 Conflict: terminated by other long poll or webhook

        Bin zurück auf 1.0.6 (auf 1.0.7 ging nicht )

        vG Looxer `
        Wir brauchen mehr Logs. Man muss wissen was vorher passiert.

        1 Reply Last reply Reply Quote 0
        • L
          looxer01 last edited by

          @Bluefox:

          Wir brauchen mehr Logs. Man muss wissen was vorher passiert. `

          ich habe auf "debug" gestellt. Es gibt aber nicht viel mehr.

          Allerdings ein Hinweis auf Node > 5.x. ich habe 4.8.1

          Caught	2017-10-04 20:37:28.365	error	by controller[8]: 2017-10-04 20:37:04.104 - telegram.0 polling_error:ETELEGRAM, Error: ETELEGRAM: 409 Conflict: terminated by other long poll or webhook
Caught	2017-10-04 20:37:28.364	error	by controller[7]: 2017-10-04 20:37:02.941 - telegram.0 polling_error:ETELEGRAM, Error: ETELEGRAM: 409 Conflict: terminated by other long poll or webhook
Caught	2017-10-04 20:37:28.364	error	by controller[6]: 2017-10-04 20:37:02.190 - telegram.0 Message sent
Caught	2017-10-04 20:37:28.364	error	by controller[5]: 2017-10-04 20:37:02.116 - telegram.0 Send message to "xxxx": Started!
Caught	2017-10-04 20:37:28.364	error	by controller[4]: 2017-10-04 20:37:02.012 - telegram.0 redis pmessage io.telegram.0.communicate.response io.telegram.0.communicate.response {"val":"","ack":true,"ts":1507142222008,"q":0,"from":"sy
Caught	2017-10-04 20:37:28.364	error	by controller[3]: 2017-10-04 20:37:02.010 - telegram.0 redis pmessage io.telegram.0.communicate.request io.telegram.0.communicate.request {"val":"","ack":true,"ts":1507142222008,"q":0,"from":"syst
Caught	2017-10-04 20:37:28.364	error	by controller[2]: 2017-10-04 20:37:01.936 - telegram.0 statesDB connected
Caught	2017-10-04 20:37:28.364	error	by controller[1]: 2017-10-04 20:37:01.924 - telegram.0 objectDB connected
Caught	2017-10-04 20:37:28.364	error	by controller[0]: Wed, 04 Oct 2017 18:37:01 GMT node-telegram-bot-api deprecated Node.js v5.x and below will no longer be supported in the future at module.js:409:26
telegram.0	2017-10-04 20:37:28.352	info	terminating
telegram.0	2017-10-04 20:37:27.914	debug	Message sent
host.iobroker	2017-10-04 20:37:27.847	info	stopInstance system.adapter.telegram.0 killing pid 1387
host.iobroker	2017-10-04 20:37:27.847	info	stopInstance system.adapter.telegram.0
telegram.0	2017-10-04 20:37:27.849	debug	Send message to "xxxx": Restarting...
host.iobroker	2017-10-04 20:37:27.846	info	object change system.adapter.telegram.0

          vG Looxer

          1 Reply Last reply Reply Quote 0
          • L
            looxer01 last edited by

            habe es gerade mit node 6.11.4 getestet.

            gleicher Fehler. Was kann ich noch liefern, um den Fehler einzugrenzen ?

            vG Looxer

            1 Reply Last reply Reply Quote 0
            • H
              Haba last edited by

              @looxer01:

              habe es gerade mit node 6.11.4 getestet.

              gleicher Fehler. Was kann ich noch liefern, um den Fehler einzugrenzen ?

              vG Looxer `

              Hi! Please test https://github.com/Haba1234/ioBroker.telegram

              Debugging muss aktiviert sein.

              1 Reply Last reply Reply Quote 0
              • L
                looxer01 last edited by

                Hi,
                @Haba:

                Hi! Please test https://github.com/Haba1234/ioBroker.telegram `

                perfekt. Es gibt keine Fehler mehr und es funktioniert.

                Im Moment ist es Version 1.0.7, also kleiner als 1.0.8

                Vielen Dank.

                Looxer

                1 Reply Last reply Reply Quote 0
                • A
                  andyb last edited by

                  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

                  1 Reply Last reply Reply Quote 0
                  • H
                    Haba last edited by

                    cd /opt/iobroker

                    npm install iobroker.telegram –production

                    iobroker upload telegram

                    iobroker restart

                    1 Reply Last reply Reply Quote 0
                    • frankjoke
                      frankjoke last edited by

                      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 webhook

                      Hab's auf 2 Rechnern probiert, immer das gleiche.

                      1 Reply Last reply Reply Quote 0
                      • L
                        looxer01 last edited by

                        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
                        1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 last edited by

                          Sicher das nur ein Prozess vom Adapter nläuft?

                          Konsole ps auxww|grep telegram

                          1 Reply Last reply Reply Quote 0
                          • L
                            looxer01 last edited by

                            @apollon77:

                            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

                            1 Reply Last reply Reply Quote 0
                            • apollon77
                              apollon77 last edited by

                              Ne, du siehst nur das grep selbst, da läuft gar kein adapterprozess gerade …

                              1 Reply Last reply Reply Quote 0
                              • L
                                looxer01 last edited by

                                @apollon77:

                                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: 😄

                                vG Looxer

                                1 Reply Last reply Reply Quote 0
                                • S
                                  Superdad last edited by

                                  @looxer01

                                  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

                                  1 Reply Last reply Reply Quote 0
                                  • L
                                    looxer01 last edited by

                                    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

                                    1 Reply Last reply Reply Quote 0
                                    • D
                                      derrapf last edited by

                                      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:6379

                                      Gruss Ralf

                                      mania25 created this issue in yagop/node-telegram-bot-api

                                      closed Error: cannot enable cancellation after promises are in use #319

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        derrapf last edited by

                                        Hat keiner eine Lösung?

                                        Was kann ich noch tun um zu helfen?

                                        Gruss Ralf

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          derrapf last edited by

                                          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.

                                          chrira2507 1 Reply Last reply Reply Quote 0
                                          • chrira2507
                                            chrira2507 @derrapf last edited by

                                            @derrapf hatte das selbe Problem, neuer Bot + Token und alles funktioniert wider. Danke für Deinen Post

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            721
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            10
                                            22
                                            6517
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo