Wiidge

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Wiidge's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I've managed to solve the issue and thought I'd post how despite having only a phone and week internet (forgive my lack of logs and details). The problem arose from me pointing to the cache drive /mnt/cache/Films but whenever the mover script removed everynight. Then couch potato had nowhere to rename too. The trick to resolve it for anyone with a similar issue is to point the renaming location to /mnt/user/Films and enable the cache drive for the user share named 'films'. This is accomplished by going to the user share tab and clicking the films user share, scrolling down to the option "use cache drive" and selecting yes. It's a small section which is easily missed if you're rushing or not paying attention. Once you do this everything should work out :-)
  2. Hello all, I'm still having trouble setting up a config for my sab/cp/sb setup. At the moment Couch potato is downloading films, but it isn't moving them from the sab folder to a top level cache folder. I found my previous issue wih sickbeard not running the sabtosickbeard.py script was that the permissions was not set. I'm just wondering if anyone knows what I might be doing wrong here, I've checked permissions but can't see anything wrong. Is there a way to force cp to check its watched directory? It's logs are practically blank. Cheers.
  3. It works! Thanks for your help everyone, it turns out the swap file was to small!
  4. I'm going to try making a 16GB swap file on the cache drive to see if that fixes this issue. I'm hoping it does. Admittedly I could do with more ram, but if this works I'll be happy for now. I'll report back!
  5. I've hard coded all of the folders now just incase they were ignoring their relative paths. So now my Temporary download folder says "/mnt/cache/.data/sabnzbd/Downloads/incomplete" The system has 4gb of ram. I still can't work out why unraid kills the python process while unpacking.
  6. I thought systems with a lot less ram than mine have managed to run sab? It looks like swap is enabled by default when looking at rc14, so I can't see how it's running out of ram. I've setup the install to go to "/mnt/cache/.apps/sabnzbd" and the data to go to "/mnt/cache/.data/sabnzbd" but I still seem to get this issue, even on a fresh install. How do I ensure /tmp files aren't being used, i've gone through as many folder menus I can in an effort to find it
  7. Have I asked this in the incorrect sub forum? Maybe I should have put it under "user customisation" to get a better response? I'm still extremely confused about setting this up and scared that constantly killing plugins will risk my data, so any help anyone can offer would still really help me out!
  8. I'm running a fairly simple setup although very new to this. I have unraid v5.0-rc3 plus installed. I have a 2TB WD green parity drive a 2TB WD green data drive a 1TB samsung data drive and a 500gb cache drive I've installed the "influenced" versions of Sab/CP and sickbeard. I also have unmenu installed (mostly to try the swap file funtionality in trouble shooting this) and simple features web front end. The setup between the usenet apps is running fine, but when sab comes to unpack and unrar the files, unraid seems to fall over horrendously after killing python processes. It mentions being out of memory despite having 4G of ram and a 4G swap enabled. I've included the stack trace from the syslog below, but I'm really starting to pull hair out working out why this happens. If anyone could lend a hand, I'd be *very* grateful! May 30 14:59:06 Tower kernel: unrar invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0, oom_score_adj=0 (Minor Issues) May 30 14:59:06 Tower kernel: Pid: 18812, comm: unrar Tainted: G W 3.0.31-unRAID #1 (Errors) May 30 14:59:06 Tower kernel: Call Trace: (Errors) May 30 14:59:06 Tower kernel: [<c105d493>] T.575+0x55/0x15f (Errors) May 30 14:59:06 Tower kernel: [<c119d61b>] ? ___ratelimit+0xaf/0xc4 (Errors) May 30 14:59:06 Tower kernel: [<c105d5cc>] T.574+0x2f/0x108 (Errors) May 30 14:59:06 Tower kernel: [<c10300b9>] ? has_capability_noaudit+0x18/0x21 (Errors) May 30 14:59:06 Tower kernel: [<c105d8a2>] out_of_memory+0x1fd/0x283 (Errors) May 30 14:59:06 Tower kernel: [<c10603b1>] __alloc_pages_nodemask+0x3f8/0x47f (Errors) May 30 14:59:06 Tower kernel: [<c1078211>] read_swap_cache_async+0x45/0xca (Errors) May 30 14:59:06 Tower kernel: [<c10782d7>] swapin_readahead+0x41/0x70 (Errors) May 30 14:59:06 Tower kernel: [<c106d8f3>] do_swap_page+0xc6/0x3a9 (Errors) May 30 14:59:06 Tower kernel: [<c106dd27>] handle_pte_fault+0x151/0x20f (Errors) May 30 14:59:06 Tower kernel: [<c106e24c>] handle_mm_fault+0x138/0x14a (Errors) May 30 14:59:06 Tower kernel: [<c101b582>] ? mm_fault_error+0x129/0x129 (Errors) May 30 14:59:06 Tower kernel: [<c101b896>] do_page_fault+0x314/0x332 (Errors) May 30 14:59:06 Tower kernel: [<c1080953>] ? vfs_read+0xe6/0xfa (Errors) May 30 14:59:06 Tower kernel: [<c107ff4a>] ? do_sync_write+0xc5/0xc5 (Errors) May 30 14:59:06 Tower kernel: [<c10809fe>] ? sys_read+0x3b/0x60 (Errors) May 30 14:59:06 Tower kernel: [<c101b582>] ? mm_fault_error+0x129/0x129 (Errors) May 30 14:59:06 Tower kernel: [<c130f302>] error_code+0x5a/0x60 (Errors) May 30 14:59:06 Tower kernel: [<c1300000>] ? pci_bus_release_bridge_resources+0x99/0x152 (Errors) May 30 14:59:06 Tower kernel: [<c101b582>] ? mm_fault_error+0x129/0x129 (Errors) May 30 14:59:06 Tower kernel: Mem-Info: May 30 14:59:06 Tower kernel: DMA per-cpu: May 30 14:59:06 Tower kernel: CPU 0: hi: 0, btch: 1 usd: 0 May 30 14:59:06 Tower kernel: CPU 1: hi: 0, btch: 1 usd: 0 May 30 14:59:06 Tower kernel: CPU 2: hi: 0, btch: 1 usd: 0 May 30 14:59:06 Tower kernel: CPU 3: hi: 0, btch: 1 usd: 0 May 30 14:59:06 Tower kernel: Normal per-cpu: May 30 14:59:06 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 0 May 30 14:59:06 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 0 May 30 14:59:06 Tower kernel: CPU 2: hi: 186, btch: 31 usd: 1 May 30 14:59:06 Tower kernel: CPU 3: hi: 186, btch: 31 usd: 0 May 30 14:59:06 Tower kernel: HighMem per-cpu: May 30 14:59:06 Tower kernel: CPU 0: hi: 186, btch: 31 usd: 2 May 30 14:59:06 Tower kernel: CPU 1: hi: 186, btch: 31 usd: 0 May 30 14:59:06 Tower kernel: CPU 2: hi: 186, btch: 31 usd: 30 May 30 14:59:06 Tower kernel: CPU 3: hi: 186, btch: 31 usd: 151 May 30 14:59:06 Tower kernel: active_anon:38 inactive_anon:0 isolated_anon:0 full_syslog_trace.txt