Icecast Streaming Media Server

[DJ-Zath]

hello everyone and Happy holidays to you all! I hope everyone is having a nice holiday season...

At first, I thought everything was Okay... but I started noticing a strange behavior with the entire server.. it STALLS!

The stalls last a few seconds in duration and happen randomly... after going through everything, I found the problem is happening when a client logs into Icecast!

While Icecast is handshaking a client, other connections on the whole box, icecast-related or not, all become completely unresponsive for that brief moment in time.. this includes chat, web, ssl.. everything.

At first, I thought it might be my ISP doing something funny with "concurrent connection limits" at the CO (might still be??) but now, I'm not too sure... (I will be calling them this morning to ask about this)

I CAN re-create the condition by simply playing a stream and then have another client attempt login.. all the other connections will freeze during that brief moment- do enough of these, and things start timing out!

This same condition exists if I have a client attempt login to a mount that has no stream on it.. all other mounts become unresponsive- along with the rest of the box.. in this example, the box remains unresponsive untill the client connection times out FIRST and then things return back to normal (untill the next connection attempt, that is).

I have noticed this "cropping up" while the in-studio receiver was attempting cxonnection to the input mounts (when no guest DJ is present) and the box acts like its under heavy load with blips and stalls throughout.. and the chat server missing much of the chats!

Shut down Icecast; and the box returns to normal.

(running 'top' reveals the box is not dropping under 95% idle The box is a dedicated 4-CPU Xeon with 2 Gigs RAM running FreeBSD 6x)

I would have noticed this condition before- and think it may have started since installing the trunk.. however, simply putting the old icecast exec may not solve it.. (this assumes that the trunk installed new version of other things.. and the other things might be the cause).

at the time of this writing, I have not yet attempted a re-install of the orginal version of Icecast.. I have merely put back the old exec file (yes I saved the new one as well- I can swap them as much as needed)

before I do that, I'd thought I'd run it pass all of you (and the master, Karl) first.
_________________
-DjZ-

[karlH]

I'm not aware of any busy loop behaviour with trunk. You should be able to run the trunk in parallel (different port/logs) with your existing icecast and run it in truss or similar utility to see if there are busy calls being made.

karl.