SABnzbd Forums

Posted: **June 11th, 2018, 10:22 am**

Hmmm, spoke too soon, the helper service can no longer restart the service, the log in debug mode shows it stops the service which I confirm, but the request for a restart never finishes:

Code: Select all

2018-06-11 17:13:15,848::INFO::[__init__:772] [SABnzbd.pyo.main] Performing SABnzbd shutdown
2018-06-11 17:13:15,848::INFO::[_cplogging:219] [11/Jun/2018:17:13:15] ENGINE Bus STOPPING
2018-06-11 17:13:15,848::INFO::[_cplogging:219] [11/Jun/2018:17:13:15] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 9090)) already shut down
2018-06-11 17:13:15,848::INFO::[_cplogging:219] [11/Jun/2018:17:13:15] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) already shut down
2018-06-11 17:13:15,848::INFO::[_cplogging:219] [11/Jun/2018:17:13:15] ENGINE Bus STOPPED
2018-06-11 17:13:15,848::INFO::[_cplogging:219] [11/Jun/2018:17:13:15] ENGINE Bus EXITING
2018-06-11 17:13:15,848::INFO::[_cplogging:219] [11/Jun/2018:17:13:15] ENGINE Bus EXITED
2018-06-11 17:13:15,849::INFO::[SABnzbd:1548] Asking the SABHelper service for a restart

Any way to get more logging to help see what it's doing? BTW, the service account I use is not an admin on the server, it never has been nor should it need to be as it has full rights to what it needs on the server and on the remote server it moves all my files to - I suspect that's why having the helper service as "local system" was fine before.

Posted: **June 11th, 2018, 11:42 am**

I don't have Windows Server so I can't reproduce..
But you say you still get the error on startup?

Posted: **June 12th, 2018, 1:35 am**

safihre wrote: ↑June 11th, 2018, 11:42 am I don't have Windows Server so I can't reproduce..
But you say you still get the error on startup?

Only if I use the domain account for both services. If I switch the helper back to "local system" as it was before then I get the message at start-up.

I've also discovered that either way, "local system" or account, the helper service can only stop the main service and never manages to restart it. I have to access the server and manually start it up again. This used to work before.

Posted: **June 12th, 2018, 1:41 am**

Seems Windows 10 put many restrictions on Mailslot communication, but I don't know why/what and how to really work around it..

Posted: **June 12th, 2018, 1:52 am**

Well, if the changes were to fix issues in later versions of Windows, shouldn't they only be applied to them?

Previous versions of SABnzbd were fine, and as it stands I won't be able to upgrade to a newer Windows build until Server 2019 is released later this year.

SABnzbd Forums

Error - Cannot reach the SABHelper service

Re: Error - Cannot reach the SABHelper service

Re: Error - Cannot reach the SABHelper service

Re: Error - Cannot reach the SABHelper service

Re: Error - Cannot reach the SABHelper service

Re: Error - Cannot reach the SABHelper service