Page 2 of 3

Re: Sabnzbd crashing on qnap

Posted: January 7th, 2019, 12:53 am
by nis14
Looks like I can reproduce the crash with a specific NZB file... is there any logging I can turn on the help diagnose?

Re: Sabnzbd crashing on qnap

Posted: January 7th, 2019, 12:55 am
by OneCD
Can you enable debug logging in the SAB UI?

Re: Sabnzbd crashing on qnap

Posted: January 7th, 2019, 2:09 am
by nis14
I ran it with debug on, I didn't get the error message previous when it crashed. Around the time of the crash the last thing in the logs was API calls. I remove the chrome extension which uses the API to see if that helps. It's successfully downloaded the previously failing NZB twice now but I'll keep testing

Re: Sabnzbd crashing on qnap

Posted: January 7th, 2019, 5:17 am
by nis14
That didn't help in the end

Re: Sabnzbd crashing on qnap

Posted: January 7th, 2019, 5:42 am
by safihre
What are the last few lines before "__version__ = 19"?

Re: Sabnzbd crashing on qnap

Posted: January 9th, 2019, 4:35 am
by nis14
Where is that sorry?

Re: Sabnzbd crashing on qnap

Posted: January 9th, 2019, 5:21 am
by safihre
At the end of the Debug log.

Re: Sabnzbd crashing on qnap

Posted: January 9th, 2019, 8:39 pm
by nis14
2019-01-07 16:29:24,302::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:29:24,335::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:29:39,326::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:29:39,372::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:29:54,620::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:29:54,821::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:30:09,582::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:30:09,726::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:30:24,278::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:30:24,328::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:30:39,291::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:30:39,338::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:30:54,314::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:30:54,371::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:31:09,529::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:31:09,593::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:31:24,644::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
2019-01-07 16:31:24,669::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:31:39,334::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'10', 'mode': u'history'}
2019-01-07 16:31:39,336::DEBUG::[interface:481] API-call from 192.168.1.16 [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36] {'output': u'json', 'apikey': u'<HASH>fdbb23c', 'limit': u'5', 'mode': u'queue'}
__version__ = 19
__encoding__ = utf-8
[misc]

Re: Sabnzbd crashing on qnap

Posted: January 10th, 2019, 3:14 am
by safihre
Very strange. Seems like a hard-kill..

Re: Sabnzbd crashing on qnap

Posted: January 12th, 2019, 1:12 am
by nis14
Is there a script I can periodically run to check if the process is running and if not restart it?

Re: Sabnzbd crashing on qnap

Posted: January 12th, 2019, 1:32 am
by OneCD
@nis14, I've since updated the SABnzbd QPKG and it should now recover correctly from a crash. The new version is 190109. Can you please download the latest sherpa script and reinstall your SABnzbd? No stability fixes, unfortunately. :(
nis14 wrote: January 12th, 2019, 1:12 am Is there a script I can periodically run to check if the process is running and if not restart it?
How do you feel about re-running the init script with a 'start' command via your cron - maybe once per hour? This wouldn't shutdown a running instance, it would only launch SAB if SAB wasn't already running.

To everyone: the current init script launches [SABnzbd.py] with the '--daemon' option, then exits. Maybe I could remove the daemon option, and put the launch in a loop? Means the user wouldn't be able to exit SAB via a UI shutdown, but they could run another init with a 'stop' command to shutdown SAB.

It's not a fix, just a way of ensuring SAB is restarted automatically.

Thoughts?

Re: Sabnzbd crashing on qnap

Posted: January 12th, 2019, 5:16 am
by safihre
Seems this problem is only sporadic? Would probably be nice to keep the UI-based shutdown option.

Re: Sabnzbd crashing on qnap

Posted: January 12th, 2019, 3:00 pm
by OneCD
Agree @safihre, it may be better for @nis14 to regularly start SABnzbd via cron.

Re: Sabnzbd crashing on qnap

Posted: January 12th, 2019, 11:14 pm
by nis14
@OneCD I've updated SABnzbd to 190109. I'm happy to run a cron job hourly. What's the best way to do that?

Re: Sabnzbd crashing on qnap

Posted: January 12th, 2019, 11:21 pm
by OneCD
Suggest adding a line to your crontab structured like this:

Code: Select all

0 * * * * /etc/init.d/sabnzbd.sh start
... but this isn't added in the "usual" Linux way.

Due to customisations QNAP have made to their cron system, you'll need to follow the wiki instead: https://wiki.qnap.com/wiki/Add_items_to_crontab