0.6.6 Not Starting Up

[DualSavage]

HI There,

I am running Windows 7 Professional SP1 64-Bit and used to use version 0.6.5 of SABNZBD (through Chrome) which was working ok. There were a few hiccups which I was trying to iron out.

I upgraded to version 0.6.6 this morning and now SABNZBD won't start at all. I googled for a 64 bit version/installer and found a 0.6.6 Beta2 exe file which I also tried but still nothing.

Thanks in advance.

[shypike]

Did the installer work properly?

Have you tried the SABnzbd-Safe mode (see Windows Start menu)?
Otherwise start a command prompt and type (with the quotes included):
"c:\program files (x86)\sabnzbd\sabnzbd-console.exe"

You'll see logging pass by, which may tell you what the problem is.

[DualSavage]

Hi there,

Thanks for the super fast reply!! I tried both safe mode and console and each of those methods opened up SAB in a browser window.

I re-ran the 0.66 installer (non-beta) and made sure to tick "Run on startup" and then rebooted but it still doesn't open until I click safe mode in the start menu folder.

Cheers

[shypike]

"Run on startup" (i.e. run SABnzbd at system startup) is not the same as start browser when SABnzbd starts up.
Also "run on startup" (as done by the installer) has a number of issues and we're going to remove that option.
Whether or not the browser starts up is determined by Config->Switches->"Launch Browser on Startup".

[DualSavage]

Hi again....

In the installer when it finished there are 2 tick boxes. 1 about the readme file and the other says "Start SABNZBD (hidden)". The very first time I ran the 0.6.6 installer I left this ticked when exiting. The second time I ran the 0.6.6 (non-beta) installer I didn't tick that option when exiting.
[Not sure if this is relevant]

After running the safe mode option I went into config > switches and I did notice that the "Launch Browser on Startup" switch was unticked.

I ticked it, clicked the "Save Changes" button at the bottom of the page and closed SAB's tab in Chrome. I rebooted and nothing happened again. Went back into Safe mode and the "Launch Browser on Startup" switch is still unticked.

It doesn't seem to be saving that setting?

Out of curiosity....What is the difference between your "SABnzbd" and "SABnzbd - Safe Mode" options in the start menu? Should I not just put the safe mode option in my startup folder instead of the other one?

[shypike]

It's very confusing, sometimes I'm lost myself.

1. "Launch at startup"
This launches SABnzbd at login.
(Not reliable because on many systems it's tied to the admin logging in and not the regular user account.
Installation is actually done by the "admin" account and not the regular user account.)

2. "Lauch (hidden)"
Just a convenience for first time users who don't know how to start it otherwise.
Not a happy feature either, especially the "hidden" part.

3. "Safe mode"
This forces:
- Use of 127.0.0.1:8080 for the web server, to solve incorrect setttings locking you out.
- Disable web server username/password, because regularly people lock themselves out.
- Launch browser, for people who forgot how to connect to the UI

Went back into Safe mode and the "Launch Browser on Startup" switch is still unticked.

That's bad. Safe mode should enable the browser launch permanently. I'll check that.

[dss]

curiously, since updating to 0.6.6 i'm having similar behaviour (on XP) - i can start SABnzbd using the address manually or via bookmarks etc, however, the switch for Launching in the browser saves initially and then defaults back to 'off' each and every reboot

[shypike]

If you let Windows restart SABnzbd automatically at login (through the link the installer places in the Startup folder),
the browser-launch will always be switched off.
This is because the link in the Startup folder contains the -b0 parameter, explicitly disabling the browser-launch.
The assumption is that you don't appreciate this browser launch at login.
It's been like this since early 0.5.x releases.

[dss]

If you let Windows restart SABnzbd automatically at login (through the link the installer places in the Startup folder),
the browser-launch will always be switched off.
This is because the link in the Startup folder contains the -b0 parameter, explicitly disabling the browser-launch.
The assumption is that you don't appreciate this browser launch at login.
It's been like this since early 0.5.x releases.

Yup, but used to happen was that windows starting up (and starting up SABnzbd) didn't trigger a SABnzbd window, but then going to the 'Start Menu' shortcut would trigger a browser window.

[shypike]

but then going to the 'Start Menu' shortcut would trigger a browser window.

No, the link in the Start menu always has had a -b0 setting.
Nevertheless, there have been some changes in the way SABnzbd starts,
so I'll check some more scenario's.

[DualSavage]

Hi there,

Ok are you saying then if we remove the -b0 parameter from the link in the startup folder then it should automatically open the browser tab after a Windows reboot?

Thanks again for all the assistance!

[shypike]

Yes, after you have enabled it again in Config->Switches.

[dss]

i've tripled checked - the start menu shortcut doesn't have the -b0 parameter (the startup menu shortcut does).

When "Launch Browser on Startup" is enabled, it stays enabled even if SABnzbd is shutdown and restarted. However, on a restart of XP, the setting returns to disabled again.

[shypike]

OK, I found out what happened.
When SABnzbd sees that an identical version of itself is already running, it will start the browser pointing to SABnzbd.
So far, previous releases ignored the -b0 setting when doing this.
At the request of other users, the -b parameter is now inspected and when it's -b0, the browser isn't started.
The auto-started instance will reset Config->Switches->Launch-Browser, but this makes no difference,
since later clicks on the shortcut will ignore this setting anyway.

The new behaviour is perfectly logical, however it's not necessarily what you want.
0.6.6 sees that Config->Switches->Launch-Browser is off and will not start the browser (even without any -b parameter).
I can fix this and make both user groups happy by only obeying the -b0 setting when it's explicitly added.
This would mean that you can click on the normal shortcut (which doesn't have -b0) and still launch the browser.

[DualSavage]

Thank you Shypike! Will look forward to that update (",)