Suddenly can't connect to SABnzbd

I have the sherpa SABnzbd pkg running on my NAS (TS-464) and suddenly today I can’t communicate with it. The only thing that I’m aware of that’s changed is I installed the latest QNAP firmware update QTS 5.2.9.3499 early this morning. My other pkgs running on the NAS are working fine and the SABnzbd pkg is running with no errors. I’ve uninstalled and re-installed but still no go.

Short of rolling back to the previous firmware (is that even possible?) I’m out of ideas. Does anyone have any info or experiencing similar?

Hi mate, can you please post the output of this command?

/etc/init.d/sabnzbd.sh status
# /etc/init.d/sabnzbd.sh status

- QPKG enabled: true
- application auto-update: false
- active git branch: master
- daemon PID: none

It’s not running at the moment.

Can you please check the service log?

/etc/init.d/sabnzbd.sh log

I didn’t know these commands existed :slight_smile:
This are the logs from my last re-install attempt til now, it seems the virtual python env isn’t there anymore…no idea why?

    109 - source: sabnzbd.sh, action: start, time: Fri 29 May 2026 12:45:58 PM EST, load: 1.94 
    110 - package: 260502, service: 260502, library: 260501
    111 - QPKG enabled: true
    112 - application auto-update: false
    113 - active git branch: 
    114 - daemon PID: none
    115 - file exists: /opt/bin/git
    116 > create 'SABnzbd' from remote repository: OK
    117 - active git branch: master
    118 > create new virtual Python environment: failed
    119 dbug: (LL) 
    120 dbug: (LL) adding external log to main log ...
    121 dbug: (LL) ----------------------------------------------------------------------------------------------------
    122 dbug: (LL) log file: '/var/log/DisplayRunAndLog_O7su6q'
    123 dbug: (LL) command: 'export PIP_CACHE_DIR="/share/CACHEDEV1_DATA/.qpkg/SABnzbd/pip-cache" VIRTUALENV_OVERRIDE_APP_DATA="/share/CACHEDEV1_DATA>
    124 dbug: (LL) = result_code: [1]
    125 dbug: (LL) ••••••••••••••••••••••••••••••••••• stdout & stderr begins below •••••••••••••••••••••••••••••••••••
    126 dbug: (LL) /opt/bin/python3: No module named virtualenv
    127 dbug: (LL) ••••••••••••••••••••••••••••••••••• stdout & stderr is complete ••••••••••••••••••••••••••••••••••••
    128 dbug: (LL) ----------------------------------------------------------------------------------------------------
    129 > create QPKG 'pip' config: OK
    130 > add location '/share/CACHEDEV1_DATA/.qpkg/SABnzbd/pip-cache' as 'pip' cache: OK
    131 > add location '/share/CACHEDEV1_DATA/.qpkg/SABnzbd/qpkg-wheels' to 'pip' search path: OK
    132 ! unable to install addons: virtual Python environment does not exist
    133 = source: sabnzbd.sh, action: start, time: Fri 29 May 2026 12:46:01 PM EST, result: FAILED, elapsed: 2,440ms, load: 2.11 
    134 •
    135 - source: sabnzbd.sh, action: stop, time: Fri 29 May 2026 5:11:54 PM EST, load: 1.12 
    136 - package: 260502, service: 260502, library: 260501
    137 - QPKG enabled: false
    138 - application auto-update: false
    139 - active git branch: master
    140 - daemon PID: none
    141 = source: sabnzbd.sh, action: stop, time: Fri 29 May 2026 5:11:54 PM EST, result: OK, elapsed: 24ms, load: 1.12 
    142 •
    143 - source: sabnzbd.sh, action: start, time: Fri 29 May 2026 5:12:12 PM EST, load: 0.95 
    144 - package: 260502, service: 260502, library: 260501
    145 - QPKG enabled: true
    146 - application auto-update: false
    147 - active git branch: master
    148 - daemon PID: none
    149 - file exists: /opt/bin/git
    150 - active git branch: master
    151 > create new virtual Python environment: failed
    152 dbug: (LL) 
    153 dbug: (LL) adding external log to main log ...
    154 dbug: (LL) ----------------------------------------------------------------------------------------------------
    155 dbug: (LL) log file: '/var/log/DisplayRunAndLog_cQ2Rrr'
    156 dbug: (LL) command: 'export PIP_CACHE_DIR="/share/CACHEDEV1_DATA/.qpkg/SABnzbd/pip-cache" VIRTUALENV_OVERRIDE_APP_DATA="/share/CACHEDEV1_DATA>
    157 dbug: (LL) = result_code: [1]
    158 dbug: (LL) ••••••••••••••••••••••••••••••••••• stdout & stderr begins below •••••••••••••••••••••••••••••••••••
    159 dbug: (LL) /opt/bin/python3: No module named virtualenv
    160 dbug: (LL) ••••••••••••••••••••••••••••••••••• stdout & stderr is complete ••••••••••••••••••••••••••••••••••••
    161 dbug: (LL) ----------------------------------------------------------------------------------------------------
    162 ! unable to install addons: virtual Python environment does not exist
    163 = source: sabnzbd.sh, action: start, time: Fri 29 May 2026 5:12:12 PM EST, result: FAILED, elapsed: 116ms, load: 0.95

You can see all the commands if you run the service script without any args. :nerd_face:

I agree, the virtualenv module isn’t there. Hmm, is everything up-to-date?

sherpa upgrade new

Also, it’s a good idea to run a fix when things go wrong:

sherpa fix

When this is complete, try checking the SABnzbd service script status again.

It seems sherpa upgrade new has fixed it.
I now have the sabnzbd wizard and I can re-cfg it.

Thanks for your help, much appreciated.

Good work mate. :nerd_face:

If you backup the config using the service script before uninstalling, it’s a breeze to restore it again after reinstalling SABnzbd. The service script knows how to handle the backup and restore.