RuntimeError: File descriptor 2877 is used by transport <TCPTransport closed=False reading=True 0x55b8dc9baa90>
In our service we had aiohttp==3.8.5 and upgraded aiohttp to 3.10.5 version. That is all. In production now we have issues like issue below. Maybe i should to write issue to another libs, tell me about it if so, or maybe you have your own fix then tell me uvloop version i need to upgrade in my service.
traceback:
RuntimeError: File descriptor 2877 is used by transport <TCPTransport closed=False reading=True 0x55b8dc9baa90>
File "our_service/app/client.py", line 204, in get_recommendations
async with self._session.get(
File "aiohttp/client.py", line 1353, in __aenter__
self._resp = await self._coro
File "aiohttp/client.py", line 657, in _request
conn = await self._connector.connect(
File "aiohttp/connector.py", line 564, in connect
proto = await self._create_connection(req, traces, timeout)
File "aiohttp/connector.py", line 975, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "aiohttp/connector.py", line 1319, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "aiohttp/connector.py", line 1073, in _wrap_create_connection
sock = await aiohappyeyeballs.start_connection(
File "aiohappyeyeballs/impl.py", line 104, in start_connection
raise first_exception
File "aiohappyeyeballs/impl.py", line 82, in start_connection
sock = await _connect_sock(
File "aiohappyeyeballs/impl.py", line 174, in _connect_sock
await loop.sock_connect(sock, address)
File "uvloop/loop.pyx", line 2631, in sock_connect
fut = self._sock_connect(sock, address)
File "uvloop/loop.pyx", line 1089, in uvloop.loop.Loop._sock_connect
self._add_writer(sock, handle)
File "uvloop/loop.pyx", line 837, in uvloop.loop.Loop._add_writer
self._ensure_fd_no_transport(fd)
File "uvloop/loop.pyx", line 764, in uvloop.loop.Loop._ensure_fd_no_transport
raise RuntimeError(
python version: Python 3.10.15
os info: PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian
other installed libs: aiohttp==3.10.5 aiohttp_traversal==0.11.0 aiojobs==1.2.0 asyncpg==0.29.0 orjson==3.9.10 uvloop==0.19.0 yarl==1.12.1
I have also encountered this issue when upgrading from aiohttp 3.9.5 -> 3.11.11.
I was able to reproduce with this test script (gist) on Ubuntu 24 x86.
After some experimentation I found that https://github.com/aio-libs/aiohttp/pull/10464 resolved the issue for my test script... however it does feel like there's something funny on uvloop's side here, in that when an exception is thrown on this line:
https://github.com/MagicStack/uvloop/blob/7bb12a174884b2ec8b3162a08564e5fb8a5c6b39/uvloop/loop.pyx#L2066
then it is possible for the transport to linger on in
https://github.com/MagicStack/uvloop/blob/7bb12a174884b2ec8b3162a08564e5fb8a5c6b39/uvloop/loop.pyx#L150
despite the file descriptor being relinquished to the OS.
Also, it looks like https://github.com/MagicStack/uvloop/pull/646 would be a uvloop-side fix for this issue.