Sabnzbd 0.5.0.alpha2 "Blocked server" bug??
Posted: May 6th, 2009, 8:27 am
Hi I am recently having a few problems....
I use 3 nntp-servers.. Let's say A, B and C (A being the first added, b the second etc.)
When just starting the program it all works. After a while; server B or server C or both will stop working and go on 'blocked'.. After this it will start todo weird things....When I restart sabnzbd things are normal again for a while.
This is the output...notice the amount of servers listed here (I only have 3)....
Connections
* reader.xsnews.nl:119: 0
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* highspeednews.xenosite.nl:119: 0
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0
* newsreader1.eweka.nl:119: 0
Last warnings (clear)
2009-05-06 08:40:57,864 WARNING Thread [email protected]:119: timed out
2009-05-06 08:41:52,036 ERROR Too many connections to server highspeednews.xenosite.nl:119
2009-05-06 08:41:59,021 WARNING Thread [email protected]:119: timed out
2009-05-06 08:42:03,628 WARNING Thread [email protected]:119: timed out
2009-05-06 08:42:04,518 WARNING Thread [email protected]:119: timed out
2009-05-06 08:42:14,932 WARNING Thread [email protected]:119: timed out
2009-05-06 12:47:34,418 ERROR Failed to connect: timed out [email protected]:119
2009-05-06 12:47:34,418 ERROR Failed to initialize [email protected]:119
2009-05-06 12:47:34,445 WARNING Thread [email protected]:119: failed to initialize
2009-05-06 12:48:04,471 WARNING Thread [email protected]:119: timed out
2009-05-06 12:48:04,483 WARNING Thread [email protected]:119: timed out
2009-05-06 13:51:59,460 WARNING Thread [email protected]:119: timed out
2009-05-06 13:59:25,508 WARNING Thread [email protected]:119: timed out
2009-05-06 14:14:06,582 WARNING CRC Error in (136DDE8A -> 22F8E4B6)
2009-05-06 14:14:15,415 WARNING CRC Error in (61700FE5 -> 11B4993B)
2009-05-06 14:15:32,765 WARNING Thread [email protected]:119: timed out
2009-05-06 14:20:06,551 WARNING Deleting /mnt/transdata3/sabnzbd.temp/law-and-order-s192/ctu-x264-law.and.order.1914.vol00+1.par2 failed
2009-05-06 14:20:06,560 WARNING Deleting /mnt/transdata3/sabnzbd.temp/law-and-order-s192/ctu-x264-law.and.order.1917.vol00+1.par2 failed
2009-05-06 14:22:50,084 ERROR CRC mismatch! ofs =49999980
2009-05-06 14:23:41,114 WARNING ERROR: CRC failed in law.and.order.s19e16.720p.hdtv.x264-ctu.mkv"
Server A (xenosite) never has an error. Me thinks this is because it's the first server added.
The boys down at the xsnews.nl forum (in dutch) seem to think that it's timing related (whatever that means; they suggested thinkering with the timeout, but 120 sec or 30 sec doesn't make a difference). Also I've seen this behaviour on 0.4.7 happening. Could the python version used invluence this? (python v25 - 2520 (something like that) is used) I'm installing v25 -2541 right now to try to fix things)..... EDIT: Sabnzbd is now running on python 25-2.5.4.1 with the same result... But now i get this: 2009-05-06 16:05:17,832 ERROR Failed login for server reader.xsnews.nl:119 (a moment ago it was 'timed out' )...
Hope anybody can read thru my ramlings, and get down to the core.... grz. Tijlbert
I am running freenas v7;
I use 3 nntp-servers.. Let's say A, B and C (A being the first added, b the second etc.)
When just starting the program it all works. After a while; server B or server C or both will stop working and go on 'blocked'.. After this it will start todo weird things....When I restart sabnzbd things are normal again for a while.
This is the output...notice the amount of servers listed here (I only have 3)....
Connections
* reader.xsnews.nl:119: 0
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* highspeednews.xenosite.nl:119: 0
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0 (blocked)
* newsreader1.eweka.nl:119: 0
* newsreader1.eweka.nl:119: 0
Last warnings (clear)
2009-05-06 08:40:57,864 WARNING Thread [email protected]:119: timed out
2009-05-06 08:41:52,036 ERROR Too many connections to server highspeednews.xenosite.nl:119
2009-05-06 08:41:59,021 WARNING Thread [email protected]:119: timed out
2009-05-06 08:42:03,628 WARNING Thread [email protected]:119: timed out
2009-05-06 08:42:04,518 WARNING Thread [email protected]:119: timed out
2009-05-06 08:42:14,932 WARNING Thread [email protected]:119: timed out
2009-05-06 12:47:34,418 ERROR Failed to connect: timed out [email protected]:119
2009-05-06 12:47:34,418 ERROR Failed to initialize [email protected]:119
2009-05-06 12:47:34,445 WARNING Thread [email protected]:119: failed to initialize
2009-05-06 12:48:04,471 WARNING Thread [email protected]:119: timed out
2009-05-06 12:48:04,483 WARNING Thread [email protected]:119: timed out
2009-05-06 13:51:59,460 WARNING Thread [email protected]:119: timed out
2009-05-06 13:59:25,508 WARNING Thread [email protected]:119: timed out
2009-05-06 14:14:06,582 WARNING CRC Error in (136DDE8A -> 22F8E4B6)
2009-05-06 14:14:15,415 WARNING CRC Error in (61700FE5 -> 11B4993B)
2009-05-06 14:15:32,765 WARNING Thread [email protected]:119: timed out
2009-05-06 14:20:06,551 WARNING Deleting /mnt/transdata3/sabnzbd.temp/law-and-order-s192/ctu-x264-law.and.order.1914.vol00+1.par2 failed
2009-05-06 14:20:06,560 WARNING Deleting /mnt/transdata3/sabnzbd.temp/law-and-order-s192/ctu-x264-law.and.order.1917.vol00+1.par2 failed
2009-05-06 14:22:50,084 ERROR CRC mismatch! ofs =49999980
2009-05-06 14:23:41,114 WARNING ERROR: CRC failed in law.and.order.s19e16.720p.hdtv.x264-ctu.mkv"
Server A (xenosite) never has an error. Me thinks this is because it's the first server added.
The boys down at the xsnews.nl forum (in dutch) seem to think that it's timing related (whatever that means; they suggested thinkering with the timeout, but 120 sec or 30 sec doesn't make a difference). Also I've seen this behaviour on 0.4.7 happening. Could the python version used invluence this? (python v25 - 2520 (something like that) is used) I'm installing v25 -2541 right now to try to fix things)..... EDIT: Sabnzbd is now running on python 25-2.5.4.1 with the same result... But now i get this: 2009-05-06 16:05:17,832 ERROR Failed login for server reader.xsnews.nl:119 (a moment ago it was 'timed out' )...
Hope anybody can read thru my ramlings, and get down to the core.... grz. Tijlbert
I am running freenas v7;