February 21, 201115 yr YEP! Midnight Commander showed all lines had ^M at the end. I removed them, saved the files, and both Stop and Start function as intended. Thanks Peter.
February 22, 201115 yr Anyone jumped the 0.6 beta 2 bandwagon? I copied it to the usb stick in a separate folder and copied over the sabnzbd.ini file from my 0.5.5 installation. Downloading works fine, but the queue shows empty, while items do show up in history when finished. Any ideas?
February 22, 201115 yr I haven't tried it. I'm running 0.5.6 and it's been working great with no issues so I really have no great desire to upgrade. Peter
February 22, 201115 yr I haven't tried it. I'm running 0.5.6 and it's been working great with no issues so I really have no great desire to upgrade. Peter The reason I upgraded is that in the previous version (0.5.x) the log folder also contained the article cache. This meant that if I kept it on the cache disk, the disk would never spin down (because of the log file) and thus unRAID would never go to sleep. If I keep it on the USB stick, it will seriously add to the write cycles and eventually kill some memory cells.
February 23, 201115 yr I have been running CouchPotato so there is no chance my cache drive will spin down anyways. different goals I see. Peter
February 23, 201115 yr The reason I upgraded is that in the previous version (0.5.x) the log folder also contained the article cache. This meant that if I kept it on the cache disk, the disk would never spin down (because of the log file) and thus unRAID would never go to sleep. If I keep it on the USB stick, it will seriously add to the write cycles and eventually kill some memory cells. Why not just point the log directory to the file system loaded in memory (i.e /var/log or /tmp/log)? If you follow my suggestions in the wiki, you should be able to get your cache drive to spin down, at least until the next episode search/SAB activity/page access/etc.
February 28, 201115 yr My cache drive won't unmount. This is how I attempt the process: 1) Shutdown SAB from the web interface 2) Click the Stop Python button in the User Scripts page 3) Open myMain 4) Spin down all drives (they do as such) 5) Click Stop Array (I was doing this from the unRAID link, so the array was not fully be stopped. Stopping the array from the Array Management page will kill all processes, no matter if data corruption occurs or not) I was careful to stop both the SAB program and Python before clicking Stop from the Array Management page. 6) Wait 7) The other five disks unmount and the unmounting label disappears after a few seconds, but the cache drive continues to show as unmounting. The most recent time this happened, the tower's web gui stopped loading. I ran /sbin/powerdown from Putty and it's now shutdown. I need for the Array to shutdown when asked to. Unnecessary parity checks are, well, unnecessary.
February 28, 201115 yr Are you running SickBeard or CouchPotato? Those will also keep your cache drive spinning. Terminal open? Anything?
February 28, 201115 yr Are you running SickBeard or CouchPotato? Those will also keep your cache drive spinning. Terminal open? Anything? Sick and Couch are never running. I commented them out in the Go script. I don't think terminal was open. Terminal is an umbrella term for Putty, etc., correct?
February 28, 201115 yr Try using the fuser command to see what process is using the disk. Or try using the "stop array" button in unMENU, which will kill processes that are preventing the array from being stopped and then stop it.
February 28, 201115 yr Try using the fuser command to see what process is using the disk. Or try using the "stop array" button in unMENU, which will kill processes that are preventing the array from being stopped and then stop it. The Stop Array button allows the array disks to unmount, but not the cache drive. fuser -cu /dev/cache ?
February 28, 201115 yr I use the command underneath as a last resort when killing the python process ID didn't work: fuser -mvk /mnt/cache
February 28, 201115 yr Using the steps above, but with the Stop Array button on the Array Management page, the cache drive unmounted in just a few seconds. It's unclear to me what the differences are between the Stop Array buttons (Array Management and unRAID Main), but that's for another day.
February 28, 201115 yr Using the steps above, but with the Stop Array button on the Array Management page, the cache drive unmounted in just a few seconds. It's unclear to me what the differences are between the Stop Array buttons (Array Management and unRAID Main), but that's for another day. The stop button via unMenu will kill things that are keeping the array busy. The unRAID page does not try to kill anything keeping a disk busy.
February 28, 201115 yr Using the steps above, but with the Stop Array button on the Array Management page, the cache drive unmounted in just a few seconds. It's unclear to me what the differences are between the Stop Array buttons (Array Management and unRAID Main), but that's for another day. The stop button via unMenu will kill things that are keeping the array busy. The unRAID page does not try to kill anything keeping a disk busy. Do you know why they have different functions?
February 28, 201115 yr Do you know why they have different functions? Yes, the assumption of LimeTech is that you are smart enough to stop applications that are running on the array before you shut the server down. There is also the assumption that something important could be happening that you do not want killed. If it was killed it could be detrimental and cause data corruption. None of the addon's to this point have been sanctioned by LimeTech, we are on our own at this point. Addon support is coming but for right now it is not implemented completely.
February 28, 201115 yr I'm pretty sure that even having Windows Explorer open to the cache disk would keep it from unmounting. Having a terminal window logged in and cd'd to the cache disk will do it for sure. You likely just closed the application (not knowing it was related) the successful time it stopped. And the stop button was never meant to do anything more. In my mind, there was no intention of unRAID running applications such as this so there was no need for unRAID to support stopping these add-ons. Peter
March 23, 201115 yr After adding a new Supermicro controller, and booting up, sab won't respond. Not sure where to start, unfortunately. Go script: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c # determine if cache drive online, retry upto 7 times for i in 0 1 2 3 4 5 6 7 do if [ ! -d /mnt/cache ] then sleep 15 fi done # If Cache drive is online, start SABnzbd, Sickbeard, and CouchPotato if [ -d /mnt/cache ]; then cd /mnt/cache/.custom installpkg /boot/packages/SABnzbdDependencies-2.1-i486-unRAID.tgz python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d -s 192.168.3.175:8082 # python /mnt/cache/.custom/sickbeard/SickBeard.py --daemon # python /mnt/cache/.custom/couchpotato/CouchPotato.py -d fi Output of top in Putty: Tower login: root Linux 2.6.32.9-unRAID. root@Tower:~# top top - 21:12:34 up 49 min, 1 user, load average: 2.15, 2.09, 1.72 Tasks: 84 total, 3 running, 81 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 7.3%sy, 0.0%ni, 14.3%id, 68.1%wa, 9.3%hi, 1.0%si, 0.0%st Mem: 1814368k total, 1771424k used, 42944k free, 128028k buffers Swap: 0k total, 0k used, 0k free, 1526620k cached Unknown command - try 'h' for help PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6448 root 20 0 14276 4264 3080 R 5.0 0.2 1:39.63 smbd 3316 root 20 0 62104 1976 696 S 4.3 0.1 2:14.95 shfs 305 root 20 0 0 0 0 S 0.3 0.0 0:06.89 kswapd0 1 root 20 0 704 308 264 S 0.0 0.0 0:01.48 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0 5 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0 6 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper 11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 async/mgr 112 root 20 0 0 0 0 S 0.0 0.0 0:02.15 sync_supers 114 root 20 0 0 0 0 S 0.0 0.0 0:00.00 bdi-default 116 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kblockd/0 117 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kacpid 118 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kacpi_notify 119 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kacpi_hotplug 232 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ata/0 233 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ata_aux 237 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksuspend_usbd 242 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khubd 245 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kseriod 280 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rpciod/0 350 root 20 0 0 0 0 S 0.0 0.0 0:00.00 aio/0 356 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsiod 361 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kslowd000 362 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kslowd001 589 root 20 0 0 0 0 S 0.0 0.0 0:00.00 usbhid_resumer 628 root 16 -4 1944 860 480 S 0.0 0.0 0:00.05 udevd I don't see Python in there. I visited the User Scripts page, and clicked Stop Python, then clicked Start Python. ctrl+c in Putty, then ran top again. No Python... syslog-2011-03-22.txt
March 23, 201115 yr Is your cache drive still there. Go to the SAB directory and try to run it from the command line. Don't use any switches and you'll get some data back on what it's doing. Peter
March 23, 201115 yr Is your cache drive still there. Go to the SAB directory and try to run it from the command line. Don't use any switches and you'll get some data back on what it's doing. Peter Will do. I pasted installpkg /boot/packages/SABnzbdDependencies-2.1-i486-unRAID.tgz, then pasted: python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d -s 192.168.3.175:8082 and sab is now loading. I was certain a reboot has happened since sab install and before this reboot. Maybe not. Looks like the dependencies did not re-install after shut down. I looked through the Pkg Manager, but don't see what should be set to install upon reboot.
May 5, 201115 yr Is there an easy way for updating to 0.6.0 final for 0.5.x installed via this thread's method?
May 5, 201115 yr Is there an easy way for updating to 0.6.0 final for 0.5.x installed via this thread's method? Assuming your .sabnzbd folder is on the cache drive, you just copy the files over. Easy peasy, lemon squeezy. I did this to upgrade from 0.5.x to 0.6RC2. Back up the entire .sabnzbd folder before copying over, just in case.
Archived
This topic is now archived and is closed to further replies.