Page 1 of 1
Latest windows update broke Sab
Posted: December 12th, 2020, 5:29 am
by lamergamer
Or at least i think it's the latest update.
Sab version 3.1.1.
Symptom: Sab keeps restarting, does not download or is gust super unstable.
All happened after Thursday i installed the latest windows updates i got offered: KB4592438, KB4593175 (security), KB4562830 (feature).
The log shows this after thursday. All was fine before.
well no error log since im new and can't post links.....
Starting the console version gives this error. Then crashes.
well no error post either since im new and can't post links.....
Re: Latest windows update broke Sab
Posted: December 12th, 2020, 6:01 am
by sander
post the sab log on pastebin, and post the pastebin URL with spaces around the dots here ...
Re: Latest windows update broke Sab
Posted: December 12th, 2020, 6:08 am
by Coldashbin
Since KB4592438 update on Thursday, I am unable to get SABNZB (3.1.1 [99b5a00]) working. The servers will not connect.
I tested the servers using another usenet download client and they are working fine, leading me to believe the issue is with SABNZB.
testing the server connections in SABNZB gives the below error:-
[Errno 10061] (10060, '[WinError 10053] An established connection was aborted by the software in your host machine')
Re: Latest windows update broke Sab
Posted: December 12th, 2020, 6:26 am
by lamergamer
https : // pastebin . com/z6xmZeUu
To add. I paused the downloads in the queue (a very large one was on when it last worked, i shut computer down in the evening, updated win in the morn, hasn't worked ever since; and it's 98% complete) and it did not crash / do the restart thing it does otherwise. Dloads are paused atm.
Re: Latest windows update broke Sab
Posted: December 12th, 2020, 7:33 am
by sander
So
https://pastebin.com/z6xmZeUu
a repetition of:
Code: Select all
2020-12-12 12:23:34,343::WARNING::[_cplogging:213] [12/Dec/2020:12:23:34] ENGINE socket.error 10058
Traceback (most recent call last):
File "cheroot\server.py", line 1267, in communicate
File "cheroot\server.py", line 702, in parse_request
File "cheroot\server.py", line 743, in read_request_line
File "cheroot\server.py", line 300, in readline
File "_pyio.py", line 557, in readline
File "cheroot\makefile.py", line 420, in read
File "_pyio.py", line 1067, in read
File "_pyio.py", line 1107, in _read_unlocked
File "socket.py", line 669, in readinto
BrokenPipeError: [WinError 10058] A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call
Might be (Windows' internal) firewall. Windows ... so start with a few Windows reboots. If that does not solve it, temporarily disable your Windows firewa// & virusscanner.
Code: Select all
Console
Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.py", line 932, in _bootstrap_inner
File "sabnzbd\downloader.py", line 637, in run
File "sabnzbd\nzbstuff.py", line 924, in update_download_stats
TypeError: can't concat int to bytes
That is indeed a SABnzbd problem.
https://github.com/sabnzbd/sabnzbd/blob ... #L916-L923
Weird that that pops up now. But first solve the Windows socket problem.
Re: Latest windows update broke Sab
Posted: December 12th, 2020, 10:10 am
by safihre
To solve the last problem, you will have to delete the totals10.sab in your SABnzbd config directory.
Re: Latest windows update broke Sab
Posted: December 12th, 2020, 10:58 am
by lamergamer
Seems disabling firewall helped. Managed to download a bunch of things. It still restarted a couple of times itself, but then stabilized. I'll update tomorrow, when i have reenabled the firewall, see what happens. I will delete the totals10.sab file as well. Thanks.
Re: Latest windows update broke Sab
Posted: December 13th, 2020, 11:13 pm
by lamergamer
It seems resetting windows firewall (and my router while i was at it, if ever that helped) solved the issue. I guess something changed in there with the update (since it was a security update) and that just broke Sab. And i bet deleting that file helped as well. Not sure which was the more important of the fixes but it's fixed. Thank you gents! Good luck!