SABnzbd Forums

Hi all, on OS X 10.5.8 running .4.11 (.app install) I'm getting the following. Note that this is happening right this instant, and has happened in the past, and seems to happen once in a while.

2009-08-05 19:23:48,835 ERROR [newswrapper] Failed to connect: (22, 'Invalid argument') [email protected]:119
2009-08-05 19:23:56,835 ERROR [newswrapper] Failed to connect: (22, 'Invalid argument') [email protected]:119
2009-08-05 19:25:11,795 ERROR [newswrapper] Failed to connect: (22, 'Invalid argument') [email protected]:119
2009-08-05 19:25:20,831 ERROR [newswrapper] Failed to connect: (22, 'Invalid argument') [email protected]:119
2009-08-05 19:25:28,831 ERROR [newswrapper] Failed to connect: (22, 'Invalid argument') [email protected]:119
2009-08-05 19:25:36,833 ERROR [newswrapper] Failed to connect: (22, 'Invalid argument') [email protected]:119
2009-08-05 19:25:37,854 WARNING [downloader] Thread [email protected]:119: timed out
2009-08-05 19:25:37,854 WARNING [downloader] Thread [email protected]:119: timed out
2009-08-05 19:25:37,855 WARNING [downloader] Thread [email protected]:119: timed out
2009-08-05 19:25:37,856 WARNING [downloader] Thread [email protected]:119: timed out
2009-08-05 19:25:37,856 WARNING [downloader] Thread [email protected]:119: timed out
2009-08-05 19:25:37,857 WARNING [downloader] Thread [email protected]:119: timed out
2009-08-05 19:25:37,857 WARNING [downloader] Thread [email protected]:119: timed out

TekSavvy is my ISP newsserver, the others are the free IPV6 ones (note that I can ping6 kame.net no problem)

Any ideas?

--
resolved: looks like the IPV6 newsgroups are timing out, and that's rolling over to my other newsgroups. Best bet - remove the ipv6 servers, OR get in on some .50 lovin' where you can make servers optional Further edit - instead of removing, I just the # of connections to 0 for eweka, newzilla works fine. The beta apparently gets around this by allowing some servers to be optional, instead of killing all connections if one can't connect.

coolfish wrote: The beta apparently gets around this by allowing some servers to be optional, instead of killing all connections if one can't connect.

Indeed, 0.5.0 was modified to accommodate this sort of situation where you have a bunch of unreliable (but cheap) servers.
Previously, the servers had to be just reliable (only the retention time differences were taken care of).

coolfish wrote: Hi all, on OS X 10.5.8 running .4.11 (.app install) I'm getting the following. Note that this is happening right this instant, and has happened in the past, and seems to happen once in a while.
--
resolved: looks like the IPV6 newsgroups are timing out, and that's rolling over to my other newsgroups. Best bet - remove the ipv6 servers, OR get in on some .50 lovin' where you can make servers optional Further edit - instead of removing, I just the # of connections to 0 for eweka, newzilla works fine. The beta apparently gets around this by allowing some servers to be optional, instead of killing all connections if one can't connect.

The IPv6 XSNEWS.NL server is currently down, so that's why get the failed to connect errormessages,

You can always check their serverstatus at http://xsnews.nl/ipv6

Since that this server is in Beta it happens sometimes that  the server is down..

thanks for the timely help....
I was really in a great need....