0.6.6 Immediate Shutdown

[MarcD]

Hi,

I just installed 0.6.6 on OSX Lion / safari 5.1 and can't get it to run.
My Growl notification gives 2 messages: Sabnzb+ is running, immediately followed by Sabnzb+ has shut down.
Normally, I have it to shut down once my last queue item is completed, now I can't even access my settings as it is already "disconnected from the localhost"

Any clues on a solution?
- already tried reinstalling
- also reinstalled the 0.6.6 snow leopard version, same issue...

Thanks!

[shypike]

The Leopard version won't help you, re-install the other one.
Check the host name you used.
Use TextEdit to open this file and look for the line "host =" and "port = ",
change it to a safe value like "host = 127.0.0.1" and "port = 8080".
/Users/user/Library/Application Support/SABnzbd/sabnzbd.ini

[leronb]

I also have immediate shutdown right after launching sabnzbd 6.6. I am using OSX 6.8. The
sabnzbd.ini file is as you said in your response to MarcD. I went back to 6.5, which works perfectly and will wait for a version without this bug.

[leronb]

Sorry I mean OSX 10.6.8 (Snow Leopard).

[shypike]

Without more info, this bug is not going to be solved, since you're the only one reporting it.
Can you page through the log file a bit, so get some more info.
It's here:
/Users/user/Library/Application Support/SABnzbd/logs/sabnzbd.log
Remove the file, try to start up SABnzbd again and then inspect the file.
Otherwise, email it to bugs at sabnzbd.org

[MarcD]

Thanks for your quick replies.
Although I'm a Newbie to this forum, I am surely not one on Mac OSX... I have been searching all around it for the log file to send you some more details. Guess the hint is here as I could not find the log file, nor any SABnzbd directory in Application Support. Hints to me something might have gone wrong with the installer!

I'll follow leronb's option to roll back to 0.6.5. now.

good luck on tracing this bug, sorry I can't be of any more help

[shypike]

Do you happen to have "Shutdown SABnzbd" as an end-of-queue action?
There's a bug in 0.6.6 that can make it exit immediately the next time you start it.

[grasfer]

Do you happen to have "Shutdown SABnzbd" as an end-of-queue action?
There's a bug in 0.6.6 that can make it exit immediately the next time you start it.

Hello, i enabled shutdown sabnzbd yesterday night, and today when computer started and always like 1-2min after the computer shutdown again.

I then rememberd sabnzb and i had it in autostart so i removed it from there and now computer starts fine.

So i guess sopmething is wrong with Shutdown Sabnzb

Also if i start sabnzbd now i get a windows notification about windows shutting down in 1min etc.

edit: if anyone need to fix this behaviour, open up sabnzbd.ini and look for 'queue_complete = shutdown_pc' .
Remove that line and now sabnzb should start again

[shypike]

The problem is that the behaviour of the end-of-queue action changed
from "when queue becomes empty" to "when queue is empty".

[ThaMan]

Also have this problem with version 0.6.6 en Mac OS Lion
i also went back to 0.6.5 because it just isn't fixable !!!

I cant find my ini file of SABNZB to change it, and this also means that you have to change that ini file every time you want to start the program so this actually a NO OPTION
I always set a timer to start downloading files and i also set "shutdown" when done. The next day i want to download something it immediatly shuts down my Mac.

So i'm also waiting for a kinda fix !
Because it is a nasty bug

[shypike]

There will be a new release tonight.

[ThaMan]

Superb Shypike, because i was trying to get it to work as we speak
found the ini file and i have to change it every time to make it work again

When i choose "Shutdown Program" it immediatly closes the program at startup
when i choose "Shutdown Pc" it immediatly shutdowns the Mac.

Thx for your help and time !

[shypike]

The setting that you should change is "queue_complete_pers".
Setting this to 1 (the default) will preserve the last end-of-queue" action,
this triggers the EOQ action at startup (the actual bug, it should not even be looked at at startup time).
Setting it to 0 will make it necessary to select Shutdown/Standby/Hibernate EOQ action each time you want it.
You can question the wisdom of making 1 the default.

[ThaMan]

Thx for the new release Shypike
will test it and let you know all works

[ThaMan]

0.6.7 Worlks perfectly, nice job