#732452 icecast2: Icecast 2.3.2 doesn't list all mount points

Package:
icecast2
Source:
icecast2
Description:
streaming media server
Submitter:
Roy Meulekamp
Date:
2022-07-19 04:21:03 UTC
Severity:
normal
#732452#5
Date:
2013-12-18 08:11:00 UTC
From:
To:
Dear Maintainer,

I have installed icecast2 on a Debian Wheezy server, which is used to 'proxy' some streams to the internal network. This all works fine.
However, it seems that I cannot list all the mount points that are configured on this server. Only mount points which have been used at least once are shown.

I have several relay configurations like this:
<relay>
        <server>hostname of source</server>
        <port>8000</port>
        <mount>/radio</mount>
        <local-mount>/radio</local-mount>
        <relay-shoutcast-metadata>1</relay-shoutcast-metadata>
	<on-demand>1</on-demand>
</relay>
These relay mount points do just work fine.

This problem is also described here: http://comments.gmane.org/gmane.comp.audio.icecast.general/8710
Icecast2 revision 15122 should have fixed this problem, see http://lists.xiph.org/pipermail/commits/2008-July/013869.html

I tried to fix it by editing some xsl files (removing conditionals), but that didn't seem to fix it.
#732452#10
Date:
2015-03-07 02:24:04 UTC
From:
To:
Hi Roy,
is this bug report still valid with Icecast 2.4.0?

Thank you!

Carlo
#732452#15
Date:
2015-03-11 09:30:37 UTC
From:
To:
Carlo Stemberger schreef op 07.03.2015 03:24:

Hi Carlo,

I'm not sure. I still have the Wheezy version (2.3.2-9+deb7u2). Would
you want me to try the backported version?

Best regards,

Roy
#732452#20
Date:
2015-03-11 13:35:43 UTC
From:
To:
Hi Roy,

2015-03-11 10:30 GMT+01:00 <debian.bugs@slimdesign.nl>:

Could you try to reproduce this bug by using a (virtual?) testing machine
with Jessie/Sid, please? It would be very useful.

Otherwise you could just use backports, but you should think hard before
upgrading your working machine.

Thank you!

Carlo
#732452#27
Date:
2022-07-19 04:09:14 UTC
From:
To:
close 732452
thanks

Howdy,

Since the problem is noted to be fixed upstream by the user reporting the bug
and various releases have happened since 2015, and with the inability to reach
the user reporting this bug, I am now closing it.

Please feel free to re-open if this bug still affects you, but appears to be fixed.


~Unit 193
Unit193 @ Libera
Unit193 @ OFTC