Since upgrading to 2.0 early last month, Windows patches have been breaking SAB.
When I installed patches last month, after the subsequent reboot, SAB would no longer load.
The process would run for about 10 seconds then die.
I reinstalled, and life was good.
Well I installed this months patches, and same thing happened.
Process would run for maybe 10 seconds then die.
Reinstalled again.
Unfortunately, I didn't think to grab the log file before reinstalling.
I will reboot in the morning to test/verify whether it's the reboot or patching that's causing it, but, anything else to look at?
Nothing in the Windows event logs stuck out.
I had been running 1.1.1 since December and never had this issue with reboots or patches.
2.0.0 Breaking after Server 2016 Essentials Updates/Reboots
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.
Re: 2.0.0 Breaking after Server 2016 Essentials Updates/Rebo
So it happens just after a reboot. Patching isn't part of it.
I just rebooted the server, and sure enough, SAB process runs for 10 seconds or so then dies.
Nothing in the log file.
Increased log level to debug, but still nothing getting logged.
So it looks like it has to run elevated now? Did that change?
If I start it via Run as Admin it continues to work.
I swear I didn't have 1.1.1 running elevated.
UAC is also turned off already (though it never really turns completely off.)
Launching sabnzbd-console.exe from non-elevated command prompt:
D:\Program Files (x86)\SABnzbd>SABnzbd-console.exe
Error:
Can't write to logfile
I just rebooted the server, and sure enough, SAB process runs for 10 seconds or so then dies.
Nothing in the log file.
Increased log level to debug, but still nothing getting logged.
So it looks like it has to run elevated now? Did that change?
If I start it via Run as Admin it continues to work.
I swear I didn't have 1.1.1 running elevated.
UAC is also turned off already (though it never really turns completely off.)
Launching sabnzbd-console.exe from non-elevated command prompt:
D:\Program Files (x86)\SABnzbd>SABnzbd-console.exe
Error:
Can't write to logfile
Re: 2.0.0 Breaking after Server 2016 Essentials Updates/Rebo
I think something is wrong with your user folder where sabnzbd stores its settings file and log folder.
Either its not writable (anymore) or not called correctly when starting sabnzbd.
Do you run sabnzbd as a Windows service? The upgrade to 2.0.0 requires updating the settings for those.
The default locations of the settings file would be here
https://sabnzbd.org/wiki/advanced/directory-setup
Maybe you can check the permissions of that? Or just delete the whole folder there (after backing up the sabnzbd.ini file, you will lose you're queue and history though!). Sabnzbd will then try to create that folder again, when run normally or when you specify the Config file location on the command line.
Either its not writable (anymore) or not called correctly when starting sabnzbd.
Do you run sabnzbd as a Windows service? The upgrade to 2.0.0 requires updating the settings for those.
The default locations of the settings file would be here
https://sabnzbd.org/wiki/advanced/directory-setup
Maybe you can check the permissions of that? Or just delete the whole folder there (after backing up the sabnzbd.ini file, you will lose you're queue and history though!). Sabnzbd will then try to create that folder again, when run normally or when you specify the Config file location on the command line.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: 2.0.0 Breaking after Server 2016 Essentials Updates/Rebo
I actually have sab installed in D:\Program Files (x86) which is the same as where 1.1.1 was installed (I swear it was, anyway.)
It is not, yet, running as a service.
Process runs under my Admin account. Admin account has full control perms, but I know Program Files folders are protected folders.
Or maybe... 1.1.1 was installed in appdata? Last log entry in appdata is from December, so I'm not sure.
Any way... looks like the install location is different this go around. I will dig in to running it as a service, as that should mitigate the issue (if it's running as SYSTEM rather than a user acct, that should bypass protected folder restrictions.)
All else fails, I'll move the log file location.
Thanks.
It is not, yet, running as a service.
Process runs under my Admin account. Admin account has full control perms, but I know Program Files folders are protected folders.
Or maybe... 1.1.1 was installed in appdata? Last log entry in appdata is from December, so I'm not sure.
Any way... looks like the install location is different this go around. I will dig in to running it as a service, as that should mitigate the issue (if it's running as SYSTEM rather than a user acct, that should bypass protected folder restrictions.)
All else fails, I'll move the log file location.
Thanks.