NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Sickbeard post-processing chokes Ultra 6
Hi everyone,
I have Sickbeard TPB alpha installed on my Ultra 6 running OS 6.1.4, as well as Transmission and Plex Media Server.
Sickbeard is the git version and is always up-to-date.
Everything works great until Sickbeard starts post-processing, which in my case is just moving the completed downloads to a correct folder.
It will process up to 20 items at best, and then my NAS just completely freezes.
I can't login via SSH anymore, can't open the web GUI no more, ... nothing.
Only thing I can do then is push the power button until the NAS powers off, and then boot it again.
That's obviously not a good thing.
I suspect Sickbeard eats all the RAM until nothing is left which causes the NAS to hang.
There seems to be no way however to prevent SB from doing that (no way to set a limit on memory usage).
The command free -m shows I have only about 10MB of RAM free from the 1GB that is in the NAS, but I realise this is normal behaviour as the OS will use the available RAM for caching. Actually only 36% of my RAM is in use when I only have Transmission running and nothing else:
Therefore I was wondering if it would help anything if I were to install 2GB of RAM in the Ultra 6.
Won't the 2GB be consumed by the OS just as well, leaving the undesired effect of SB causing the system to hang? Or will it likely solve my problem?
Transmission uses just 2% of CPU and about 2.5% of RAM on average, and system load averages look fine too with just Transmission running:
I can't launch Sickbeard at this moment to check the numbers when SB is active since I'm connected to my NAS over a VPN and wouldn't be able to push the button if things go awry again. Will update this post tonight when I'm back home.
Anyone else here having any issues running Sickbeard on their Ultra?
I have Sickbeard TPB alpha installed on my Ultra 6 running OS 6.1.4, as well as Transmission and Plex Media Server.
Sickbeard is the git version and is always up-to-date.
Everything works great until Sickbeard starts post-processing, which in my case is just moving the completed downloads to a correct folder.
It will process up to 20 items at best, and then my NAS just completely freezes.
I can't login via SSH anymore, can't open the web GUI no more, ... nothing.
Only thing I can do then is push the power button until the NAS powers off, and then boot it again.
That's obviously not a good thing.
I suspect Sickbeard eats all the RAM until nothing is left which causes the NAS to hang.
There seems to be no way however to prevent SB from doing that (no way to set a limit on memory usage).
The command free -m shows I have only about 10MB of RAM free from the 1GB that is in the NAS, but I realise this is normal behaviour as the OS will use the available RAM for caching. Actually only 36% of my RAM is in use when I only have Transmission running and nothing else:
root@megapinnemuts:~# free -m
total used free shared buffers cached
Mem: 985 955 30 0 0 598
-/+ buffers/cache: 356 629
Swap: 1023 0 1023
Therefore I was wondering if it would help anything if I were to install 2GB of RAM in the Ultra 6.
Won't the 2GB be consumed by the OS just as well, leaving the undesired effect of SB causing the system to hang? Or will it likely solve my problem?
Transmission uses just 2% of CPU and about 2.5% of RAM on average, and system load averages look fine too with just Transmission running:
top - 15:00:16 up 5:54, 1 user, load average: 0.22, 0.31, 0.33
Tasks: 173 total, 1 running, 172 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.2 us, 0.4 sy, 0.0 ni, 98.8 id, 0.4 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem: 1009592 total, 980876 used, 28716 free, 216 buffers
KiB Swap: 1047932 total, 0 used, 1047932 free, 615104 cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2219 root 19 -1 424m 33m 4440 S 1.0 3.4 1:24.58 readynasd
12137 guest 20 0 179m 27m 4248 S 1.0 2.7 5:08.94 transmission-da
23379 root 20 0 28448 1644 1172 R 0.3 0.2 0:00.29 top
1 root 20 0 45304 3896 1516 S 0.0 0.4 0:02.47 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.13 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.07 ksoftirqd/0
I can't launch Sickbeard at this moment to check the numbers when SB is active since I'm connected to my NAS over a VPN and wouldn't be able to push the button if things go awry again. Will update this post tonight when I'm back home.
Anyone else here having any issues running Sickbeard on their Ultra?
1 Reply
Replies have been turned off for this discussion
- Hmm, no responses yet on the RAM question.
However, I've been monitoring system load more closely in the mean time, and I've concluded that I don't have this problem anymore if I don't let Sickbeard start on system boot. When I boot my Ultra 6 with OS 6.1.4, system loads rise between 3.0 and 5.0 for a couple of minutes. It are the readynasd and java processes that start taxing the CPU heavily right after boot. After < 5 minutes, system load goes back to normal (0.3~0.5).
If I then start Sickbeard and there are a number of files (20~40) in the post-processing folder, system load skyrockets again up to 7.0 with CPU utilizations up to 200%, but the Ultra 6 doesn't freeze anymore. When post-processing is over, load drops back to a maximum of 0.8 with Transmission, Sickbeard, Couchpotato and Headphones all running simultaneously.
So my problem was clearly due to the combination of SB + readynasd & java overloading the Ultra 6 at boot. Solution = a simple script that monitors system load right after boot and that launches the other daemons when load has decreased back to normal values.
Still would like to know if adding more RAM would make sense though ;)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
