SABnzbd 1.2.0 (All ReadyNAS Platforms)

So here we are again with another SABnzbd update. This time I managed to build for all ReadyNAS platforms and without further ado those are the links to the add-ons:

Comments

  1. Hans Åström says:

    Still no NZBGet update?
    I purchased both SABnzb and NZBGet and can only use NZBGet..

    // Hans

  2. Martin Adlerborn says:

    I’m also interested in NZBGet Stable version 17.1.
    Thanks in advance.

  3. Jay Sams says:

    I get an error even on factory reset system:

    Setting up sabnzbd (1.2.0-rnx1) …
    ln: target ‘/apps/sabnzbd/config/Downloads’ is not a directory
    dpkg: error processing package sabnzbd (–configure):
    subprocess installed post-installation script returned error exit status 1
    Errors were encountered while processing:
    sabnzbd
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    root@ReadyNAS:/media/sabnzbd#

    • Jay Sams says:

      I figured out the issue. This command is looking for the data volume but since I have USB drives attached it returns 2 values (Data – the Raid volume and Media – USB volumes). It picks Media as the data volume and it goes downhill from there. I ejected the USB drives before installing and now it install properly without errors.

      With USB drives attached:
      root@ReadyNAS:~# rn_nml -g volumes | grep resource-id | awk -F= ‘{ print $2 }’ | awk ‘{ print $1 }’ | tr -d ‘”‘
      data
      media

      After USB drives ejected:
      root@ReadyNAS:~# rn_nml -g volumes | grep resource-id | awk -F= ‘{ print $2 }’ | awk ‘{ print $1 }’ | tr -d ‘”‘
      data

      • Whoa. Cool find, thanks a lot! Would you mind running the command

        rn_nml -g volumes | grep resource-id

        with the USB drive attached and send the output for I’m currently abroad and can’t test myself?

        • Jay Sams says:

          root@ReadyNAS:/apps/sabnzbd/config/admin# rn_nml -g volumes | grep resource-id

          • Jay Sams says:

            root@ReadyNAS:/apps/sabnzbd/config/admin# rn_nml -g volumes | grep resource-id

        • Jay Sams says:

          Sorry – it isn’t posting the results which is why I keep trying:

        • Jay Sams says:

          I removed the less than and greater than to see if that works that surrounds the results:

          Volume resource-id=”data” resource-type=”Volume”/
          Volume resource-id=”media” resource-type=”Volume” ejectable=”true”/