SABnzbd Forums

I'm running version 2.3.6 [190ec0a] on qnap TS-219PII firmware 4.3.3.0724 install using shipera.

During some downloads the I get disconnected from the webpage, what I know so far is:
- I get an Err_Connection_refused on reconnect
- Sabnzbd process isn't running anymore
- I restart using the qnap app centre
- This is in the logs 2019-01-07 11:13:54,514::ERROR::[nzbstuff:1537] Error importing <NzbFile: filename=<HASH>ed7455a.part55.rar, type=None>

Any help on resolving this is appreciated.

Hi and welcome to the forum.

Can you please post the SAB init log? This can be viewed with:

Thank you, this is the last start

-------------------- start requested --------------------
= Mon Jan 7 11:13:07 EST 2019
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK

Can you please post the last few start/stops? I'm trying to see if the stop event is recorded.

Can't seem to post it... "New user are not allowed to post links".

* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): -------------------- stop requested --------------------
= Sun Jan 6 19:45:55 EST 2019
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Sun Jan 6 19:46:04 EST 2019
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK

-------------------- stop requested --------------------
= Mon Jan 7 10:30:10 EST 2019
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Mon Jan 7 10:30:17 EST 2019
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK

-------------------- stop requested --------------------
= Mon Jan 7 11:13:00 EST 2019
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Mon Jan 7 11:13:07 EST 2019
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK

* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): -------------------- stop requested --------------------
= Sun Jan 6 19:31:03 EST 2019
= (SABnzbdplus) is not active
-------------------- start requested --------------------
= Sun Jan 6 19:31:21 EST 2019
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
From git://github.com/clinton-hall/nzbToMedia
e1fe633..f9f3faf master -> origin/master
* [new tag] 12.0.5 -> 12.0.5
* [new tag] 12.0.2 -> 12.0.2
* [new tag] 12.0.2-rc.1 -> 12.0.2-rc.1
* [new tag] 12.0.3 -> 12.0.3
* [new tag] 12.0.3-rc.1 -> 12.0.3-rc.1
* [new tag] 12.0.4 -> 12.0.4
* [new tag] 12.0.4-rc.1 -> 12.0.4-rc.1
* [new tag] 12.0.5-rc.1 -> 12.0.5-rc.1
Updating e1fe633..f9f3faf
Fast-forward
.bumpversion.cfg | 2 +-
README.md | 2 +-
TorrentToMedia.py | 2 +-
cleanup.py | 45 +++++++++++++++++++++++++++++++++++++++++----
core/__init__.py | 2 +-
core/auto_process/movies.py | 5 ++++-
core/version_check.py | 2 +-
nzbToMedia.py | 2 +-
setup.py | 2 +-
9 files changed, 52 insertions(+), 12 deletions(-)

before that it looks like an upgrade...

create mode 100644 libs/win/test_path.py
delete mode 100644 libs/xdg/BaseDirectory.py
delete mode 100644 libs/xdg/DesktopEntry.py
delete mode 100644 libs/xdg/Exceptions.py
delete mode 100644 libs/xdg/IconTheme.py
delete mode 100644 libs/xdg/IniFile.py
delete mode 100644 libs/xdg/Locale.py
delete mode 100644 libs/xdg/Menu.py
delete mode 100644 libs/xdg/MenuEditor.py
delete mode 100644 libs/xdg/Mime.py
delete mode 100644 libs/xdg/RecentFiles.py
delete mode 100644 libs/xdg/__init__.py
delete mode 100644 libs/xdg/util.py
delete mode 100644 libs/yaml/__init__.py
delete mode 100644 libs/yaml/representer.py
delete mode 100644 libs/yaml/resolver.py
delete mode 100644 libs/yaml/scanner.py

nis14 wrote: ↑January 6th, 2019, 11:12 pm -------------------- start requested --------------------
= Sun Jan 6 19:46:04 EST 2019
= (SABnzbdplus) is not active
* updating (SABnzbdplus): OK
Already up to date.
* updating (nzbToMedia): OK
Already up to date.
* stopping (SABnzbdplus) with SIGTERM: stopped OK in 0 seconds
* starting (SABnzbdplus): OK

That "stopping" line shouldn't be there. Your init log shows that it's repeated each time SAB is supposed to be starting.

What version is your SABnzbd QPKG? This is shown in your QTS App Center.

In App Center is says SABnzbdplus 180909.... I installed it with shirpa

Yup, that's the latest one.

Can you please download and run the newest sherpa script and use it to reinstall SAB?

Just had a thought: are you running two instances of SAB?

I've recently reinitialised the NAS and fresh installed SAB so shouldn't be running two...

Only one process running
[~] # ps ax | grep -i sabnzbd | grep -v grep
14328 admin 61964 S /opt/bin/python2.7 SABnzbd.py --daemon --config-file /share/MD0_DATA/.qpkg/SABnzbdplus/config/config.ini --browser 0 --pidfile /tm

I've updated SAb

[/share/Public] # curl -ksO https://raw.githubusercontent.com/onecd ... /sherpa.sh && chmod +x sherpa.sh
[/share/Public] # ./sherpa.sh SABnzbd
sherpa.sh (190106)

[ done ] downloaded sherpa package list
[ done ] downloaded QPKG (SABnzbdplus_180909.qpkg)
[ done ] updated Entware package list
[ done ] no IPKGs are required
[ done ] downloaded & installed (PIP modules)
[ done ] daemon stopped (sabnzbd.sh)
[ done ] created 'SABnzbdplus' settings backup
[ done ] uninstalled QPKG 'SABnzbdplus'
[ done ] installed QPKG (SABnzbdplus_180909.qpkg)
[ done ] wait complete
[ done ] daemon stopped (sabnzbd.sh)
[ done ] restored 'SABnzbdplus' settings backup
[ done ] daemon started (sabnzbd.sh)

[ done ] 'SABnzbdplus' has been successfully reinstalled!

- To display the debug log:
cat /share/Public/sherpa.debug.log

nis14 wrote: ↑January 7th, 2019, 12:18 am I've recently reinitialised the NAS and fresh installed SAB so shouldn't be running two...

Agree.

nis14 wrote: ↑January 7th, 2019, 12:18 am Only one process running
[~] # ps ax | grep -i sabnzbd | grep -v grep
14328 admin 61964 S /opt/bin/python2.7 SABnzbd.py --daemon --config-file /share/MD0_DATA/.qpkg/SABnzbdplus/config/config.ini --browser 0 --pidfile /tm

Yup, looks good.

BTW: I can now see why that "stopping" line is appearing in the log. Here's the first few lines of the 'start' function: So, if I had to guess, that PID file isn't being removed - probably because SAB crashes and doesn't perform a graceful shutdown via the init script.

I'll have to do some work on this separate problem, but the bad news is it won't stop your SAB from crashing again. It will only help it recover better.

Unfortunately, with QNAP models like yours that have a fixed 512MB RAM, there's an intermittent issue between QTS, the Python interpreter installed via Entware, and SAB that causes this sudden SAB shutdown.

No-one has been able to work out why it happens. In fact, there was another user only this morning who's SAB was also disappearing, but their NAS model has only 256MB RAM. Unless it can be found why this crash occurs, the only thing I can suggest is a NAS upgrade. This doesn't occur with models that have 1GB or more of RAM.