SABnzbd Forums

SABnzbd version 0.5.6 (Windows version)

Hello,

I like the way my PC is going to standby after the queue is empty. But sometimes I work on this PC and suddenly goes in standby mode.
So I created a custom Standby script (AutoIt script). The script gives a message the PC goes in standby in one minute.
I placed the Auto standby.exe into the script-folder and selected it as the 'On queue finish' option.

But when the queue finish, nothing happen  When I manual start the exe, it works fine.

This is the log output:

---

2011-02-28 20:16:35,233::DEBUG::[__init__:649] Saving data for postproc1.sab in C:\Documents and Settings\Administrator\Local Settings\Application Data\sabnzbd\cache\postproc1.sab
2011-02-28 20:16:35,250::INFO::[postproc:574] Queue has finished, launching: (Auto standby.exe)
2011-02-28 20:16:35,250::INFO::[__init__:597] Spawning external command C : \ P r o g r a m " " F i l e s \ S i c k b e a r d \ a u t o P r o c e s s T V \ A u t o " " s t a n d b y . e x e

---

Are those spaces normal?

Is there anything I did wrong?

Is your normal scripts folder "c:\Program Files\Sickbeard\AutoProcessTV".
It should be entered without quotes in Config->Folders.
The spawning external command should look like:
C:\Progra~1\SICKBEAR~1\AutoPr~1\AUTO~S~1.exe
(This because due to a bug in the Python runtime, we need to resort to the old 8.3 shortened paths.)

Hi Shypike,

Yes, "c:\Program Files\Sickbeard\AutoProcessTV" is the script folder set in the config (without quotes).

I made a folder in the root of C called 'SScripts' and renamed the scipt from 'Auto standby.exe' to 'Standby.exe'.
Changed the location of the script folder (Post-Processing Scripts Folder:) to C:\SScripts

Still the same problem. What could be causing this?

---

2011-02-28 20:54:39,530::DEBUG::[__init__:649] Saving data for postproc1.sab in C:\Documents and Settings\Administrator\Local Settings\Application Data\sabnzbd\cache\postproc1.sab
2011-02-28 20:54:39,530::INFO::[postproc:574] Queue has finished, launching: (Standby.exe)
2011-02-28 20:54:39,530::INFO::[__init__:597] Spawning external command C : \ S S c r i p t s \ S t a n d b y . e x e
2011-02-28 20:54:40,250::DEBUG::[bpsmeter:60] bps: 532776.502965

---

Just a gamble.
What happens if you make a little batch file to call the exe file?

I'm sorry.

---

2011-02-28 23:05:39,592::DEBUG::[__init__:649] Saving data for postproc1.sab in C:\Documents and Settings\Administrator\Local Settings\Application Data\sabnzbd\cache\postproc1.sab
2011-02-28 23:05:39,592::INFO::[postproc:574] Queue has finished, launching: (Standby.bat)
2011-02-28 23:05:39,592::INFO::[__init__:597] Spawning external command C : \ S S c r i p t s \ S t a n d b y . b a t

---

It has something to do with the On Queue Finish option.
When selecting the Standby.exe on a new added File (on the Home tab), it works perfect!

---

2011-02-28 23:08:44,265::INFO::[newsunpack:127] Running external script C:\SScripts\Standby.exe(C:\Documents and Settings\Administrator\Mijn documenten\downloads\complete\00-the_separation-retire_your_engines-2008.m3u.1, 00-the_separation-retire_your_engines-2008.m3u.nzb, 00-the_separation-retire_your_engines-2008.m3u, , None, alt.binaries.inner-sanctum, 0)
2011-02-28 23:08:45,000::DEBUG::[bpsmeter:60] bps: 4511159.87346

---

WTF?
Sadly, I have no explanation for this.

Goodmorning from here 

Today I will try to test it on a different PC to see if the same problem occur.

Keep you updated.

Just tested the same script from the same folder on another PC (pc at work).

The same thing happened.

---

2011-03-01 09:00:10,342::INFO::[postproc:574] Queue has finished, launching: (Standby.exe)
2011-03-01 09:00:10,342::INFO::[__init__:597] Spawning external command C : \ S S c r i p t s \ S t a n d b y . e x e

---

Could you please look into the code.

Both PC's where running Windows XP SP3 (32 bit)

Can you email me a copy of the sabnzbd.ini file, so I can check?
It needs to be from a system where it fails.
Remove all passwords first and send it to bugs at sabnzbd.org

Just send my configuration file.

The "queue_complete" field is empty.
So this INI file doesn't even launch an end of queue script.
Is this the right INI file?

Oh, sorry. I cleared the On queue finished option to test the On download complete setting.

This is the setting in the ini file when the On queue finisdhed is set to 'Standby.exe'.

queue_complete = script_Standby.exe

I will email you the complete script.

Well after some investigation, I'm the one to say sorry.
The end-of-queue function simply doesn't work on Windows
due to a (rather silly) programming error.

If you really need this feature you should switch over to 0.6.0Beta2.
Or have a few day patience and wait for Beta3, which will solve a number of Beta2 issues.

Thanks for the investigation, shypike!

I can wait a few days for beta3

Thanks again.