Icecast Streaming Media Server

DJ-Zath · Last edited by DJ-Zath on Sun Feb 15, 2009 9:02 pm; edited 1 time in total

hello to everyone

I have read through the forums and couldn't find anything relating to my issues exactly, so I'll try it here.

But, first the technical details:

Server Host is a Gigabyte 8IPX-DREL with an Intel E-7501 chipset and 2 Dual-core Xeon CPUs

Unit has 2 Gigs RAM and a clock speed of 2.4 Ghz per CPU and a FSB of 512

Unit is mounted in a 1U Blade box and positioned at the Backbone interface (CoLo)

Unit is a dedicated machine for Icecast and is connected to a 300 mips fiber.

Unit runs FreeBSD 6.3 with a fresh install (not from upgrade) and is fully-secured.

Icecast is fully-compiled with all needed libraries as per the gcc package (make)

although Icecast was installed under "full" root, it was transferred to another account and
all perms and access were properlly configured.

Streaming Server: Icecast v2.3.2

Now the problems:

First problem:

I can NOT get any Icecast mount to accept a password from any icecast client.
this includes libshout/perl on localhost and/or oddcast from a remote box. logs simply show
"invalid or missing password - source rejected" no other errors are noticed or recorded.
I CAN get a shoutcast-configured mount to work just fine, but I would then need the ability to
run MORE than one shoutcast mount and the ability to fall back from one shoutcast mount to
another. this isn't possable with icecast (as far as I can tell)

Second problem:

when a relay mount is initiated, theres a long "delay" for the first connection
from a listener.. including fallback mounts and direct connections.. this delay remains for about
2 minutes, but not exact nor consistant.. first listener MUST remain on the mount for the delay
time entirely before the mount will switch online.. once connected, mount remains connected and
active and will switch immediately from there unless the source disconnects.. then the delay
happens again. if a listener does not remain connect for the entire 2 minutes then the next listener will have to.. etc etc etc.. needless to say, this is useless in the current state.

third problem:

this one is more of an issue than a problem.. I need to know HOW to "AUTH" into the admin page(s)
using a script- and NOT a browser.. I want a "bot" to log into the admin page to collect
information locally.. I can't get the AUTH to accept a single line script- only seems to REQUIRE
a interactive login. (a bot cann't enter an interactive login since its NOT GUI-based).

there you have it!
any help/suggestions would be helpful..

-DjZ-

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

without the xml it's guess work here.

first, If the message containing "... attempted to login with invalid or missing password" then is has to be down to the username/password not matching. some source clients don't allow a username other than "source" which is the global default in icecast but you may of changed it in the <mount>

Second, Is this an on-demand relay, so the first listener is triggering a relay connection. Is that relay connection attempt stalling and dropping to a fallback (the error log will be useful here).

Third, depends on the machanism you use but the admin pages use basic http auth so http://admin:pw@host:port/admin/listclients?.... is valid

karl.

DJ-Zath · Posted: Sat Feb 14, 2009 9:02 pm Post subject:

hi there Karl and thanks for your reply.. I didn't include the xml unless it was requested.. and so, here it is!

please note:

passwords/login names and paths are not actual
paths are common to one-another (example shown is /path/to/icecast)

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

you probably want to revisit some of those settings. 32 bytes is not much for a burst, likewise 128kbytes is not much for the maximum queue length

karl.

DJ-Zath · Posted: Sun Feb 15, 2009 3:21 am Post subject:

hi there buddy..

yeah, I know those values are low.. I run it close to realtime this is because the input feed is UDP.. Icecast runs at a 2 second latency.. this includes the remote DJ switch-ins.. noone reports any tearing or skipping.. but I shall adjust them just the same.. the idea is a 1/sec buffer or one sample in the buffer.. keeps things low-latency..

in case you wondered, I have already tried increasing (and decreasing) the values but it was no help or has no desernable effect..

again, thanks for the suggestions.. tommorrow I'll be looking into the http auth script for the bot..

-DjZ-