Icecast Streaming Media Server

Anonymous · Guest

Having trouble with sources getting dropped for seemingly no reason, which in turn, of course, drops the listeners. Here's an exerpt from what I am seeing in the error.log:

<snip>

[2007-04-02 23:30:09] INFO source/source_main listener count on /truth103_high.mp3 now 1
[2007-04-02 23:30:38] INFO connection/_handle_source_request Source logging in at mountpoint "/truth103_low.mp3"
[2007-04-02 23:30:38] WARN connection/_handle_source_request Mountpoint /truth103_low.mp3 in use
[2007-04-02 23:31:53] INFO connection/_handle_source_request Source logging in at mountpoint "/truth103_low.mp3"
[2007-04-02 23:31:53] WARN connection/_handle_source_request Mountpoint /truth103_low.mp3 in use
[2007-04-02 23:33:08] INFO connection/_handle_source_request Source logging in at mountpoint "/truth103_low.mp3"
[2007-04-02 23:33:08] WARN connection/_handle_source_request Mountpoint /truth103_low.mp3 in use
[2007-04-02 23:34:23] INFO connection/_handle_source_request Source logging in at mountpoint "/truth103_low.mp3"
[2007-04-02 23:34:23] WARN connection/_handle_source_request Mountpoint /truth103_low.mp3 in use
[2007-04-02 23:35:38] INFO connection/_handle_source_request Source logging in at mountpoint "/truth103_low.mp3"
[2007-04-02 23:35:38] WARN connection/_handle_source_request Mountpoint /truth103_low.mp3 in use
[2007-04-02 23:35:53] INFO connection/_handle_source_request Source logging in at mountpoint "/truth103_low.mp3"
[2007-04-02 23:35:53] WARN connection/_handle_source_request Mountpoint /truth103_low.mp3 in use
[2007-04-02 23:35:59] WARN source/get_next_buffer Disconnecting source due to socket timeout
[2007-04-02 23:35:59] INFO source/source_shutdown Source "/truth103_low.mp3" exiting
[2007-04-02 23:35:59] WARN source/get_next_buffer Disconnecting source due to socket timeout
[2007-04-02 23:35:59] INFO source/source_shutdown Source "/truth103_high.mp3" exiting

</snip>

The source then reconnects about 15 seconds later when the encoder (SimpleCast) retries. It will stay connected for about 5-10 minutes, and then this whole thing starts over again.

I'm confused, because while I realize it looks like the source client is falling behind and Icecast is simply terminating the connection due to timeout, I don't understand why it is generating "mount point is in use" errors.

The system is running Novell Suse 10.1 out of the box, Apache is disabled and Icecast is answering on port 80. The machine is a dual-xeon 2.4GHz box with 4GB of RAM and a 3ware RAID 1 on a pair of 300GB drives. Bandwidth (shouldn't) be an issue, as the box is located at a co-location facility with a full 100mbps pipe run to it.

Ideas?

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

The 'in use' messages are because something is already connected using that mountpoint. Icecast does not allow multiple source client connections to the same mountpoint.

karl.

Anonymous · Guest

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

I can't comment on the exact issue as there's little info to go on, you don't have level 4 data and you haven't shown what data is on the NIC or what is logged on the access log.

One encoder (with mountpoint /truth103_low.mp3) disconnects at 23:35:59 (it's unknown when it initially connected), the second encoder is just getting rejected because of the mountpoint clash. This behaviour is normal. The source timeout (assuming it's 10 secs) is the thing you need to investigate. That indicates that either your source client is stalling or data is not getting to icecast, either way, 10 seconds is a very large amount of time for icecast to not receive any stream data.

karl.