Icecast Streaming Media Server

rec91402 · Joined: 14 Nov 2009 Posts: 32

I have an icecast 2.3.2 server on CentOS 64bit which after some time will spawn additional instances of itself, and with this additional instances comes problems. Feeds will think they are online but are not actually playable... they may be connected to one of the instances, but not one which can play the feed.

What would be causing additional instances to be spawned?

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

icecast does not spawn itself, the nearest thing is the on-connect settings but those won't show as that. It's probably down to however icecast is started, maybe a loop or a regular check that believes icecast has died and starts another instance.

karl.

rec91402 · Joined: 14 Nov 2009 Posts: 32

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

is this 2.3.2 and if so where from, and lets see what is being created. When you see it again, do a ps -eLf | grep icecast and send that list to me, we'll do a trace to see which process is listening on the port and what the threads are doing.

karl.

rec91402 · Joined: 14 Nov 2009 Posts: 32

rec91402 · Joined: 14 Nov 2009 Posts: 32

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

do a netstat -tnlp | grep 8000 (assuming port 8000 is a listening port of icecast), that will tell us which process actually has the port.

If you are on linux then you can strace -o file1.txt -tt -p <id> where id is thread id (lwp) from the ps -eLf list. There's probably a few threads and we only need a couple of seconds to see what is happening on each. On linux, the pid of each icecast is unique but is shared amongst the threads.

karl.