windkh/node-red-contrib-telegrambot

getting a polling error: aggregate error

mildly2late opened this issue · 7 comments

mildly2late commented

Hi im getting this error when deploy my telegram bot, has anyone seen this before? ive used this package for multiple computers and its the first time im encountering this

Unhandled rejection RequestError: AggregateError
at new RequestError (C:\Users\USER\node_modules\request-promise-core\lib\errors.js:14:15)
at plumbing.callback (C:\Users\USER\node_modules\request-promise-core\lib\plumbing.js:87:29)
at Request.RP$callback [as _callback] (C:\Users\USER\node_modules\request-promise-core\lib\plumbing.js:46:31)
at self.callback (C:\Users\USER\node_modules\request\request.js:185:22)
at Request.emit (node:events:514:28)
at Request.onRequestError (C:\Users\USER\node_modules\request\request.js:877:8)
at ClientRequest.emit (node:events:514:28)
at TLSSocket.socketErrorListener (node:_http_client:495:9)
at TLSSocket.emit (node:events:514:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

windkh commented

I guess I remember having seen a similar thing when connection was lost or rejected due to network failure. Not 100% sure

mildly2late commented

thanks for the reply, i tried running on a test PC in the same network before-hand and seems to be fine. just hoping that i dont have to swap out the whole thing

E1cid commented

Seeing similar issue since update to 15.1.9

Unhandled rejection Error: ETELEGRAM: 409 Conflict: terminated by other getUpdates request; make sure that only one bot instance is running
    at /data/data/com.termux/files/home/.node-red/node_modules/node-telegram-bot-api/src/telegram.js:299:15
    at tryCatcher (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/async.js:102:5)
    at Async.drainQueues [as _onImmediate] (/data/data/com.termux/files/home/.node-red/node_modules/bluebird/js/release/async.js:15:14)
    at process.processImmediate (node:internal/timers:478:21)

If i turn poling off in config the error stops

windkh commented

This indicates that you used the same token in several places. The server does not like if the messages are polled by two parties

windkh commented

please try with new version 16.0.0

duycop commented

node-red-contrib-telegrambot
version: 16.0.1

  • node "receiver" polling -> error -> polling ->error : loop forever
  • node "sender" => getting a error: **EFATAL: AggregateError**
windkh commented

@duycop can you reproduce it?