Hi,

 

I have 4.5.2 installed and for the last few months, the server goes down every couple of weeks.

 

I finally captured some logs. Seems to me it runs out of memory and kills SMBD. Can someone look into this for me and let me know where the memory leak may be occuring.

 

I run the following packages:

 

unraid web

rtorrent

screen

unraid_notify

cache_firs

 

I have attached the log file. In this case it hapenned right after the mover of the cache ... but sometimes it happens for example when I want to move large files from explorer on my pc.

 

 

 

 

 

log.txt

Only you can tell...

 

Run this command now, then again in a day, see which process size is growing:

Displaying top 25 memory-consuming processes

ps aux | head -1; ps aux | sort -rn +3 | head -25

another version of the same, but showing "real" memory consumed:

ps vx | head -1; ps vx | grep -v PID | sort -rn +6 | head -25

 

Good luck.  My best guess will be the rtorrent process, but it will be interesting to see for sure.

I run cache_dirs all the time, and it uses a minimal amount of memory, but it will depend on how many files/directories you have it scanning.  On my server the biggest users are the smbd processes.

 

 

Joe L.

This post describes what to look for in the process listings and how to interpert memory usage:

http://mail.nl.linux.org/linux-mm/2003-03/msg00077.html

Thanks!

 

i'm going to keep an eye on this but i think you're right about rtorrent:

 

USER      PID %CPU %MEM    VSZ  RSS    TTY      STAT START  TIME COMMAND

root      9832  0.5      3.0  126720 62916 pts/0    Ss+  May28  25:29  /usr/bin/rtorre                                                            nt -n -o import=/boot/custom/etc/rtorrent.rc

 

Is that KB? so 126MB of memory is being used?

 

I'm going to lok at rtorrent if there is anything I can do to flush the memory every few days... maybe restart it ?

You might also want to take a look at the size of your in-memory filesystems [/] to see if it's growing beyond memory too, perhaps by something writing to the tmp or log dirs.

You might also want to take a look at the size of your in-memory filesystems [/] to see if it's growing beyond memory too, perhaps by something writing to the tmp or log dirs.

 

How would I check that?

 

 

Also, say it is rtorrent .... what can I do about it? I've been reading options in rtorrent, all i got so far was this; http://libtorrent.rakshasa.no/wiki/RTorrentPerformanceTuning (The first 2) but I doubt it has anything to do with the memory leak.

 

 

You might also want to take a look at the size of your in-memory filesystems [/] to see if it's growing beyond memory too, perhaps by something writing to the tmp or log dirs.

 

How would I check that?

 

 

Also, say it is rtorrent .... what can I do about it? I've been reading options in rtorrent, all i got so far was this; http://libtorrent.rakshasa.no/wiki/RTorrentPerformanceTuning (The first 2) but I doubt it has anything to do with the memory leak.

 

Either reboot more frequently, or get a newer version of rtorrent with the memory lean fixed.

Ok, that link i sent you with the buffer size won't do any good right? seems it has to do more about chunks...

 

 

I'm going to wait though and confirm it is in fact the memory leak.

 

Hi,

 

so an update on this. It doesn't seem to be "rtorrent" the culprit as I notice it's been steady at anywhere between 125Mb to 150MB, (it fluctuates up and down between that range) it seems to just be everytime a torrent gets activated it goes up a bit and then back down when it's deactivated.

 

On the other hand, I noticed a thread open for the very same problem I am having;

 

http://lime-technology.com/forum/index.php?board=14.0

 

You see, I seem to recall that I lose connection to the server when:

 

A) I leave a terminal open by accident for a prolonged period of time

 

or

 

B) From my windows machine I attempt to copy/move a file from one share to another (not through a terminal).