Sab locking up on start

[josephbphillips]

I am having a problem that started very recently, but I can't think of a significant change that would have caused this. 

I noticed a day or two ago that I hadn't seen any DL's coming through.  When I moved the mouse over the menu icon, I got the spinning beach ball.  I also found that sab was using around 100% CPU consistently.  I tried rebooting the computer, uninstalling and deleting all settings, reverting to stable release, but regardless I see similar results.  When I load Sab, Growl says Sab is shutting down, and then it just hangs with the beach ball.

The only change I have made in my system lately is moving from wireless to wired ethernet.  That resulted in a change to the IP address, but I am unable to access Sab on either IP.

Any ideas?


Version: 0.5.0Beta6
OS: OS X 10.6.2
Install-type: DMG
Skin (if applicable): (Plush)
Firewall Software: None
Are you using IPV6? (I believe it is used on my internal network?)
Is the issue reproducible? (yes)

[josephbphillips]

Logs attached.

Thanks!!

[josephbphillips]

Of course- I have been working on this for hours, but as soon as I post this I figure out a solution.

The change in IP was borking Sab.  Is that a feature or a bug?

I love the program and love the improvements!  It does seem like a simple IP change should throw a decipherable error rather than causing the software to s--- the bed...

Thanks for all the hard work!

[shypike]

If you hard-code a numerical IP into the sabnzbd.ini,
that's what SABnzbd will use.
You should use either the hostname or 0.0.0.0.
We recommend the numerical IP only when all other methods fail.

[josephbphillips]

Thanks! 

I changed it to localhost and it worked fine locally, but I couldn't access it remotely.  If I use 0.0.0.0, it seems to work as expected.

Thanks!!