SABnzbd Forums

Posted: **February 8th, 2013, 11:37 am**

With IPv6 not working, I get the error messages below on my STDOUT:

2013-02-08 17:31:40,013::INFO::[downloader:375] [email protected]:119: Initiating connection
2013-02-08 17:31:40,014::ERROR::[downloader:380] Failed to initialize [email protected]:119
2013-02-08 17:31:40,014::INFO::[downloader:381] Traceback: 
Traceback (most recent call last):
  File "/home/sander/oude-SABnzbds/SABnzbd-0.7.7/sabnzbd/downloader.py", line 376, in run
    nw.init_connect(self.write_fds)
  File "/home/sander/oude-SABnzbds/SABnzbd-0.7.7/sabnzbd/newswrapper.py", line 263, in init_connect
    self.server.username, self.server.password, self.blocking, write_fds)
  File "/home/sander/oude-SABnzbds/SABnzbd-0.7.7/sabnzbd/newswrapper.py", line 165, in __init__
    raise socket.error(errno.EADDRNOTAVAIL, "Address not available - Check for internet or DNS problems")
error: [Errno 99] Address not available - Check for internet or DNS problems
2013-02-08 17:31:40,035::INFO::[downloader:640] Thread [email protected]:119: failed to initialize
2

That seemed new, so I went back in version:
Up to 0.7.5, I just get a timeout
With 0.7.6 and higher, I get the above error message

Is this as designed / wanted?

Posted: **February 8th, 2013, 1:50 pm**

You tell me.
This was the last significant change involving IPv6 since 0.7.0:

https://github.com/sabnzbd/sabnzbd/comm ... b2551d4235

Posted: **February 8th, 2013, 2:19 pm**

Well, if you ask me:

I find a traceback a bit strange. As SABnzbd raises the error message, why is it not caught by a calling function within SAB?
The message itself is OK. If possible, it should mention the newsserver it is trying to reach. ... well, assuming the message also appears when a server is not reachable.
BTW: I'm not sure it started since 0.7.6 ... that was a quick test.

Posted: **February 8th, 2013, 2:35 pm**

The exception is caught, what you're seeing is a debug traceback for diagnostic purposes.

Posted: **February 9th, 2013, 2:28 am**

shypike wrote:The exception is caught, what you're seeing is a debug traceback for diagnostic purposes.

You have no IPv6 yourself, right? If so, when you fill out newszilla6.xs4all.nl as a server, do you get the same traceback?

Posted: **February 9th, 2013, 6:22 am**

I see the traceback in the log (as intended).
The Status->Connections page shows: # Connections: Failed to connect: (60, '[Errno 65] No route to host') [email protected]:119
When I also enable another server, downloading runs along fine, meaning that the downloader did not crash.

There is no problem as far as I can tell.

Posted: **February 9th, 2013, 6:29 am**

shypike wrote:
There is no problem as far as I can tell.

OK, then I will just regard the traceback logging as a big fat warning ...

Posted: **April 22nd, 2013, 2:12 am**

If I use this line at gai.conf

precedence ::ffff:0:0/96 100

a connection to newszilla6.xs4all.nl:119 is not possible. "telnet newszilla6.xs4all.nl 119" works fine nevertheless.

Kind regards,

sueppchen

SABnzbd Forums

Ipv6 not working => traceback (since 0.7.6)

Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)

Re: Ipv6 not working => traceback (since 0.7.6)