Sickchill: SickRage service stuck in "Paused" state

[loryans]

Before submitting your issue:

Enable debug logging in SickRage settings, reproduce the error (be sure to disable after the bug is fixed)

Branch/Commit: Not sure, used Windows Installer. SickRage was set to stable branch.
OS: Windows 10 Insider build 15019
What you did: Nothing (seriously). Has been running for months without issue.
What happened: Came home one day and the service is stuck on "Paused" state. Have uninstalled, rebooted, re-installed, no change. Windows Event Viewer doesn't give any useful information.
What you expected: the service to start

sickrage eventlog.txt

Logs:

PASTE LOGS HERE

[SickRage2]

Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked

• [ ] Include basic information: Branch/Commit, OS, What you did, What happened, What you expected
• [ ] Enable debug logging (be sure to disable after the bug is fixed)
• [ ] Post debug logs, either inline (for smaller logs) or using gist

Please make sure you also read how to create an issue and followed all of the steps.

The title should describe your issue. Having "SR not working" or "I get this bug" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.

Sometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.

Thanks!

[loryans]

I ended up completely uninstalling and re-installing manually, same problem.
Running SickRage manually appears to work, so I'm guessing the cause is the nssm service utility.

[miigotu]

@VinceVal any idea?

[epicns]

Same issue here. This is definitely caused by something in the latest Windows Insider builds... I rolled back and SickRage was working properly... decided to skip build 15019 and when the next build (15025) updated again the SickRage service is stuck paused. I compared before/after on the security rights to my sickrage installation and they are the same before/after the new build and I also verified that my environment variables are the same after the build update and they are. Also tried running the service as Network Service as well as myself (member of the "Administrators" group) with the same result of it failing to start properly and sticking at paused.

[loryans]

Good to know. Interestingly it didn't happen straight after the upgrade to 15019 - more like about 2-3 days later.
I've since upgraded to 15025 but haven't tried to test it, as I've gone the VBS script method for now.

[PlaceboPRS]

"VBS script method"? Can you specify please? I'm another on 15025 unable to start Sickrage the regular way :(

Edit: googled and found this guide http://www.htpcguides.com/install-sickrage-windows-usenet-torrent-tv/ and that worked for me, thanks for the hint!

[miigotu]

Tried changing the user the service runs as to your normal user? Maybe the network user is no longer part of Everyone?

[loryans]

@PlaceboPRS yep, that's the one I was referring to. :-)
@miigotu it doesn't appear to be a permissions thing, otherwise something would be logged somewhere. Also I doubt MS would make such a significant change to security permissions between builds without documenting it, but I will check.

[miigotu]

I was just saying, because it makes sense for the network user to not have access to your user files. imho they SHOULD change that.

[loryans]

Is anyone still seeing this issue on 15031? I haven't tried to move away from the VBScript method yet.

[PlaceboPRS]

Yes I tried to set it up again last night as a service and it's exactly the same problem in 15031 as before :( Back to the VBS.

[marc-d]

Same problem - Windows 10 Insider Preview 15031 (rs2_release)

Glad I finally checked here - I've tried everything to fix this and had no luck. Guess I'll look into VBScript.

[loryans]

I'm actually finding that python.exe crashes every day or so. Anyone else experiencing that?

[PlaceboPRS]

Yes same thing here, once a day it crashes with a pop up showing the crash error and Sickrage has to be manually restarted with the VBS.

[Holand]

Same problem here (Windows 10.0.15042). I downloaded the latest nssm.exe (2016-09) which didn't help. Somehow the vbs solution doesn't work for me either. Any ideas here?

[miigotu]

Unless one of you can find a solution, we won't be making changes to accommodate unreleased versions of windows. This is due to a windows bug, not SR. The vbs works and it also works from CLI. I tried to figure it out by installing a windows vm and I cant see anything that causes it, it just doesn't work.

[PlaceboPRS]

Managed to grab a screenshot of the Python pop up error:

[loryans]

I had to do a full rebuild of my media PC and installed Win10 15042. Same problem with the installer.
Did full uninstall and then manual component install - same problem with Python crashing.
I think I'll just set up a scheduled task to kill the process and restart it manually every 24 hours.

[muheras]

This looks like it has now migrated to a normal Windows 10 install. I'm getting it on my non-insider build of 14393.969

[sharkykh]

@muheras Try running SickRage manually. If it doesn't load then you were probably affected by a bad update.
Follow these instructions

[muheras]

@sharkykh Yep that fixed it, who knows how it happened but thanks for pointing me to the fix.

[scott3n2]

@SickRage2 There is a simple fix to this if users are on Windows 10 Creators Update. Go into the Edit SickRage Service and remove the check by Console window and then click Edit Service. Then you can go to your services and stop and start the SickRage service.

You can also modify this by adding DWORD value AppNoConsole in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSickRageParameters and setting the Hexadecimal value to 1.

[sharkykh]

@scott3n2 Thank you!
Ping @loryans @PlaceboPRS @marc-d @Holand @DarkDivide - Please test this suggested fix.

[DarkDivide]

Awesome, i applied the suggested registry tweak and restarted the service and its working normally now.

Great work @scott3n2 Thank you!

[JeremyTBradshaw]

Nice fix! I didn't noticed that I had the issue for the last couple of days or so, until tonight, lucky me it was already solved here.

[loryans]

Bingo, worked a treat. Thank you!

[mynkow]

My SickRage died after installing the new big windows update OSBuild=15063.138 Version=1703

I can confirm that the registry fix is working for me. 10x

[ChrisMoriarty]

The console window checkbox seems to have worked. The sickrage service was indeed able to start. Thanks!

[guypepper]

I have the same problem service remains paused I tried clicking the console window and adding the 1 hexdecimal and reinstalling a few different ways but am having no luck anyone got any other ideas?

win 10
15063.608