Icecast Streaming Media Server

[Enforcer]

Hello there.

I run icecast2, but in 7-9 hours the icecast2 is down with error in syslog (Debian 5):
Jan 6 13:28:49 vm1094 kernel: [172302.179048] Out of memory: kill process 13785 (icecast2) score 30376 or a child
Jan 6 13:28:49 vm1094 kernel: [172302.180207] Killed process 13785 (icecast2)

And now I am watching TOP in ssh. Free memory is slowly down. Icecast2 process takes 60% of memory. In 1 hour 70%. In a while - 80%. And so on.

What is going on? How can I fix this?

Allowed memory on VDS is 288 MB total. There is only icecast2. No www. But apache and mysql are installed. After all is about 220 MB free left.

Number of listener is 10 maximum at time. But usually it is 3-5.
Memory doesnt free itselft. Maybe I should run some script in cron?

Please, help!

[karlH]

which version of icecast is this?, 2.3.2 is the latest release code.

karl.

[Enforcer]

Icecast 2.3.2

[karlH]

You'll have to let me know the specifics of your icecast setup. If you have hundreds of streams or huge queues then those will use up memory but icecast should not be seeing a steady increase in memory usage to the point that the OOM killer is triggered. You could use the trunk code as well.

karl.

[Enforcer]

There are only 2 relay from the one radio station! That's it.
And the script that display in my www:
1. current song
2. number of listener
of both relay



When I "killall icecast2" the memory free again!
See below:

[karlH]

You didn't say what your queue sizes are, but assuming those are not silly then can you try the same again with trunk either from svn or http://people.xiph.org/~brendan/snapshots/icecast

karl.

[Enforcer]

Queue size is 524288.
Mayby I should set it less than 288 mb of ram? For example, set to 150000?

icecast.xml:

<limits>
<clients>100</clients>
<sources>5</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>

<burst-on-connect>1</burst-on-connect>

<burst-size>65535</burst-size>
</limits>


http://people.xiph.org/~brendan/snapshots/icecast
What shell I do with that? Just install (make && make install) and run as a process?

[karlH]

512k is fine for a queue size. yes the tarball works just the same as the normal release tarball.

karl.

[Enforcer]

So, should I install icecast trunk and use it? Or what to do?

I need the most easy way to fix my problem.
Thanks.

[karlH]

yes try the trunk code, see if there is any memory issue relating to that because that is what will be altered if required. There has already been a number of updates to 2.3.2 already and your problem may already be fixed.

karl.

[Enforcer]

I'm very grateful for help. Icecast-trunk works well for now. Using about 1% of MEM.

But I can't modify xsl - /web/status.xsl
Changes are not apply and display the default page.
However if I remove status.xsl then get "Could not parse XSLT file".
It means I'm changing right file.

Shall I restart icecast server?

My icecast.xml:

<paths>
<basedir>/home/icecast</basedir>
<logdir>/home/icecast/logs</logdir>
<webroot>/home/icecast/web</webroot>
<adminroot>/home/icecast/admin</adminroot>
<alias source="/" dest="/status.xsl"/>
</paths>

[karlH]

I'd have to check that specific usage, I don't think that particular path has been changed, but your log should report where the xsl file is being read or not. obviously is there is an xslt parse error then that could be an issue.

karl.

[Enforcer]

The new xsl file works well now. It begin to work in a few hours.

[cmodyssey]

Hi,

I take it the changes that are in the trunk code that resolve known memory issue(s) will be included in version 2.3.3?

When is version 2.3.3 due to be released?

Thanks,

Richard.

[karlH]

When ready, the trunk code will be tagged as 2.3.3. I'm not sure when to do that just yet, I do have a couple of smaller changes lined up but no change in functionality unless people start screaming. I don't think there's any reports of crash related issues with trunk

karl.