Support Forum

Thanks safihre! Cheers!

Awesome. Thank you both for your help!

Thank you for your hard work! Glad you guys were able to identify the bug. Looks like the response was prematurely parsed. I'll turn off the checker now, but I'm not sure whether it happens outside of checking as well. Also, I'm not sure whether the \x00 reported by sander is related/isolated cause ...

garbage in the answer in the precheck: thousands of \x00 (limited to 80 characters in logging below) 2024-03-11 20:17:12,608::DEBUG::[newswrapper:97] SJ 200: bytearray(b'223 0 <JxFgMzBwLqVoRcPuJzHoSgFy-1658672651406@nyuu>\r\n@premiumize.me (no posting)\r\n\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0...

I'll try tomorrow night. I'm away from my home network atm.

I didn't notice them because it didn't freeze sabnzbd. Or did it in your case?

The only error that resulted to a froze and require restart was the 222 status code.

But this only happens when it's pre-checking, right? I'll turn of checking for now, and report to them.

I'm using them because they bundle with a bunch of other services that I use. Thank you Sander!

This happens only at the beginning of a job, right? I can drop a support ticket and let them know their downloads are 400-ing in the beginning.

Is it possible that this behaviour is interfering with the checking script?

Ignore my hypothesis above about proxmox/docker! Because: With "Check before download" on, I do get the Traceback ... in the checking phase: 2024-03-11 18:05:54,488::DEBUG::[downloader:744] Article <hcqsDHTqW6xYgZU7ss@d106420829d7979391nvei38GALVE6L35cyB8> is present 2024-03-11 18:05:54,4...

can you run SABnzbd on a PC/Mac, and do downloads... I'm away from my home setup until tomorrow evening. I'll try again when I get back. As mentioned, I also couldn't reliably reproduce the problem. Based on observation, it seems to happen more often or predominately on large jobs (larger than 10G)...

Thanks for the explanation. It only happens sometimes, making it very hard to reproduce and troubleshoot. It started just last week, and I've been using the same newsgroup for over 5 years now. Not sure if it's by fluke; just an observation: #1 When the error shows up, I restart the entire container...

it's usenet.premiumize.me

Been using this setup for many years; started getting these errors last week. Nothing resumes until i restart the container. I'm out of ideas. Need some help. Things I've changed recently: - moved from unraid docker to debian docker - started using sabnzbd-notify(dot).py to communicate with Slack - ...