[Icecast-dev] Server does not kill dead source mounts
Paul Zaremba
pzaremba at gmail.com
Sun Apr 7 21:22:00 UTC 2024
Hi all,
I've been completely stymied by this, and am finally reaching out after
exhausting all other options short of digging through the code.
I'm running 2.4.4 with and without TLS on two separate ports. I find some
of my friends (who are using BUTT on Mac OSX) will drop their stream,
sometimes due to a network failure, or sometimes by manually pressing
"STOP" on their clients.
However, the mount point persists on the server, preventing them from
reconnecting until I manually either kill the source from the web UI, or
restart the server. We're using "dynamic" mounts, where the client
specifies the name of the mount. These are not preconfigured in the
icecast.xml file.
I ran an experiment last night, wondering if it was my network setup
(firewall/NAT/etc.) that's leaving these TLS connections stalled. So, I
installed BUTT locally on a mac here inside the LAN, and did a direct IP
connection to the server, using the non-TLS port. I pressed "stop" on
BUTT, but the source mount remains in the server admin UI, almost 24 hours
now since I stopped and shut down the BUTT app. So I think I can eliminate
TLS and/or my network setup.
I don't see much, if any mention of this doing Google searches.
Anyone have any idea? I have the source code, like I said, but haven't
gone digging into it yet to try to debug. I'm a fairly skilled C/C++ dev,
so that's my next step.
Regards,
-p
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20240407/a2e9bb98/attachment.htm>
More information about the Icecast-dev
mailing list