SABnzbd Forums

Hi Guy's (Girls?),

Total new here so a new newbie (woei!)
I'm from the Netherlands so please no flame’s about my typing mistakes .
The problem:
I have  a server Windows 2008 R2 (64 bits), I had a older version installed from Sabnzbd and never had any problems. But last week I upgraded it to  SABnzbd+ 0.5.0RC6.
The problem is that sometimes par2 needs to repair, and then it sometimes going to hang the application. Well at least it uses 100% cpu (quadro cpu) 4 cores are full load, and it looks like its doing something but in sabnzbd (from the website you can look at History and there it say’s repairing file at 92% but it stays there!. Because the other downloads are done there all have the status waiting  When I stop the process the load disappear, and its starting to unpack.
Off course I can delete this version and rollback but I thought maybe we can fix it?
Here a spec from my system:
Dell 755 optiplex
8GB ddr2 memory
Total of 4.7TB hard disks (5 X sata 3 X usb disks.) (have to buy a pci Sata controller for the rest of the 3 disks..
CPU = Quadro  E9400
Windows server 2008 64bits
All the logs ended 2 days ago ? so can’t find anything about today.
Anyone have a idea what’s going wrong? Maybe I’m totally wrong here our I don’t put in the right information but ask I will check this thread a lot.

greetings,

CobraICE

update:

i have a 211mb log file: sabnzbd.exe.log with this error:
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file

thought i need to post it.. 211mb is much for a log file...

CobraICE wrote: update:

i have a 211mb log file: sabnzbd.exe.log with this error:
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file
Traceback (most recent call last):
  File "logging\handlers.pyo", line 73, in emit
  File "logging\handlers.pyo", line 147, in shouldRollover
ValueError: I/O operation on closed file

thought i need to post it.. 211mb is much for a log file...

i found the logs btw its in my profile.but nothing on par2.

in my ini i have multicore enabled: par2_multicore = 1

greetings,

Cobra

How often does this happen?

if you close sabnzbd and change par2_multicore = 1 to par2_multicore = 0 does this ever happen?

The logging is not related but a persistent bug in
the programming library we use (as described in ISSUES.txt).
It doesn't influence the working of SABnzbd, only the content of the log folder.

switch wrote: How often does this happen?

if you close sabnzbd and change par2_multicore = 1 to par2_multicore = 0 does this ever happen?

well after posting this i changed it to 0 (no multicore) before it happens almost every day.