QUERY · ISSUE

ESP32: Socket.listen(backlog) leads to OSError: 112

openby mrwhy-origopened 2020-02-08updated 2020-02-11

port-esp32

Currently I'm trying to listen to a socket. My setup is utilizing uasyncio.

But the same error is happening with plain use of sockets as well.

I'm building the master branch with EspIDF 3.3.1

import usocket as _socket
ai = _socket.getaddrinfo("0.0.0.0", 80, 0, _socket.SOCK_STREAM)
ai = ai[0]
s = _socket.socket(ai[0], ai[1], ai[2])
s.setblocking(False)
s.setsockopt(_socket.SOL_SOCKET, _socket.SO_REUSEADDR, 1)
s.bind(ai[-1])
s.listen(10)

Edit:
Just finished tests with ESP IDF 4 --> Same problem.

CANDIDATE · ISSUE

esp8266: listen()/accept() broken?

closedby roger-opened 2015-05-07updated 2015-07-03

ports

I'm testing the following server script:

import esp

esp.connect('xxx', 'xxx')  

s = esp.socket()

def on_connect(sock):
    print(s.accept()) 

s.bind(('', 80))
s.onconnect(on_connect)
s.listen(5)

But get a OSError: not listening everytime I connect. Seems like something is broken?

Assessment

Q Qwen · high

Both issues concern socket.listen() functionality on ESP-based ports (ESP32 vs ESP8266), but they report different errors and symptoms. Issue #5624 reports OSError: 112 (ENOSPC - no space left on device) on ESP32 when calling listen() on a non-blocking socket. Issue #1237 reports OSError: 'not listening' on ESP8266 when calling accept() after listen(). These are different error codes, different ports, and potentially different root causes. While they share the same general topic (socket listen/accept issues on ESP ports), they do not describe the same underlying problem and one does not resolve the other.

Suggested action

Keep both issues open as they address different bugs. The maintainer may want to review if there's a common underlying issue in the socket implementation across ESP ports, but they should be tracked separately.

ESP32: Socket.listen(backlog) leads to OSError: 112

esp8266: listen()/accept() broken?

Keyboard