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
