Skip to content

CLOSE_WAIT leak in ProxyBackward #204

@thatsdone

Description

@thatsdone

Hi,
I'm using Backward proxy mode, and I noticed the mode has CLOSE_WAIT leak after fixing #179 locally.

First of all, after starting 2 pproxy services following the manual, one as backward mode, eventually I see
bunch of errors in the public proxy side.

socket.accept() out of system resource
socket: <asyncio.TransportSocket fd=8, family=2, type=1, proto=6, laddr=('0.0.0.0', 8081)>
Traceback (most recent call last):
  File "/usr/lib/python3.12/asyncio/selector_events.py", line 178, in _accept_connection
  File "/usr/lib/python3.12/socket.py", line 295, in accept
OSError: [Errno 24] Too many open files

I noticed that number of CLOSE_WAIT status socket increases monotonically in the public proxy side
and this is the problem of the above error.

I'm setting up my proxy pair like below.

  • public proxy
pproxy -l http://:8080 -r http+in://:8081 -v
  • behind firewall proxy
 pproxy -l http+in://IP_ADDRESS_OF_THE_PUBLIC_PROXY:8081/ -v

Regards

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions