Very large sabnzbd.exe.log

[psycik]

Found this yesterday.  Sitting in the main application directory was a log file sabnzbd.exe.log - at about 160mb.  Seemed to be in use.

What controls this, and should it be getting that large?

I run .5.2 on Windows XP.

[psycik]

Just had a quick look at it.  Its full of the following:

Code: Select all

Traceback (most recent call last):
  File "logging\handlers.pyo", line 74, in emit
  File "logging\handlers.pyo", line 131, in doRollover
WindowsError: [Error 32] The process cannot access the file because it is being used by another process
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):

[shypike]

Known issue. See ISSUES.txt in SABnzbd's program folder.
Cannot be solved as long as the Python designers don't fix this.
You can avoid the problem largely by setting the logging level low (info or errors/warnings).

[shypike]

We will try to create some crude fix for this.
The problem isn't so much the failure of the logging itself,
but the fact that the size limiter of the logging fails too.