I've been struggling with this problem for about a month or so now. Every time I think I start to have a handle on how SABDNZB and Sick Beard work together, I get knocked back three paces.
I've been trying to tweak the post-processing so that SABDNZB and Sick Beard will work together and rename my shows to my naming convention and then copy them to my external repository. For awhile it was downloading things but not doing the post-processing. So I go into SABDNZB Config and make changes. When I restart SABDNZB, it's completely hosed (again). My short cut points to "C:\Program Files (x86)\SABnzbd\SABnzbd.exe" --server 127.0.0.1:8080. However, after attempting to restart SABDNZB, the web pages launches with an error since it's trying to open 10.0.0.4:563. This makes no sense. The shortcut points to local host and 563 is the port that SABDNZB is supposed to listen on for my newsgroup provider. I don't understand how the web interface can start using settings not specified in the short cut.
Also, and I am so bewildered I don't know if this related or not, I tried to switch my newsgroup provider server name from eunews.blocknews.net to us.blocknews.net. For whatever reason this change will not take. It doesn't matter if I try to use the we interface or edit the sabdnzb.ini file. Either the change is ignored or SABDNZB starts acting all wonky on startup.
This next bit has to do with SABDNZB and Sick Beard. In SABDNZB I enabled the API Key so Sick Beard can access it. Since post-processing wasn't working correctly, I had SABDNZB generate a new API key. When I tried to update the API key value in Sick Beard the change won't take. I go into Config > Search Settings and then paste in the new API key value. I then use the test feature. Sick Beard returns a successful test. Then I save changes and return to the home page. Yet when I come back, the API key value has returned to the old value. This happens no matter if I use the Sick Beard web interface or edit the Sick Beard config.ini.
I would really love to know why my setup has gotten so wonky. It was working beautifully for a long time. All I wanted to do was to point SABDNZB to a different newsgroup server. Not sure why that has wreaked such havoc.
Thanks in advance for any suggestions.
BTW - Win 7 64-bit and Chrome.
Serious issue when restarting
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
- Newbie
- Posts: 17
- Joined: February 27th, 2014, 2:30 pm
Re: Serious issue when restarting
Just to be sure, also add the -f parameter and the full path to your sabnzbd.ini file.
So:
-f /Users/you/..../sabnzbd.ini
So:
-f /Users/you/..../sabnzbd.ini