SABnzbd Forums

Version: 0.5.0 beta 5
OS: windows 7 rtm
Install-type:Windows zip
Skin (if applicable):Classic - Darkblue
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? Yes
Browser Version:- Firefox 3.5.6

hi all, i've noticed that i cannot shutdown sabnzbd by clicking the shutdown button on the "Home" tab when something is in the Queue, if i try and hit shutdown then i just get the hourglass, if i hit refresh on the browser then it stops hourglassing and goes back to displaying the "Home" tab.

i believe this was a problem with version 0.4.x in that you needed to pause before you could shutdown, however i thought i read somewhere that this was getting reworked in the later 0.5.x version so that pausing wouldn't be necessary or is this still true for version 0.5.x?

If you have a large memory cache, SABnzbd must flush this to disk.
This can delay the shutdown considerably.
If you run SABnzbd on your local system, you should try running
SABnzbd-console.exe instead of SABnzbd.exe.
This will give you the black console window showing logging information
(also set logging level to Info or  Debug on the Connections page).
This may show where the program is stuck (if at all).

shypike wrote: If you have a large memory cache, SABnzbd must flush this to disk.
This can delay the shutdown considerably.
If you run SABnzbd on your local system, you should try running
SABnzbd-console.exe instead of SABnzbd.exe.
This will give you the black console window showing logging information
(also set logging level to Info or  Debug on the Connections page).
This may show where the program is stuck (if at all).

ok ive done as suggested and am eventually getting the following output displayed in my browser:-

Unrecoverable error in the server.
Traceback (most recent call last):
  File "cherrypy\_cpwsgi.pyo", line 79, in setapp
  File "cherrypy\_cpwsgi.pyo", line 219, in get_response
  File "cherrypy\_cprequest.pyo", line 579, in run
TimeoutError

i assumed that the delay was due to the cache, however ive turned off the cache completely and im still getting the long wait before shutdown, i hope the error above gives you some insight, although i fear all its telling you is its timed out?.

paul.

Very odd, it's the internal webserver getting impatient.
We need to look again at the shutdown method.
One would say shutting down is trivial, but it isn't