Page 1 of 1

[SOLVED] error in Sickrage log regarding connections to SAB

Posted: January 24th, 2015, 8:09 pm
by moveright
Out of nowhere, I am now getting piles of errors in my SickRage log with regards to not being able to connect to SAB,

Code: Select all

2015-01-24 18:41:29 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:28 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:27 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:26 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:25 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:24 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:23 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:22 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:20 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:19 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:18 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:17 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:16 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:15 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:14 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:13 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:12 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:10 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:09 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:08 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:07 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:06 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:05 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:04 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:03 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:02 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:41:01 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:59 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:58 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:57 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:56 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:55 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:54 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:53 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:40:52 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:39:57 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:39:56 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:39:54 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:39:53 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:39:52 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
2015-01-24 18:39:51 SEARCHQUEUE-BACKLOG-107671 :: Unable to connect to SAB: socket error : error [Errno 10061] No connection could be made because the target machine actively refused it
It goes on even further than that but I figured this should give you an idea. I Googled this and the only thing I came up with is to make sure that https was not enabled in SAB and I did verify that.

What else can I check?

If it helps, my backlog in SickRage is HUGE. I'm not sure if that is what is causing this issue but I thought it was useful information.

Thanks!

Re: error in Sickrage log regarding connections to SAB

Posted: January 25th, 2015, 3:53 am
by sander
What is the IP address and port of SABnzbd? With a webbrowser, can you access SABnzbd on the IP/Port combo?
What is the IP address and port Sickrage is trying to access SABnzbd on?

Re: error in Sickrage log regarding connections to SAB

Posted: January 25th, 2015, 8:42 am
by moveright
Thanks for the response!

Ok, first off - sorry for not leading with more information, that was totally my fault. My Sickrage and SAB installations are on the same windows 7 machine.

I am able to log into SAB from other machines at the address 192.168.1.50:8080. My Sickrage SAB config points to //localhost:8080. Seems like a dumb question - but would it be ineffectual to change //localhost:8080 to 192.168.1.50:8080?

Re: error in Sickrage log regarding connections to SAB

Posted: January 25th, 2015, 9:10 am
by shypike
If all the software is local, it's safer to use 127.0.0.1 instead of "localhost".
Localhost can resolve to either 127.0.0.1 or ::1 (IPv6), it's not always predictable which
program picks which address. And they are really different addresses.

Re: error in Sickrage log regarding connections to SAB

Posted: January 25th, 2015, 2:09 pm
by moveright
Ok - thank you for the input. I went ahead and changed the address in SickRage to point to SAB at http://127.0.0.1

We'll see if this takes care of it as of tomorrow.

Thanks!

Re: error in Sickrage log regarding connections to SAB

Posted: January 25th, 2015, 4:17 pm
by shypike
Make sure you tell both programs that they should use 127.0.0.1
Just in case SABnzbd starts listening only to ::1

Re: error in Sickrage log regarding connections to SAB

Posted: January 25th, 2015, 5:55 pm
by moveright
Done. Thank you very much. Odd that in SAB, the listening address was 0.0.0.0.

I'll report back here in a couple of days to say if this took care of the problem. Thanks!

Re: error in Sickrage log regarding connections to SAB

Posted: January 26th, 2015, 2:52 am
by shypike
0.0.0.0 isn't a real address, it's short-hand for listen on all addresses.
But the "all" doesn't always work out.

Re: error in Sickrage log regarding connections to SAB

Posted: January 27th, 2015, 8:11 pm
by moveright
Just now checked and it looks like no errors! Thanks!