| View previous topic :: View next topic |
| Author |
Message |
aproache
Joined: 21 Nov 2009
Posts: 3
|
 Posted: Sat Nov 21, 2009 2:36 pm Post subject: Huge memory eating |
 |
|
Hi.
Last days we have a very strange problem: one of our icecasts eats 500-600 mb per 2 hours, so it just killed by system because of memory allocation failed.
Config:
| Code: |
<icecast>
<limits>
<clients>100000</clients>
<threadpool>5</threadpool>
<queue-size>65536</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>32768</burst-size>
</limits>
...
<fileserve>1</fileserve>
<paths>
<basedir>/radio/icecast-2.3.2</basedir>
<logdir>/tmp/log</logdir>
<webroot>/radio/icecast-2.3.2/web</webroot>
<adminroot>/radio/icecast-2.3.2/admin</adminroot>
<pidfile>/var/run/icecast/icecasthost.pid</pidfile>
<!-- Aliases: can also be used for simple redirections as well,
this example will redirect all requests for http://server:port/ to
the status page
-->
<alias source="/" dest="/index.html"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<loglevel>1</loglevel> <-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>5120</logsize>
</logging>
<security>
<changeowner>
<user>ice</user>
<group>ice</group>
</changeowner>
</security>
</icecast>
|
| Quote: |
[2009-11-20 16:22:50] WARN Memory allocation failed : xmlEncodeEntitiesReentrant: malloc failed
[2009-11-20 16:56:32] WARN Memory allocation failed : growing buffer
[2009-11-20 17:31:21] WARN Memory allocation failed : building text
[2009-11-20 17:31:21] WARN Memory allocation failed : building node
[2009-11-20 17:31:21] WARN Memory allocation failed : building node
[2009-11-20 17:31:21] WARN error
[2009-11-20 17:31:21] WARN xsltNewTransformContext: out of memory
|
It's starting with /usr/local/bin/icecast_host -b -c /home/config.xml &
How can we fix it? It's problem only of one server, on other 3 we haven't it. |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Sat Nov 21, 2009 2:53 pm Post subject: |
|
|
At log level 1 we won't see anything to determine what could cause the issue. I would try the current trunk code to see if that resolves the problem first
http://people.xiph.org/~brendan/snapshots/icecast/
karl. |
|
| Back to top |
|
|
aproache
Joined: 21 Nov 2009
Posts: 3
|
| Posted: Sat Nov 21, 2009 10:28 pm Post subject: |
|
|
Thnku!!!
The last trunk (21nov) is working great, currently 50mb stable. |
|
| Back to top |
|
|
aproache
Joined: 21 Nov 2009
Posts: 3
|
| Posted: Fri Feb 12, 2010 8:24 pm Post subject: |
|
|
the problem is not solved 
in 1 day icecast's eating about 1gb memory and being killed by system. |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Feb 12, 2010 9:59 pm Post subject: |
|
|
I've emailed you me current set of work for trunk (there is also my branch work at my website which you can also use), but it would be better to increase the log level to 4 so we can see what is going on in more detail.
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
