SABnzbd Forums

I'm currently running 0.7.5 successfully as a service. After an upgrade to 0.7.6 beta 1, the sabnzbd service crashes every time with this error in event viewer:

The instance's SvcRun() method failed
Traceback (most recent call last):
File "win32serviceutil.pyo", line 806, in SvcRun
File "SABnzbd.pyo", line 1698, in SvcDoRun
File "SABnzbd.pyo", line 1121, in main
File "SABnzbd.pyo", line 730, in check_for_sabnzbd
File "sabnzbd\misc.pyo", line 698, in exit_sab
SystemExit: 0
%2: %3

Running the sabnzbd.exe instead of the service also doesn't appear to work. The .exe dies almost immediately upon launch.
Reverting back to 0.7.5 works.

OS is Windows 2008 R2

Any suggestions?

TIA,

LJ

How does SABnzbd's own log file end?
Set debug logging on by editing the sabnzbd.ini file directly: It looks very much like SABnzbd thinks there's another instance running on the same machine.
Is that so?

I had a similar thing happen when I tried installing 0.7.6 beta 1. I ran it and saw the .exe show in process manager for a second, then it disappeared. I ended up just deleting my programfiles/sabnzbd directory and reinstalling 0.7.5 without any problems, but it did seem like it was crashing out, but I didn't look for any log files.

shypike wrote:How does SABnzbd's own log file end?
Set debug logging on by editing the sabnzbd.ini file directly:

Code: Select all

[logging]
    log_level = 2

It looks very much like SABnzbd thinks there's another instance running on the same machine.
Is that so?

SABnzbd is set to run as a service and the .exe isn't loaded in processes.

I've set that now in the .ini... tried installing it again and I must be blind because I'm not finding a .log file - either when running it via the service or the sabnzbd.exe. My INI looks like this:

log_dir = h:\sabnzbd\logs <--- sabnzbd.log should be there (it's there in 0.7.5)
admin_dir = h:\sabnzbd\admin
[logging]
log_new = 0
max_log_size = 5242880
log_level = 2
log_backups = 5
enable_cherrypy_logging = 0

Thanks,
LJ

log_dir = h:\sabnzbd\logs <--- sabnzbd.log should be there (it's there in 0.7.5)

To clarify my statement: I can delete the sabnzbd.log in 0.7.5 and it'll recreate it next time I start the service. It doesn't recreate in 0.7.6b1

LJ

Did you install the new version over the new one.
In other words, are the locations off files still the same.
Maybe you should delete both services are redefine them.
From my testing, I can find no issues with running it as a service.

Yeap, same location, I just did an upgrade. I'll try removing the services, upgrading, then reinstall them.

LJ

I looked at the code change that removed the version check, when checking for an already running instance.
Under some circumstances the new code can give unpredictable results.
This could explain your issue.
I will change the code for 0.7.6Beta2 and PM you as soon as it is available.

shypike wrote:I looked at the code change that removed the version check, when checking for an already running instance.
Under some circumstances the new code can give unpredictable results.
This could explain your issue.
I will change the code for 0.7.6Beta2 and PM you as soon as it is available.

Awesome, thanks.

As a side note, I also got it working as a service again.

Like you suggested: try removing the service then re-adding.. Here's what I did:

Remove the SABnzbd service and the helper service.
Upgraded to 0.7.6b1 (no other removals, just a simple update).
reinstalled the services from the 0.7.6b1 exes. Appears to be running ok now.

LJ

It could be that after your last stop of 0.7.5, registry info was left behind.
In such a case, the incorrect change in the code would let SABnzbd assume that
an instance was already running (and therefore bailing out).
In some sense, it's a pity that you already removed the cause.
Of course I cannot blame you for doing that

lol... I can always go back to 0.7.5 and try it again if you want

Skypike:

I just installed Beta 2 over Beta 1. No issues with the service going from 1 to 2. I can still test 0.7.5 --> beta 2 if you want.

At any rate, thanks for quick fixes you devs do!

LJ

I pretty confident that the issue is what I described.
Given that the most probable initial cause was left behind registry info,
it's not certain that a new upgrade 0.7.5->0.7.6 would show the problem again.
Thanks for trying the Betas and so preventing problems for future upgraders.