Computer: Mac Pro (mid 2010)
OS: MacOS High Sierra 10.13.6
I've been using SABNZBD for years on this machine, which hosts pyMedusa, SABNZBD, and Plex. A few days after upgrading from 3.3.0 to 3.3.1, the system started crashing the SABNZBD process every few seconds. The logs didn't indicate anything, so I removed the INI file and set everything up from scratch for the first time in years. I let the system run on 3.3.1 for a few days, and it happened again - and I had to set up from scratch again, and this time I made a copy of the INI afterward.
After a few days, the SABNZBD process once again started crashing every few seconds. So I went ahead and deleted the 3.3.1 version and installed a 3.3.0 version. I copied in the INI and started the process, and it's been running for two weeks without issue. So is there something in 3.3.1 that's causing INI corruption? Or something else?
Upgrading to 3.3.1 causes corruption
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
What is this INI corruption you're talking about?
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
I don't know what the corruption is, other than it's happening on Mac OS High Sierra with SABNZBD 3.3.1. Whenever I install 3.3.1 over 3.3.0 and let it run for a couple of days, it'll cause the app to crash repeatedly and give me a ton of connection errors until I delete my INI and recreate it.
Re: Upgrading to 3.3.1 causes corruption
after such an app crash, and allegedly a corrupted INI: open the file sabnzbd.ini with a plain text editor. What do you see?
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
I did a diff on a corrupted INI and a working INI, and the only thing that I can see different is my new provider (which I added a few days ago). That new provider is working fine under 3.3.0, so I don't think that's the cause of the corruption.
I grabbed a bunch of lines from the start of the application through a full crash. Link: https://pastebin.com/yjBZUwVD
I grabbed a bunch of lines from the start of the application through a full crash. Link: https://pastebin.com/yjBZUwVD
Re: Upgrading to 3.3.1 causes corruption
So there is no corruption of your INI file, right?
Your sabnzbd.log is interesting:
10.0.1.248?! Did you fill that out out at http://127.0.0.1:8080/sabnzbd/config/general/#host ? If so, don't do that; fill out 0.0.0.0
#BADHOST
That is bad. Set your logging to +Debug via Wrench -> Status -> right lower corner: +Debug.
Then run SABnzbd again. Wait until it stops, and post the sabnzbd.log again.
Your sabnzbd.log is interesting:
Code: Select all
2021-07-15 06:07:01,999::INFO::[_cplogging:213] [15/Jul/2021:06:07:01] ENGINE Serving on http://10.0.1.248:8080
#BADHOST
Code: Select all
2021-07-15 06:07:32,430::INFO::[__init__:1007] Restarting because of crashed downloader
Then run SABnzbd again. Wait until it stops, and post the sabnzbd.log again.
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
Yeah, I filled that out. I've had it there for a while because at one time SABNZBD would connect through WiFi and not Ethernet, and 10.0.1.248 is the static IP on my LAN that I assigned to this machine. I believe there's a setting now for which interface to use (though that may be Plex, I can't remember) so I can remove this.
In order to do the debug, I'll have to upgrade to 3.3.1 again, then wait a few days for it to start crashing.
In order to do the debug, I'll have to upgrade to 3.3.1 again, then wait a few days for it to start crashing.
Re: Upgrading to 3.3.1 causes corruption
Ah, then you know what you're doing and you can keep it that way.walterhpdx wrote: ↑July 20th, 2021, 3:24 pm Yeah, I filled that out. I've had it there for a while because at one time SABNZBD would connect through WiFi and not Ethernet, and 10.0.1.248 is the static IP on my LAN that I assigned to this machine. I believe there's a setting now for which interface to use (though that may be Plex, I can't remember) so I can remove this.
OK.walterhpdx wrote: ↑July 20th, 2021, 3:24 pm In order to do the debug, I'll have to upgrade to 3.3.1 again, then wait a few days for it to start crashing.
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
It just started crashing - so it took 6 weeks to start. Logs coming.
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
The application is crashing every 30-90 seconds now. Just started after a reboot.
Link to pastebin: https://pastebin.com/1Nm5cGCX
Link to pastebin: https://pastebin.com/1Nm5cGCX
Re: Upgrading to 3.3.1 caused "[__init__:1007] Restarting because of crashed downloader"
2021-08-22 08:26:01,582::INFO::[__init__:1007] Restarting because of crashed downloader
and a bit earlier:
2021-08-22 08:25:33,559::INFO::[__init__:1133] Could not determine system certificate validation quality due to connection problems
Anyway: if you go back tot SABnzbd 3.3.0, is it OK again?
and a bit earlier:
2021-08-22 08:25:33,559::INFO::[__init__:1133] Could not determine system certificate validation quality due to connection problems
Anyway: if you go back tot SABnzbd 3.3.0, is it OK again?
-
- Newbie
- Posts: 8
- Joined: July 17th, 2013, 8:45 pm
Re: Upgrading to 3.3.1 causes corruption
Yes. I ran 3.3.0 from the time it was released until 3.3.1 was released without issue. It's only with 3.3.1 that this happens, and it starts a few weeks into it.
Re: Upgrading to 3.3.1 caused "[__init__:1007] Restarting because of crashed downloader"
OK, go back to 3.3.0, so that 1) you have a stable environment and 2) make sure 3.3.0 does not cause a "crashed downloader" after weeks of usage.