TimedOut on get_updates #802

misha-antonenko · 2017-08-16T11:21:49Z

Calling get_updates consistently crashes the bot with telegram.error.TimedOut: Timed out .

The code:

updates = self.bot.get_updates(
    offset=self.update_id,
    timeout=30,
    network_delay=1.0
)

The log:

Traceback (most recent call last):
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 402, in _make_request
    six.raise_from(e, None)
  File "<string>", line 2, in raise_from
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 398, in _make_request
    httplib_response = conn.getresponse()
  File "/app/.heroku/python/lib/python3.6/http/client.py", line 1331, in getresponse
    response.begin()
  File "/app/.heroku/python/lib/python3.6/http/client.py", line 297, in begin
    version, status, reason = self._read_status()
  File "/app/.heroku/python/lib/python3.6/http/client.py", line 258, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/app/.heroku/python/lib/python3.6/socket.py", line 586, in readinto
    return self._sock.recv_into(b)
  File "/app/.heroku/python/lib/python3.6/ssl.py", line 1002, in recv_into
    return self.read(nbytes, buffer)
  File "/app/.heroku/python/lib/python3.6/ssl.py", line 865, in read
    return self._sslobj.read(len, buffer)
  File "/app/.heroku/python/lib/python3.6/ssl.py", line 625, in read
    v = self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/utils/request.py", line 174, in _request_wrapper
    resp = self._con_pool.request(*args, **kwargs)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/request.py", line 70, in request
    **urlopen_kw)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/request.py", line 148, in request_encode_body
    return self.urlopen(method, url, **extra_kw)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/poolmanager.py", line 244, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 666, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/util/retry.py", line 347, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/packages/six.py", line 686, in reraise
    raise value
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 617, in urlopen
    chunked=chunked)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 405, in _make_request
    exc_cls=ReadTimeoutError)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 321, in _raise_timeout
    raise exc_cls(*args)
telegram.vendor.ptb_urllib3.urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='api.telegram.org', port=443): Read timed out. (read timeout=31.0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/myapp/bot.py", line 81, in update_forever
    network_delay=1.0
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/bot.py", line 52, in decorator
    result = func(self, *args, **kwargs)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/bot.py", line 1392, in get_updates
    result = self._request.post(url, data, timeout=float(read_latency) + float(timeout))
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/utils/request.py", line 252, in post
    **urlopen_kwargs)
  File "/app/.heroku/python/lib/python3.6/site-packages/telegram/utils/request.py", line 176, in _request_wrapper
    raise TimedOut()
telegram.error.TimedOut: Timed out

The text was updated successfully, but these errors were encountered:

mendiej · 2017-08-18T09:29:03Z

I encounter the same issue/error (socket.timeout). For getUpdates, timeout set to anything but 0 results in errors. They are way less frequent when leaving out the timeout parameter, but they still do occur.

jh0ker · 2017-09-21T19:12:45Z

FYI the network_delay parameter is deprecated (at least in the latest version), so instead you should be using the read_latency parameter. And perhaps choosing a higher value for this parameter could solve your issue?

Andreychik32 · 2017-10-08T12:35:12Z

I have the same issue. Changing the read_latency parameter seems to not do any work on this issue.

tsnoam · 2017-10-11T20:16:47Z

Hi,
I'm sorry for my very late response.
@levzhazeschi - the problem with long polling is that you might lose connection without the application even knowing it.
In order to debug network problems we must have much more data. The first things to check (but upon adding the data, more questions will probably rise):

Where do you host your bot? I see "heroku", but what region?
Followup to 1 - have you measured the latency towards api.telegram.org ?
Do you get the error you described immediately at the first get_updates attempt or after several successful iterations?
If after several iterations:
4.1. How many iterations until failure?
4.2 How long before failure?
To answer 4, and in general, please enable debug logging from ptb and upload logs with more context - before and after the failure.

sutyrin · 2017-12-16T17:04:11Z

Hey folks!

I've very affected by this. Is there a quickfix to just ignore these and silently reconnect, if needed?

Are patches welcome, eh? ;)

Shadowigor · 2018-01-23T18:56:37Z

Is there any progress on this? I can still reproduce this with the newest version, I start getting the errors after about 30 minutes of inactivity.

sobolevn · 2018-02-08T18:02:49Z

I also have this error.

Logerfo · 2018-02-08T18:18:02Z

I had this issue using heroku. The problem was that my Procfile started with web. I changed it to bot and worked like a charm!

TimedOut exception is an expected an normal event. To reduce noise and make things more "fluent" we now: - Make sure that we don't sleep after the timeout but rather retry immediately. - Log debug instead of error level. Fixes #802

tsnoam · 2018-02-18T14:03:20Z

Hi,
Please see the recently uploaded wiki article about network errors:
https://github.com/python-telegram-bot/python-telegram-bot/wiki/Handling-network-errors

I hope it will answer why a timeout is (unfortunately) an unavoidable condition and will give you some hints on how to fine tune your bot.

In addition, once PR #1007 will be merged, there will be a better handling of timeouts during get_updates (that merge should happen today).

TimedOut exception is an expected an normal event. To reduce noise and make things more "fluent" we now: - Make sure that we don't sleep after the timeout but rather retry immediately. - Log debug instead of error level. Fixes #802

yongman · 2018-04-29T10:30:03Z

I also have this problem.

Andreychik32 · 2018-04-29T10:32:12Z

@yongman, just update python-telegram-bot using this command:

pip install -U python-telegram-bot

yongman · 2018-04-29T10:41:47Z

@Andreychik32 ,Thanks for you reply.

I update the python-telegram-bot by pip3, but I also get the following errors.

2018-04-29 06:37:47,954 [Level 99]: ehforwarderbot.__main__ (__main__.init; __main__.py:87)
     Initializing master blueset.telegram...
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 402, in _make_request
    six.raise_from(e, None)
  File "<string>", line 2, in raise_from
  File "/usr/local/lib/python3.6/dist-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 398, in _make_request
    httplib_response = conn.getresponse()
  File "/usr/lib/python3.6/http/client.py", line 1331, in getresponse
    response.begin()
  File "/usr/lib/python3.6/http/client.py", line 297, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python3.6/http/client.py", line 258, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/usr/lib/python3.6/socket.py", line 586, in readinto
    return self._sock.recv_into(b)
  File "/usr/lib/python3.6/ssl.py", line 1009, in recv_into
    return self.read(nbytes, buffer)
  File "/usr/lib/python3.6/ssl.py", line 871, in read
    return self._sslobj.read(len, buffer)
  File "/usr/lib/python3.6/ssl.py", line 631, in read
    v = self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 617, in urlopen
    chunked=chunked)
  File "/usr/local/lib/python3.6/dist-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 405, in _make_request
    exc_cls=ReadTimeoutError)
  File "/usr/local/lib/python3.6/dist-packages/telegram/vendor/ptb_urllib3/urllib3/connectionpool.py", line 321, in _raise_timeout
    raise exc_cls(*args)
telegram.vendor.ptb_urllib3.urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='api.telegram.org', port=443): Read timed out. (read timeout=9)

During handling of the above exception, another exception occurred:

and the bot exit.

By the way, the network from my vps to api.telegram.org:443 seems good.

yongman · 2018-04-29T10:48:21Z

More to say, this error occur from today and bot cannot work as before.

Brawl345 · 2018-04-29T10:49:19Z

Telegram currently has a power outage: https://twitter.com/telegram/status/990474364108894209
Bots are not working atm in some regions.

yongman · 2018-04-29T10:55:25Z

@Brawl345 Thanks for your information.

It seems the telegram's problem, but the python-telegram-bot also have the bug if timeout exists?

tsnoam · 2018-04-29T18:26:39Z

@yongman
I invite you to join our users group where we have a vibrant community helping each other: https://telegram.me/pythontelegrambotgroup

As suggested in one of the earlier comments please make sure to read the wiki page: https://telegram.me/pythontelegrambotgroup

If you've identified an actual bug with the library please open a new issue instead of reviving an old one.

tsnoam · 2018-04-29T18:28:53Z

@yongman
Sorry, the proper link for the wiki article:
https://github.com/python-telegram-bot/python-telegram-bot/wiki/Handling-network-errors

tsnoam self-assigned this Oct 11, 2017

tsnoam added the pending reply label Oct 11, 2017

avbelyaev mentioned this issue Dec 18, 2017

на машине отвалился long-polling? YetAnotherTimeTracker/yatt#50

Closed

tsnoam mentioned this issue Feb 15, 2018

updater.py: Better handling of timeouts during getUpdates #1007

Merged

tsnoam closed this as completed Feb 18, 2018

python-telegram-bot locked as resolved and limited conversation to collaborators Apr 29, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TimedOut on get_updates #802

TimedOut on get_updates #802

misha-antonenko commented Aug 16, 2017

mendiej commented Aug 18, 2017

jh0ker commented Sep 21, 2017

Andreychik32 commented Oct 8, 2017

tsnoam commented Oct 11, 2017

sutyrin commented Dec 16, 2017

Shadowigor commented Jan 23, 2018

sobolevn commented Feb 8, 2018

Logerfo commented Feb 8, 2018

tsnoam commented Feb 18, 2018

yongman commented Apr 29, 2018

Andreychik32 commented Apr 29, 2018

yongman commented Apr 29, 2018

yongman commented Apr 29, 2018

Brawl345 commented Apr 29, 2018 •

edited

Loading

yongman commented Apr 29, 2018

tsnoam commented Apr 29, 2018

tsnoam commented Apr 29, 2018

TimedOut on get_updates #802

TimedOut on get_updates #802

Comments

misha-antonenko commented Aug 16, 2017

mendiej commented Aug 18, 2017

jh0ker commented Sep 21, 2017

Andreychik32 commented Oct 8, 2017

tsnoam commented Oct 11, 2017

sutyrin commented Dec 16, 2017

Shadowigor commented Jan 23, 2018

sobolevn commented Feb 8, 2018

Logerfo commented Feb 8, 2018

tsnoam commented Feb 18, 2018

yongman commented Apr 29, 2018

Andreychik32 commented Apr 29, 2018

yongman commented Apr 29, 2018

yongman commented Apr 29, 2018

Brawl345 commented Apr 29, 2018 • edited Loading

yongman commented Apr 29, 2018

tsnoam commented Apr 29, 2018

tsnoam commented Apr 29, 2018

Brawl345 commented Apr 29, 2018 •

edited

Loading