Synology DSM 6

[Orlith77]

Hi Guys

I moved to the version 6 of DSM for Synology.
Since then I saw an error when starting sabnzbd on it : unzip binary not found.
I thought that my SABNZBD version was broken after the upgrade so I decided to remove it and reinstalled the beta from SynoCommunity
BUt I got the same behavior.

Any idea ?

Btw I don't know if it could be linked but adding nzb file from wwww.nextdownload.org is always failing with this error :
Fichier NZB invalide Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST.nzb, rejeté (raison=not well-formed (invalid token), ligne=1

"Nzb files" from nextdownload.org are rar file.
If I add such file to my NAS sabnzbd, i get the error
I f I use my Windows sabnzbd there is no error
If I unrar the file and add the nzb to the Nas sabnzbd, there 's no error and the download start

What could be the issue then ?

Feel free to ask for any information

Thx

[shypike]

If the NZB files are compressed in RAR5 format,
then SABnzbd cannot read them.
It's internal RAR support is still at RAR4 level.
(For unpacking of downloaded files we use the external unrar tool.)

[Orlith77]

If the NZB files are compressed in RAR5 format,
then SABnzbd cannot read them.
It's internal RAR support is still at RAR4 level.
(For unpacking of downloaded files we use the external unrar tool.)

Ok but what if the same rar file can be read by sabnzbd windows version ? Is that normal behavior ?
Thx for your reply

[shypike]

I have no idea.
Possible something goes wrong in the upload (like our built-in webserver doing something odd).
I don't have the means to debug a Syno (nor do I have one).

Maybe it's an option to set logging to "Debug" on the Status page
and see whether anything useful is logged when you load an RAR-red NZB.

[Orlith77]

Unfortunatly there's not much useful in the log :

Code: Select all

2016-01-21 11:31:10,350::INFO::[__init__:639] Adding Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST.rar
2016-01-21 11:31:10,423::INFO::[nzbstuff:668] Replacing dots with spaces in Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST
2016-01-21 11:31:10,427::DEBUG::[nzbstuff:1554] Dupe checking NZB in history: filename=Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST.nzb, md5sum=None, result=False
2016-01-21 11:31:10,428::DEBUG::[nzbstuff:1557] Dupe checking NZB against backup: filename=Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST.nzb, result=False
2016-01-21 11:31:10,437::DEBUG::[nzbstuff:1563] Dupe checking series+season+ep in history: series=False, season=, episode=, result=False
2016-01-21 11:31:10,439::INFO::[misc:793] Creating directories: /volume1/Download/incomplete/Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST
2016-01-21 11:31:10,469::WARNING::[nzbstuff:721] Fichier NZB invalide Pawn.Sacrifice.2014.FRENCH.720p.BluRay.x264-LOST.nzb, rejeté (raison=not well-formed (invalid token), ligne=1)

Thanks anyway for your help

[shypike]

There are two possible causes.
1. The NZB inside the RAR file is no good
2. The name of the RAR file doesn't end in .rar, so that SABnzbd doesn't know it's a RAR file
Meaning: the name that is sent along with the uploaded file is wrong

1. is unlikely if you can upload the same RAR to the Windows version
2. could be caused by a bug in the internal webserver or the indexer website or a unhappy combination of both

Do you upload the RAR file manually to the Syno-SABnzbd or
does Syno-SABnzbd need to get it from the indexer website by itself?

[Orlith77]

1. the nzb file itself looks fine because if I extract the nzb from the rar and put it in sabnzbd on my nas it downloads well
2. could be

I set up sab to look in a folder (on my nas) every 5s. I put rar & other nzb files in that folder, then sab load them automatically. I do not use (neither looked at / was aware of ) the auto grab from indexer website.

Thx

[shypike]

I set up sab to look in a folder (on my nas) every 5s. I put rar & other nzb files in that folder, then sab load them automatically.

That the causes are narrowed down.
Do I undestand correctly that only RAR files coming from www.nextdownload.org are problematic?
Other RAR files with NZBs in them work fine?
If so, can you email me some of those "bad" RAR files for inspection?
bugs@sabnzbd.org

[Orlith77]

That the causes are narrowed down.
Do I undestand correctly that only RAR files coming from http://www.nextdownload.org are problematic?
Other RAR files with NZBs in them work fine?
If so, can you email me some of those "bad" RAR files for inspection?
bugs@sabnzbd.org

Mail sent.
I have no idea for rar file coming from other website. Never saw such website.

thx

[shypike]

I'm out of options, even my oldest test system reads the RAR without issues.
Possibly it's due to having an old version of Python installed.
Can you take a look at the Config screen?
It should list some system characteristics, like the Python version.

[Orlith77]

Hi
Thx for your test.
Here is what the log says about version :

Code: Select all

2016-01-21 11:39:00,470::INFO::[SABnzbd:1239] SABnzbd.py-0.8.0Beta5 (rev=d7f3a473d70fb1bd57ebf2249e73a72aeaf30791)
2016-01-21 11:39:00,470::INFO::[SABnzbd:1251] Platform = posix
2016-01-21 11:39:00,471::INFO::[SABnzbd:1252] Python-version = 2.7.11 (default, Dec 17 2015, 12:58:48) 
[GCC 4.6.4]
2016-01-21 11:39:00,472::INFO::[SABnzbd:1253] Arguments = /usr/local/sabnzbd-testing/share/SABnzbd/SABnzbd.py -f /usr/local/sabnzbd-testing/var/config.ini --pidfile /usr/local/sabnzbd-testing/var/sabnzbd.pid -d
2016-01-21 11:39:00,473::DEBUG::[SABnzbd:1260] My local IPv4 address = x.x.x.x
2016-01-21 11:39:00,732::DEBUG::[SABnzbd:1266] My public IPv4 address = x.x.x.x
2016-01-21 11:39:00,732::DEBUG::[SABnzbd:1274] Could not determine my IPv6 address
2016-01-21 11:39:00,827::DEBUG::[SABnzbd:1280] CPU Pystone available performance is 11075
2016-01-21 11:39:00,828::INFO::[SABnzbd:1298] Read INI file /usr/local/sabnzbd-testing/var/config.ini
2016-01-21 11:39:00,931::DEBUG::[__init__:1154] Test IPv6: Cannot reach IPv6 test host. Disabling IPv6
2016-01-21 11:39:00,932::DEBUG::[__init__:295] External IPv6 test result: False
2016-01-21 11:39:00,933::INFO::[__init__:958] Loading data for rss_data.sab from /usr/local/sabnzbd-testing/var/admin/rss_data.sab
2016-01-21 11:39:00,935::INFO::[__init__:958] Loading data for totals10.sab from /usr/local/sabnzbd-testing/var/admin/totals10.sab
2016-01-21 11:39:00,936::DEBUG::[bpsmeter:192] Read quota q=0.0 l=0.0 reset=0
2016-01-21 11:39:00,937::INFO::[postproc:89] Loading postproc queue
2016-01-21 11:39:00,938::INFO::[__init__:958] Loading data for postproc2.sab from /usr/local/sabnzbd-testing/var/admin/postproc2.sab
2016-01-21 11:39:00,940::INFO::[__init__:958] Loading data for queue10.sab from /usr/local/sabnzbd-testing/var/admin/queue10.sab
2016-01-21 11:39:00,941::DEBUG::[downloader:154] Initializing downloader/decoder
2016-01-21 11:39:00,943::INFO::[__init__:958] Loading data for watched_data2.sab from /usr/local/sabnzbd-testing/var/admin/watched_data2.sab
2016-01-21 11:39:00,945::INFO::[__init__:958] Loading data for Rating.sab from /usr/local/sabnzbd-testing/var/admin/Rating.sab
2016-01-21 11:39:00,946::INFO::[__init__:961] /usr/local/sabnzbd-testing/var/admin/Rating.sab missing
2016-01-21 11:39:00,947::DEBUG::[scheduler:168] Scheduling RSS interval task every 60 min (delay=32)
2016-01-21 11:39:00,948::INFO::[scheduler:190] Setting schedule for midnight BPS reset
2016-01-21 11:39:00,949::INFO::[downloader:241] Resuming
2016-01-21 11:39:00,950::DEBUG::[__init__:547] PAUSED_ALL inactive
2016-01-21 11:39:00,951::INFO::[__init__:348] All processes started
2016-01-21 11:39:00,952::INFO::[SABnzbd:355] Web dir is /usr/local/sabnzbd-testing/share/SABnzbd/interfaces/Glitter
2016-01-21 11:39:00,953::INFO::[SABnzbd:355] Web dir is /usr/local/sabnzbd-testing/share/SABnzbd/interfaces/smpl
2016-01-21 11:39:00,954::INFO::[SABnzbd:355] Web dir is /usr/local/sabnzbd-testing/share/SABnzbd/interfaces/Config
2016-01-21 11:39:00,955::DEBUG::[SABnzbd:1335] Unwanted extensions are ... []
2016-01-21 11:39:01,209::DEBUG::[newsunpack:149] UNRAR binary version 5.30
2016-01-21 11:39:01,210::INFO::[SABnzbd:483] _yenc module... found!
2016-01-21 11:39:01,211::INFO::[SABnzbd:491] par2 binary... found (/usr/local/sabnzbd-testing/bin/par2)
2016-01-21 11:39:01,212::INFO::[SABnzbd:496] par2-classic binary... found (/usr/local/sabnzbd-testing/bin/par2)
2016-01-21 11:39:01,212::INFO::[SABnzbd:499] UNRAR binary... found (/usr/local/sabnzbd-testing/bin/unrar)
2016-01-21 11:39:01,213::INFO::[SABnzbd:511] 7za binary... found (/usr/syno/bin/7z)
2016-01-21 11:39:01,214::INFO::[SABnzbd:518] nice binary... found (/usr/local/sabnzbd-testing/bin/nice)
2016-01-21 11:39:01,214::INFO::[SABnzbd:524] ionice binary... NOT found!
2016-01-21 11:39:01,215::INFO::[SABnzbd:527] pyOpenSSL... found (True)
2016-01-21 11:39:01,216::INFO::[SABnzbd:1361] SSL version OpenSSL 1.0.2e 3 Dec 2015
2016-01-21 11:39:01,217::INFO::[SABnzbd:1362] SSL potentially supported protocols ['SSLv2', 'SSLv23', 'SSLv3', 'TLSv1', 'TLSv1_1', 'TLSv1_2']
2016-01-21 11:39:01,218::INFO::[SABnzbd:1363] SSL actually supported protocols ['t12', 't11', 't1', 'v23', 'v3', 'v2']
2016-01-21 11:39:01,225::INFO::[SABnzbd:1509] Starting web-interface on 0.0.0.0:9099
2016-01-21 11:39:01,227::INFO::[_cplogging:216] [21/Jan/2016:11:39:01] ENGINE Bus STARTING
2016-01-21 11:39:01,248::INFO::[_cplogging:216] [21/Jan/2016:11:39:01] ENGINE Started monitor thread '_TimeoutMonitor'.
2016-01-21 11:39:01,481::INFO::[_cplogging:216] [21/Jan/2016:11:39:01] ENGINE Serving on https://0.0.0.0:9099
2016-01-21 11:39:01,590::INFO::[_cplogging:216] [21/Jan/2016:11:39:01] ENGINE Serving on http://0.0.0.0:9090
2016-01-21 11:39:01,592::INFO::[_cplogging:216] [21/Jan/2016:11:39:01] ENGINE Bus STARTED
2016-01-21 11:39:01,593::INFO::[zconfig:64] No Bonjour/ZeroConfig support installed
2016-01-21 11:39:01,630::INFO::[SABnzbd:1581] Starting SABnzbd.py-0.8.0Beta5
2016-01-21 11:39:01,631::DEBUG::[__init__:359] Starting postprocessor
2016-01-21 11:39:01,632::DEBUG::[__init__:362] Starting assembler
2016-01-21 11:39:01,633::DEBUG::[__init__:365] Starting downloader
2016-01-21 11:39:01,634::DEBUG::[scheduler:202] Starting scheduler
2016-01-21 11:39:01,636::DEBUG::[__init__:370] Starting dirscanner
2016-01-21 11:39:01,637::INFO::[dirscanner:302] Dirscanner starting up
2016-01-21 11:39:01,638::DEBUG::[__init__:375] Starting urlgrabber
2016-01-21 11:39:01,639::INFO::[urlgrabber:69] URLGrabber starting up

[shypike]

You have the latest and greatest of the Python 2.x series.
One last test is to upload the RAR file from SABnzbd user interface instead of through the watched folder.
That at least would narrow it down a bit further.

Other than that, I'm out of ideas.
The only solution I see is to unpack the RARs before sending them to the Syno.
Very inconvenient, I know.

[Orlith77]

@shypike uploading using the interface give the same error
So we're all out of idea.

Thx for your time trying to solve the issue. It's really appreciate.

[shypike]

Do you happen to have WinRAR?
If so, try RAR-ing a NZB yourself, but it should be RAR4 format, I'm sure you can choose that.
Other than that, we will probably replace the internal unrar support
with just running the external unrar tool.
That should solve your issue.
Unfortunately that won't be before we get to release 0.8.1 (maybe 0.9.0).

[Orlith77]

Thx for the information about the future version.
I'll try to rar the nzb and see. But it's not a big issue to unrar nzb file , it is just annoying. I can live like that for now

thx