Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BlockingIOError: [Errno 35] Resource temporarily unavailable #61

Closed
chabanovsky opened this issue Apr 29, 2017 · 4 comments
Closed

BlockingIOError: [Errno 35] Resource temporarily unavailable #61

chabanovsky opened this issue Apr 29, 2017 · 4 comments

Comments

@chabanovsky
Copy link

After the last update from the upstream I get the following error each time (as I understand) when I lose an internet connection (for example, a pc goes to hibernate mode and back or a router reassigns an IP–address). After the exception the app stop receiving updates.

Exception in thread UpdatesThread:
Traceback (most recent call last):
  File "/development/Telethon/telethon/network/tcp_client.py", line 80, in read
    partial = self.socket.recv(left_count)
BlockingIOError: [Errno 35] Resource temporarily unavailable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/development/Telethon/telethon/network/mtproto_sender.py", line 429, in updates_thread_method
    seq, body = self.transport.receive(timeout)
  File "/development/Telethon/telethon/network/tcp_transport.py", line 40, in receive
    packet_length_bytes = self.tcp_client.read(4, timeout)
  File "/development/Telethon/telethon/network/tcp_client.py", line 92, in read
    'The read operation exceeded the timeout.')
TimeoutError: The read operation exceeded the timeout.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/development/Telethon/telethon/network/tcp_client.py", line 80, in read
    partial = self.socket.recv(left_count)
BlockingIOError: [Errno 35] Resource temporarily unavailable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/development/Telethon/telethon/network/mtproto_sender.py", line 444, in updates_thread_method
    self.receive(r)
  File "/development/Telethon/telethon/network/mtproto_sender.py", line 135, in receive
    seq, body = self.transport.receive(timeout)
  File "/development/Telethon/telethon/network/tcp_transport.py", line 40, in receive
    packet_length_bytes = self.tcp_client.read(4, timeout)
  File "/development/Telethon/telethon/network/tcp_client.py", line 92, in read
    'The read operation exceeded the timeout.')
TimeoutError: The read operation exceeded the timeout
@Lonami
Copy link
Member

Lonami commented Apr 29, 2017

Well this also happened on #47 so maybe if this happens I should try disconnect and then reconnecting?

@Lonami
Copy link
Member

Lonami commented Apr 29, 2017

I'm not sure if this will work, but at least it's worth a try.

@Lonami
Copy link
Member

Lonami commented May 30, 2017

Those timeouts are probably related to #94 @chabanovsky. Can you please test the upstream version too?

@Lonami Lonami added the waiting-for-submitter This issue may have been solved already label Jun 2, 2017
@Lonami Lonami removed the waiting-for-submitter This issue may have been solved already label Jul 22, 2017
@Lonami
Copy link
Member

Lonami commented Jul 22, 2017

There are a few newer issues also mentioning both Errno 35 and Errno11 (causing TimeoutError). Discussion has been moved there. Also, check your system time and the wiki front page.

@Lonami Lonami closed this as completed Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants