You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a client connects to shairport-sync and then eventually disconnects, the socket stays open and will eventually exhaust the nofiles limit on the system.
Here is how to trigger the issue (use lsof | grep shairport | wc -l to count the number of open files on the server).
telnet dodecaphonism 7000
Trying 10.1.25.10...
Connected to dodecaphonism.
Escape character is '^]'.
OPTIONS rtsp://localhost RTSP/1.0
RTSP/1.0 200 OK
Server: AirTunes/366.0
Public: ANNOUNCE, SETUP, RECORD, PAUSE, FLUSH, FLUSHBUFFERED, TEARDOWN, OPTIONS, POST, GET, PUT
TEARDOWN rtsp://localhost RTSP/1.0
RTSP/1.0 451 Unavailable
Server: AirTunes/366.0
Connection: close
^]
telnet>
This is what the state of the connections is shortly after quitting telnet:
Fix looks good to me. Tried running the latest development version and despite shairport being hammered by monitoring probes, number of open files stay constant. Thank you for looking into a somewhat esoteric issue and thank you very much for shairport in general.
What happened?
When a client connects to shairport-sync and then eventually disconnects, the socket stays open and will eventually exhaust the
nofiles
limit on the system.Here is how to trigger the issue (use
lsof | grep shairport | wc -l
to count the number of open files on the server).This is what the state of the connections is shortly after quitting telnet:
Expectation would be that once telnet disconnects the socket on the server side is closed as well.
Relevant log output
Configuration Information.
How did you install Shairport Sync?
Built from source
Check previous issues
The text was updated successfully, but these errors were encountered: