Python 2.6: Cannot initiate server connection - server timeout

[Stokkes]

I recently upgraded from Python 2.5.2 to Python 2.6.2 and I'm running into a problem where there SAB can't initiate a connection to the NNTP server and generates quite a few lines of this in the logs:

Code: Select all

2010-03-01 09:56:41,939::INFO::[downloader:714] Thread [email protected]:443: timed out
2010-03-01 09:56:41,939::INFO::[downloader:714] Thread [email protected]:443: timed out
2010-03-01 09:56:41,940::INFO::[downloader:714] Thread [email protected]:443: timed out
2010-03-01 09:56:45,986::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list
2010-03-01 09:56:45,987::INFO::[downloader:458] [email protected]:443: Initiating connection
2010-03-01 09:56:46,069::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list
2010-03-01 09:56:46,069::INFO::[downloader:458] [email protected]:443: Initiating connection
2010-03-01 09:56:46,102::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list
2010-03-01 09:56:46,103::INFO::[downloader:458] [email protected]:443: Initiating connection
2010-03-01 09:56:46,136::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list
2010-03-01 09:56:46,136::INFO::[downloader:458] [email protected]:443: Initiating connection
2010-03-01 09:56:46,169::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list
2010-03-01 09:56:46,170::INFO::[downloader:458] [email protected]:443: Initiating connection
2010-03-01 09:56:46,205::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list
2010-03-01 09:56:46,205::INFO::[downloader:458] [email protected]:443: Initiating connection
2010-03-01 09:56:46,238::DEBUG::[trylist:45] Appending secure.usenetserver.com:443 to <NzbFile: filename=None, type=None>.__try_list

If I remove python 2.6 and reinstall 2.5, this problem goes away. I can recreate it 100% of the time in my environment. The environment is a Slackware-based NAS (unRAID). I'd like to upgrade to 2.6 for a few other applications that I need to run.

Any ideas?

[shypike]

I wouldn't be surprised if Python 2.6.2 contains serious errors.
We only test against Python 2.6.4.
Most Linux systems allow parallel installation of Python 2.5 and 2.6.

[Stokkes]

Confirming that Python 2.6 worked.