Page 1 of 2
"Badly formed yEnc article" error stops download
Posted: February 5th, 2016, 9:08 am
by 88keyz
In the beta when an article returns the following error "Badly formed yEnc article in ..." it causes the download to stop with only a few MB left and it never completes. I've been having this issue for a while with the 0.8x/1.0.x branch but wasn't able to put my finger on the cause. Problem exists on git, PPA and Windows versions however it doesn't exist on 0.7.x versions. I tested a couple of NZB's on both Ubuntu with the git and PPA versions of the beta branch and on Windows with the beta version and on every version I get the same thing, downloads stop with a few MB left and will not complete. Same NZB's on Ubuntu and Windows in the 0.7.x branch download, complete and extract fine. Anyone else seeing this behavior?
Re: "Badly formed yEnc article" error stops download
Posted: February 5th, 2016, 9:21 am
by shypike
That would be a serious issue indeed.
I will investigate this.
Re: "Badly formed yEnc article" error stops download
Posted: February 5th, 2016, 9:25 am
by safihre
Maybe send one of the affected NZB's to
[email protected]?
I never seen this behaviour, maybe it's a specific NZB/newsserver combination?
Re: "Badly formed yEnc article" error stops download
Posted: February 5th, 2016, 9:32 am
by 88keyz
I sent 2 NZB's that I used to test. Both of them have them have the yEnc issue. As for servers, I have Easynews and XS News and I get the same behavior on the US and EU Easynews servers and on the XS News server. All servers connecting using SSL, SSL type is set to V23 on the 0.7.x setups and to Default on the 0.8.x/1.0.x setups.
Re: "Badly formed yEnc article" error stops download
Posted: February 5th, 2016, 10:29 am
by safihre
I just downloaded them but they worked fine for me, so it must be in the combination of the newsservers. I do see the badly formed yEnc in the logs, but it continues just fine.
Astraweb and Frugal (also tried with just Frugal) on SSL.
Re: "Badly formed yEnc article" error stops download
Posted: February 5th, 2016, 10:53 am
by 88keyz
Thanks for checking. Based on your result I disabled my XS News server and the downloads completed fine. Guess that was the problem all along.
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 11:29 am
by 88keyz
Upon further investigation it turns out that the reason for the issue with the XS News server was the OpenSSL protocol support in the pyOpenSSL package that is included in Ubuntu 14.04 LTS. With Ubuntu 14.04 LTS the only available version of pyOpenSSL from apt-get is 0.13.2 which only supports TLS versions up to v1.0. However, I was able to install the latest version of pyOpenSSL, 0.15.1 - which supports TLS protocols up to v1.2, from source and this solved the problem.
For anyone else that experiences this issue, or any other issues relates to SSL protocol support, these were the steps that I took from the Ubuntu command line interface.
WARNING: Do this at your own risk! These steps may affect more than just SABnzbd.
1) Change to your home directory
2) Remove installed version of python-openssl
Code: Select all
sudo apt-get remove python-openssl
3) Download latest version of
pyOpenSSL
Code: Select all
wget http://pypi.python.org/packages/source/p/pyOpenSSL/pyOpenSSL-0.15.1.tar.gz
4) Extract downloaded archive
5) Change to new pyOpenSSL directory
6) Compile and install new pyOpenSSL version
7) Restart SABnzbd
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 3:22 pm
by shypike
Does this mean that XS News only supports TLS 1.1 and 1.2 ?
Didn't you get an error message about not being able to access the server?
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 3:39 pm
by 88keyz
No, there was never an error regarding access. And As I said same servers worked perfect under 0.7.x but that only used the SSL protocol. Could be poor protocol negotiation with the server, hard to say for certain because the only errors I ever got were regarding yEnc. All I can say is that it was a repeatable problem with certain NZBs. After upgrading the pyOpenSSL library the same NZBs complete without issue. Safihre was right though in that the issue a server related one, at least for me.
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 4:39 pm
by sander
shypike wrote:Does this mean that XS News only supports TLS 1.1 and 1.2 ?
Didn't you get an error message about not being able to access the server?
No, reader.xsnews.nl:563 offers SSL 2 and 3, and TLS 1, 1.1 and 1.2. So it must be something else.
Code: Select all
rDNS (94.232.116.131): reader.xsnews.nl.
Service detected: Couldn't determine what's running on port 563, assuming no HTTP service => skipping all HTTP checks
Testing protocols (via sockets except TLS 1.2, SPDY+HTTP2)
SSLv2 offered (NOT ok) -- 2 ciphers
SSLv3 offered (NOT ok)
TLS 1 offered
TLS 1.1 offered
TLS 1.2 offered (OK)
SPDY/NPN not offered
HTTP2/ALPN not offered
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 4:42 pm
by shypike
Sounds more like bugs in OpenSSL to me.
What I've seen so far is that SSL connections work or don't work,
not selective errors in the actual data.
0.7.20 defaulted to V23, which is auto-negotiate.
What setting did XS have in your setup?
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 5:08 pm
by sander
FWIW: I checked my own Ubuntu 14.04.3 LTS, and it indeed has TLS1, and not higher:
Code: Select all
2016-02-06 23:06:12,164::INFO::[sabnzbdplus:1367] SSL potentially supported protocols ['SSLv23', 'SSLv3', 'TLSv1']
2016-02-06 23:06:12,164::INFO::[sabnzbdplus:1368] SSL actually supported protocols ['t1', 'v23', 'v3']
... if I only had a xsnews account ... or borrow from the OP ...
Manual OpenSSL session looks good
Code: Select all
sander@haring:~$ openssl s_client -connect reader.xsnews.nl:563
CONNECTED(00000003)
depth=2 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Certification Authority
verify error:num=20:unable to get local issuer certificate
verify return:0
---
Certificate chain
0 s:/OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=*.xsnews.nl
i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
1 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
i:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Certification Authority
2 s:/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Certification Authority
i:/C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFSTCCBDGgAwIBAgIRALa31btHweOpRnpTndRO52MwDQYJKoZIhvcNAQELBQAw
gZAxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAO
BgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTYwNAYD
VQQDEy1DT01PRE8gUlNBIERvbWFpbiBWYWxpZGF0aW9uIFNlY3VyZSBTZXJ2ZXIg
Q0EwHhcNMTUwNTE4MDAwMDAwWhcNMTYwNTE3MjM1OTU5WjBYMSEwHwYDVQQLExhE
b21haW4gQ29udHJvbCBWYWxpZGF0ZWQxHTAbBgNVBAsTFFBvc2l0aXZlU1NMIFdp
bGRjYXJkMRQwEgYDVQQDFAsqLnhzbmV3cy5ubDCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBALgIG/83rEXKGsH4iVkRRbvXBqB5r4VyfMz4z7HVVgw82JW9
5AduVF0E9aH4+y/YfzNa4+UD77yiwAdw1gbYxJei6qnabkKR7szCU4vT8wNNTCK3
PwlemO7qQ56tWzh13FiZpz+2Y2eUqH6ey2mwu9bPSGTYPb5ANzBjn7HGnSkPT7O4
nW7C2FQLWcqNnTuMj8hAq2q/4Wy6yokdHmsXJ/akQqCoUjfog3qrpJsXQeukqmWv
TupdBvOm7n80oG2TaVvgoovniQkWBKX4TzvGCAas6idlt+jFQQHF+u/aF6iOZj6r
1ZsWNTpu9hR7tBFozUHiGvnxI2lLstJSjFFasHUCAwEAAaOCAdMwggHPMB8GA1Ud
IwQYMBaAFJCvajqUWgvYkOoSVnPfQ7Q6KNrnMB0GA1UdDgQWBBRqwQtys5G9Ukfc
pxcOcQkqAzIuRzAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAdBgNVHSUE
FjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwTwYDVR0gBEgwRjA6BgsrBgEEAbIxAQIC
BzArMCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8uY29tL0NQUzAI
BgZngQwBAgEwVAYDVR0fBE0wSzBJoEegRYZDaHR0cDovL2NybC5jb21vZG9jYS5j
b20vQ09NT0RPUlNBRG9tYWluVmFsaWRhdGlvblNlY3VyZVNlcnZlckNBLmNybDCB
hQYIKwYBBQUHAQEEeTB3ME8GCCsGAQUFBzAChkNodHRwOi8vY3J0LmNvbW9kb2Nh
LmNvbS9DT01PRE9SU0FEb21haW5WYWxpZGF0aW9uU2VjdXJlU2VydmVyQ0EuY3J0
MCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wIQYDVR0RBBow
GIILKi54c25ld3MubmyCCXhzbmV3cy5ubDANBgkqhkiG9w0BAQsFAAOCAQEALTXj
AFQDfOjPG/NO2cwCvfofJtuhQf61wtJX0RUWLU3vjDxEg48y5ZL7J77VRQ/o47oI
gJmQISHF7TW2k2x211Kz59h+JqzoZ/Yr7saqTePKWrqm8ys1GIr8KF/4/iI31/nA
7z+yaq17Y7G7zAiHGnYUIn9bx40JdM/hJvZOUqb71TOfuXLwqu5tKs2qI+wGjuhy
uGhdWwaNBMPEaJ7iIBHU4rFnZc0hQ/FZ/Jjr2nlki6LGFhGim3tnjAXkLC41d9FK
1kaqsBIJP7b9jwOMvF1n1hZfcrKaO155Yh/wyKqDAuk6igqrQuhAvctK8iJmbPT8
y0LCeI1Yj7BLtnMXLw==
-----END CERTIFICATE-----
subject=/OU=Domain Control Validated/OU=PositiveSSL Wildcard/CN=*.xsnews.nl
issuer=/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
---
No client certificate CA names sent
---
SSL handshake has read 4648 bytes and written 637 bytes
---
New, TLSv1/SSLv3, Cipher is AES128-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1.2
Cipher : AES128-SHA
Session-ID: 34A1EBEB42E398C51C6E276D4B495FD79126866FD9D5B5F4FD50EF27E640FAD3
Session-ID-ctx:
Master-Key: 64DD658D045D5793B2605A9A0C1033F6939708B7977321C3BB32D1E672F88CD5FFBD2C6C83EF1F934A5EE598691AEE96
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 300 (seconds)
TLS session ticket:
0000 - d0 36 c3 45 1b b6 c2 2a-52 5c ea cd 5e c2 52 de .6.E...*R\..^.R.
0010 - 72 8c a5 3e 64 02 8f 13-35 b9 30 be b3 d8 29 a1 r..>d...5.0...).
0020 - e9 36 6f 52 9f 98 91 a3-fe 98 cb 61 42 37 a6 a9 .6oR.......aB7..
0030 - 8d f9 76 be 33 37 17 5a-61 12 7a 94 fb 7f 19 72 ..v.37.Za.z....r
0040 - b5 51 09 80 1a 09 6d 79-74 3c 68 af f6 17 c0 7a .Q....myt<h....z
0050 - cd 94 f2 93 aa 58 ce ed-16 9f 7d be f4 c9 01 54 .....X....}....T
0060 - 63 f3 f5 72 2c 61 82 e5-85 c4 da f0 fe 94 89 5e c..r,a.........^
0070 - 0e 84 d1 69 e4 6c 33 74-e5 87 cb 29 3c e9 0e 8c ...i.l3t...)<...
0080 - ea 58 b4 a3 bc c6 4f 54-94 ab ac 8c 91 68 d8 07 .X....OT.....h..
0090 - a9 7f bd 8a 4c 33 83 8b-86 ea 81 b2 87 f4 6f d2 ....L3........o.
Start Time: 1454796738
Timeout : 300 (sec)
Verify return code: 20 (unable to get local issuer certificate)
---
200 Welcome to XS News
HELP
100 Help follows.
ARTICLE [msgid|number]
BODY [msgid|number]
HEAD [msgid|number]
STAT [msgid|number]
GROUP [newsgroup]
AUTHINFO [user|pass] [credentials]
LISTGROUP [newsgroup]
LIST [overview.fmt|active|active.times|newsgroups|distrib.pats|motd] [pattern]
NEWGROUPS [yyyymmdd] [hhmmss] [gmt]
XOVER [range]
OVER [range]
XZVER [range]
XPAT [header] [range|msgid] [pattern] [pattern..]
XHDR [header] [range|msgid]
HDR [header] [range|msgid]
XZHDR [header] [range|msgid]
NEWNEWS [newsgroup] [yyyymmdd] [hhmmss] [gmt]
XGTITLE [pattern]
MODE [reader]
NEXT
LAST
HELP
QUIT
DUMP
DATE
POST
IHAVE [msgid]
CAPABILITIES
XFEATURE [compress gzip]
.
QUIT
DONE
Although:
So ... the openssl CLI client does support TLS1.2, but the python version doesn't?
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 5:15 pm
by ALbino
sander wrote:FWIW: I checked my own Ubuntu 14.04.3 LTS, and it indeed has TLS1, and not higher:
Code: Select all
2016-02-06 23:06:12,164::INFO::[sabnzbdplus:1367] SSL potentially supported protocols ['SSLv23', 'SSLv3', 'TLSv1']
2016-02-06 23:06:12,164::INFO::[sabnzbdplus:1368] SSL actually supported protocols ['t1', 'v23', 'v3']
... if I only had a xsnews account ... or borrow from the OP ...
Maybe give their Free Trial a shot:
https://www.xsnews.nl/en/freetrial.html
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 5:30 pm
by sander
OK, I got a free xsnews account, set it up in a fresh SABnzbd 1.0.0 RC1 with SSL, on Ubuntu 14.04.3, downloaded it, and I get
Code: Select all
2016-02-06 23:26:40,041::INFO::[decoder:226] <Article: [email protected], bytes=186480, partnum=602, art_id=None> => missing from all servers, discarding
2016-02-06 23:26:40,059::INFO::[decoder:123] CRC Error in [email protected] (1B0D9FBB -> 035C0CC0)
2016-02-06 23:26:40,076::INFO::[decoder:123] CRC Error in [email protected] (14819170 -> D5C82176)
2016-02-06 23:26:40,097::INFO::[decoder:123] CRC Error in [email protected] (9D09219E -> B379215C)
2016-02-06 23:26:40,139::INFO::[decoder:123] CRC Error in [email protected] (8F0E19F4 -> 3E524B1F)
2016-02-06 23:26:40,218::INFO::[decoder:123] CRC Error in [email protected] (1F6B390B -> A2880B87)
2016-02-06 23:26:40,249::INFO::[decoder:123] CRC Error in [email protected] (73454019 -> A641CFE9)
2016-02-06 23:26:40,366::INFO::[decoder:123] CRC Error in [email protected] (B41971F6 -> 0914332A)
2016-02-06 23:26:40,412::INFO::[decoder:123] CRC Error in [email protected] (EC2D999E -> 165F83EB)
2016-02-06 23:26:40,428::INFO::[decoder:123] CRC Error in [email protected] (3595241B -> 0FCB7883)
2016-02-06 23:26:40,499::INFO::[decoder:123] CRC Error in [email protected] (8CC29A4A -> FA684786)
2016-02-06 23:26:40,530::INFO::[decoder:123] CRC Error in [email protected] (B1D96FB0 -> ED6E2F84)
2016-02-06 23:26:40,547::INFO::[decoder:123] CRC Error in [email protected] (BCDBFF0D -> 4BDAFB8C)
2016-02-06 23:26:40,598::INFO::[decoder:123] CRC Error in [email protected] (None -> 24BF257F)
2016-02-06 23:26:40,655::INFO::[decoder:123] CRC Error in [email protected] (6C0E45ED -> 9412FB9E)
2016-02-06 23:26:40,708::INFO::[decoder:123] CRC Error in [email protected] (D0059B40 -> 9A7966BA)
2016-02-06 23:26:40,774::INFO::[decoder:154] Badly formed yEnc article in [email protected]
... but with a successful result (at least: that's what I think):
Code: Select all
sander@haring:~/Downloads/complete/bucks$ ll
total 362444
drwxrwxr-x 2 sander sander 4096 feb 6 23:26 ./
drwx------ 5 sander sander 4096 feb 6 23:27 ../
-rw-rw-r-- 1 sander sander 150508295 feb 6 23:26 big_buck_bunny_480p_surround-fix.1.avi
-rw-rw-r-- 1 sander sander 220514438 feb 6 23:26 big_buck_bunny_480p_surround-fix.avi
-rw-rw-r-- 1 sander sander 97496 feb 6 23:25 big_buck_bunny_480p_surround-fix.nzb
Furthermore, with plain NNTP (no SSL), the result is the same:
Code: Select all
2016-01-08 23:36:17,769::INFO::[decoder:123] CRC Error in [email protected] (9D09219E -> B379215C)
2016-01-08 23:36:18,026::INFO::[decoder:123] CRC Error in [email protected] (EC2D999E -> 165F83EB)
2016-01-08 23:36:18,040::INFO::[decoder:123] CRC Error in [email protected] (B41971F6 -> 0914332A)
2016-01-08 23:36:18,292::INFO::[decoder:123] CRC Error in [email protected] (3595241B -> 0FCB7883)
2016-01-08 23:36:18,362::INFO::[decoder:123] CRC Error in [email protected] (8CC29A4A -> FA684786)
2016-01-08 23:36:18,473::INFO::[decoder:123] CRC Error in [email protected] (B1D96FB0 -> ED6E2F84)
2016-01-08 23:36:18,608::INFO::[decoder:123] CRC Error in [email protected] (BCDBFF0D -> 4BDAFB8C)
2016-01-08 23:36:18,635::INFO::[decoder:123] CRC Error in [email protected] (1F6B390B -> A2880B87)
2016-01-08 23:36:18,661::INFO::[decoder:123] CRC Error in [email protected] (73454019 -> A641CFE9)
2016-01-08 23:36:18,729::INFO::[decoder:123] CRC Error in [email protected] (None -> 24BF257F)
2016-01-08 23:36:18,801::INFO::[decoder:123] CRC Error in [email protected] (6C0E45ED -> 9412FB9E)
2016-01-08 23:36:18,918::INFO::[decoder:154] Badly formed yEnc article in [email protected]
I will now test on a Ubuntu 15.04.
EDIT: Ubuntu 15.04:
Code: Select all
2016-02-06 23:51:25,630::INFO::[decoder:123] CRC Error in [email protected] (B41971F6 -> 0914332A)
2016-02-06 23:51:25,812::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:25,825::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:25,898::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:25,901::INFO::[decoder:123] CRC Error in [email protected] (3595241B -> 0FCB7883)
2016-02-06 23:51:25,918::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:25,923::INFO::[decoder:123] CRC Error in [email protected] (EC2D999E -> 165F83EB)
2016-02-06 23:51:26,795::INFO::[decoder:123] CRC Error in [email protected] (D0059B40 -> 9A7966BA)
2016-02-06 23:51:26,892::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:26,896::DEBUG::[decoder:296] Corrupt header detected => yend: {'part': '6', 'size': '249600'}
2016-02-06 23:51:26,897::INFO::[decoder:123] CRC Error in [email protected] (None -> 24BF257F)
2016-02-06 23:51:27,015::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:27,252::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:27,313::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:27,334::DEBUG::[decoder:103] Decoding [email protected]
2016-02-06 23:51:27,336::INFO::[decoder:154] Badly formed yEnc article in [email protected]
Let's check some more:
Code: Select all
sander@streamer1504:~/Downloads$ cat sabnzbd\ \(1\).log | grep CRC
2016-02-06 23:48:00,007::INFO::[decoder:123] CRC Error in [email protected] (E5EF55CE -> 8726ABD6)
2016-02-06 23:48:00,335::INFO::[decoder:123] CRC Error in [email protected] (E59B5C27 -> 2D56B55E)
2016-02-06 23:48:00,491::INFO::[decoder:123] CRC Error in [email protected] (7B363549 -> E774B9F7)
2016-02-06 23:50:11,082::INFO::[decoder:123] CRC Error in [email protected] (0B5230BA -> E46BA117)
2016-02-06 23:50:11,160::INFO::[decoder:123] CRC Error in [email protected] (86B45542 -> 5CA7D53C)
2016-02-06 23:50:12,503::INFO::[decoder:123] CRC Error in [email protected] (C985DBC2 -> 737C50CC)
2016-02-06 23:50:12,552::INFO::[decoder:123] CRC Error in [email protected] (14BC84ED -> A3B39926)
2016-02-06 23:50:12,735::INFO::[decoder:123] CRC Error in [email protected] (08B08BB8 -> 32FDB6ED)
2016-02-06 23:50:13,887::INFO::[decoder:123] CRC Error in [email protected] (9E822642 -> E0F7435B)
...
Code: Select all
sander@streamer1504:~/Downloads$ cat sabnzbd\ \(1\).log | grep CRC | grep upload.usenetsys.com | wc -l
349
sander@streamer1504:~/Downloads$ cat sabnzbd\ \(1\).log | grep CRC | grep -v upload.usenetsys.com | wc -l
0
Now check the NZB:
Code: Select all
sander@streamer1504:~/Downloads$ cat bucks.nzb | grep "segment bytes" | grep -v upload.usenetsys.com | wc -l
884
sander@streamer1504:~/Downloads$ cat bucks.nzb | grep "segment bytes" | grep powerpost | wc -l
884
So ... the NZB has two kinds of articles
from upload.usenetsys.com: 642 articles, with 349 CRC errors. And: letters, numbers and "$" in the article name
from powerpost2000AA.local: 884, with 0 CRC errors. And: only letters and numbers in the article name.
Strange. Coincidence? Or is there a problem with the upload.usenetsys.com articles?
Maybe there is misccomunication between SAB and xsnews with the $-sign in the article name?
S
Re: "Badly formed yEnc article" error stops download
Posted: February 6th, 2016, 5:54 pm
by 88keyz
I would agree that it seems that the issue is not with SABnzbd and it's more likely related to OpenSSL, the USP or a combination of both. Could be I was the only person affected by this particular issue (system or ISP issue maybe?) in which case it'll be hard to replicate. The only thing that was weird to me was that the issue only started with 0.8.x releases and 0.7.x continued to work perfectly. That was the reason that I assumed the issue was related to SABnzbd but it seems I was wrong. I'll continue to monitor the situation and see if it repeats itself and try to provide more info if I can spot anything that seems relevant to the problem.