This is killing me...
I've tried everything I can think of, but Icecast still crashes if I define
more than 10 listen-socket ports. Is there a limit that's not documented or
is this a bug? I'm using the latest Windows build that OddSock compiled.
Thanks for any help/ideas
Fred
-----Original Message-----
From: Fred Black [mailto:fred@batanga.com]
Sent: Tuesday, July 19, 2005 1:32 PM
To: 'icecast'
Subject: RE: [Icecast] relaying IceCast from ShoutCast
Well, I've hit another problem:
Icecast crashes if I define more than 10 listen-socket ports.
I have 44 streams that I'm trying to relay via Icecast. It works just fine
until I try to add the listen-socket port definitions. If I put the 11th
one in, it will crash on startup without entering anything in the log files
(log level on 4).
I've use sysinternal tcpView to verify that the ports I'm trying to use
are
open and they are.
Any ideas anyone????
Fred
-----Original Message-----
From: Fred Black [mailto:fred@batanga.com]
Sent: Tuesday, July 19, 2005 11:17 AM
To: 'icecast'
Subject: RE: [Icecast] relaying IceCast from ShoutCast
Ok,
Found the issue,
I needed to specify another listen-socket for the port I specified in the
alias section.
The alias works now, AND, I successfully relayed it to Shoutcast!
<listen-socket>
<port>8000</port>
</listen-socket>
<listen-socket>
<port>8010</port>
</listen-socket>
<paths>
..
..
<alias port="8010" source="/"
dest="/Jazz"/>
</paths>
Thanks
Fred
-----Original Message-----
From: Fred Black [mailto:fred@batanga.com]
Sent: Tuesday, July 19, 2005 10:53 AM
To: 'icecast'
Subject: RE: [Icecast] relaying IceCast from ShoutCast
Mike,
I had tried it without the bind-address first and no luck. I took it back
out and still no luck.
I can listen to the stream by using http://38.116.36.8:8000/Jazz, but can
not get to the alias with http://38.116.36.8:8010
Fred
-----Original Message-----
From: Michael Smith [mailto:mlrsmith@gmail.com]
Sent: Tuesday, July 19, 2005 10:36 AM
To: Fred Black
Cc: icecast
Subject: Re: [Icecast] relaying IceCast from ShoutCast
On 7/19/05, Fred Black <fred@batanga.com> wrote:> I Found some old posts with some syntax for this, but it does not
> appear to work. Should this work in the Windows version?
>
> Here's the line from the Path section of my config file:
> <alias bind-address="38.116.36.8" port="8010"
source="/"
> dest="/Jazz"/>
It's extremely unlikely that you want to use the bind-address attribute. If
you do, you'll know precisely why. If you don't know exactly what it
does,
then you don't need it - it's only for certain configurations on complex
systems with multiple network interfaces.
With the port attribute set, this _should_ work in all versions.
Mike
On 7/20/05, Fred Black <fred@batanga.com> wrote:> This is killing me... > I've tried everything I can think of, but Icecast still crashes if I define > more than 10 listen-socket ports. Is there a limit that's not documented or > is this a bug? I'm using the latest Windows build that OddSock compiled.It's a hardcoded limit (MAX_LISTEN_SOCKETS in the source) which is easily changed. However, could you please file a bug report (http://bugs.xiph.org) about the crash? It should just be refusing to read any further listen-socket definitions, rather than crashing. Mike
On Wed, 2005-07-20 at 14:33, Fred Black wrote:> This is killing me... > I've tried everything I can think of, but Icecast still crashes if I define > more than 10 listen-socket ports. Is there a limit that's not documented or > is this a bug? I'm using the latest Windows build that OddSock compiled. > > Thanks for any help/ideasThere is a fixed compile limit of 10 listen sockets, but obviously icecast should not crash so there is a bug somewhere #define MAX_LISTEN_SOCKETS 10 That can be increased but that would need recompiling, what would be a reasonable limit and do you need so many ports to listen on? karl.
On 20 Jul 2005 14:53:10 +0100, Karl Heyes <karl@xiph.org> wrote:> On Wed, 2005-07-20 at 14:33, Fred Black wrote: > > This is killing me... > > I've tried everything I can think of, but Icecast still crashes if I define > > more than 10 listen-socket ports. Is there a limit that's not documented or > > is this a bug? I'm using the latest Windows build that OddSock compiled. > > > > Thanks for any help/ideas > > There is a fixed compile limit of 10 listen sockets, but obviously > icecast should not crash so there is a bug somewhere > > #define MAX_LISTEN_SOCKETS 10 > > That can be increased but that would need recompiling, what would be a > reasonable limit and do you need so many ports to listen on?In fact, it could fairly easily be made dynamic, rather than having this sort of static limit. The bug is pretty obvious, see _parse_listen_socket() in cfgfile.c. If you did make it dynamic, it'd likely be a good idea to make connection.c:wait_for_serversock() not reallocate the entire poll or select structures on every call, as that would get pretty inefficient at several hundred sockets. But that's not really a big deal. Mike
Thanks, I filed the bug report. I think we've come up with a work around for now that will allow me to work. We have 22 stations, each with a lower quality signal with ads and a higher quality signal without ads (44 streams). These stations are generated on 6 "radio servers" that have 8 stations 4 x 2(high + low quality). I only generated mp3 streams for the lower quality streams. Most of our listeners connect using Windows Media to our cluster of three Windows Media Servers. I have also setup three servers to distribute the MP3 streams and this is where I was setting up Icecast. I also have the need to have shoutcast so that's why I wanted to relay from Icecast to Shoutcast (vs. setting up another set of encoders on each of the "radio" servers). So on each of the three MP3 servers, I need to define 22 listen-socket ports for Icecast aliases to relay to shoutcast: this is when I hit this problem. However for now, I'm going to move Icecast back to the "radio" servers and then relay Icecast from there to Icecast on the MP3 servers, defining the port alisaes on each of the "radio" servers will keep the number under 10. Thanks, Fred -----Original Message----- From: Michael Smith [mailto:mlrsmith@gmail.com] Sent: Wednesday, July 20, 2005 9:49 AM To: Fred Black Cc: icecast Subject: Re: [Icecast] relaying IceCast from ShoutCast On 7/20/05, Fred Black <fred@batanga.com> wrote:> This is killing me... > I've tried everything I can think of, but Icecast still crashes if I > define more than 10 listen-socket ports. Is there a limit that's not > documented or is this a bug? I'm using the latest Windows build thatOddSock compiled. It's a hardcoded limit (MAX_LISTEN_SOCKETS in the source) which is easily changed. However, could you please file a bug report (http://bugs.xiph.org) about the crash? It should just be refusing to read any further listen-socket definitions, rather than crashing. Mike