PC shutdown doesn't work always

[switch]

There could possibly be a program running that is stopping the shutdown. Maybe we should use the -f flag to force the shutdown.

Edit: looks like we currently do try and force a shutdown.
You are not running sabnzbd as a service or anything are you?

[Peter_Pan]

Nope, I do not have other apps running other than the ones XP loads.
I am not running sabnzbd as a service.

cherrypy doesnt shut down when it happens.
Dunno if that gives you a clue.

Should I be able to see something in even viewer about the system trying to shut down?
Nothing is there.

BTW:
I just tried on my laptop where I just recently installed SP3.
Now my laptop doesnt work either.
Must be SP3 then ?

Just tried with a reinstall - which you said wouldnt work.
And it didnt 

[shypike]

cherrypy doesn't shut down when it happens.

CherryPy shutdown is logged in cherrypy.log, not in the regular log file.

Last advice I can give you is to use Steve Gibson's wizmo utility (http://www.grc.com/wizmo/wizmo.htm)
and call it with this script:

Code: Select all

@echo off
echo Shutdown was here >c:\temp\shutdown.log
wizmo quiet shutdown!

Don't forget the exclamation mark.
Put this script in the script folder and set it for end-of-queue.
Check the shutdown.log file to see whether it was called at all.
This way we will know whether it's an end-of-queue problem or
a shutdown problem. You may need to put shutdown.log somewhere else.

BTW there must be dozens of alternative utilities for this.

[Peter_Pan]

I know about cherrypy.log and nothing is in there about a shutdown.

And I can browse the 'server' when sabnzbd is supposed to have been shut down.
Seems like everything shuts down except cherrypy.

I will try Steve's wizmo.
Thx.

[shypike]

After some testing, what I see is.

CherryPy does not sign off in the log file, this because SABnzbd terminates
without specifically stopping CherryPy, but this is OK.
If you use the Smpl or Plush skins, you will be tempted to think that SABnzbd
still works, this is because these skins have a life of their own. They also are not
notified that SABnzbd has actually stopped.
On Vista I see a 10 second delay between SABnzbd stopping and the OS actually
going down, I guess that's just the OS doing its thing.

BTW: the shutdown method that SABnzbd uses, is rather blunt.
Maybe we should use the Windows built-in shutdown command line utility.
That will show a 30 sec warning before actually shutting down and can be cancelled.

[Peter_Pan]

I have no idea about how to test if cherrypy has shut down or not.

Im using the default skin, and I can browse the pages, change settings, clear the log and even send myself a test email.

But if you say so, it must be true... 

EDIT:
Ok... its because the sabnzdb process doesnt quit.
When I change a setting, sabnzbd wakes up and starts processing again:

Shutting down...
2008-06-14 19:28:47,019::INFO::[postproc] Queue has finished, launching: (None)



2008-06-14 19:28:47,289::INFO::[nzbqueue] Saving queue
2008-06-14 19:28:47,299::INFO::[sabnzbd] Saving data for queue7.sab in D:\Auto\cache\queue7.sab
2008-06-14 19:28:47,299::INFO::[sabnzbd] Saving data for bytes7.sab in D:\Auto\cache\bytes7.sab
2008-06-14 19:28:47,299::INFO::[sabnzbd] Saving data for rss_data.sab in D:\Auto\cache\rss_data.sab
2008-06-14 19:28:47,309::DEBUG::Stopping scheduler



Starting up...
2008-06-14 19:30:48,354::DEBUG::username ->
2008-06-14 19:30:48,354::DEBUG::password -> ******
2008-06-14 19:30:48,354::DEBUG::check_new_rel -> 1
2008-06-14 19:30:48,354::DEBUG::replace_spaces -> 0
etc...

But maybe thats by design?
If the PC is set to shut down anyway there is no need to shut down sabnzbd?

-----

Ok, enough of this!

I can live without knowing whats wrong. No biggie!

Keep up the good work!

[Peter_Pan]

We are still looking into these reported problems

* End-of-queue shutdown/standby/hibernate does not always work


Look no further!
Works here in RC3 

I didnt have this line in RC2:
"2008-06-18 19:36:32,717::INFO::All processes stopped"

[shypike]

The line is new, to have a proper message marking end-of-processes.
So I will be happy when it works all of the time