However, I tried it again a few minutes ago. So I think this wasn't a "temporary issue" of the Usenet provider. I tried NZBVortex right in advance and directly after SABnzbd failed and it worked flawlessly both times. However, NZBVortex succeeded while SABnzbd failed. It was the same NZB and it was the same Usenet provider (same host, port, credentials) and both clients (NZBVortex and SABnzbd) had to repair the downloaded files. What's weird is that I've used the exactly same NZB and Usenet providers with NZBVortex where it worked, while SABnzbd had issues :/ Sometimes par2 files are malformed in such a way that SABnzbd is thrown off-track.Ĭan you also email which Usenet provider(s) you're using? It could be that different parts are missing on different servers. There were malformed articles and repair was needed. Shypike wrote:I downloaded your NZB with both 0.7.20 and 0.8.0Beta3.īoth succeeded, resulting in an oddly named MKV file.
Is it possible to switch back from develop to master? SABnzbd runs on a Debian machine in a Docker container with Python 2.7.9.Īny things I can try to fix this or narrow down the issue? I'm currently running on the develop git tree on commit 583c233bd282cfef3480948c69eef0055e1828bd. However, NZB Vortex always succeeded without any problems.Īs I already wrote, it's always the same NZB file and the same Usenet server in SABnzbd and NZB Vortex.
Nzbvortex crashing mac download#
Unfortunately SABnzbd wasn't able to download & repair my files in all cases.
0 kommentar(er)
