2GB logfile - causing crashes?

Report & discuss bugs found in SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
dualnic
Newbie
Newbie
Posts: 8
Joined: October 2nd, 2010, 8:41 am

2GB logfile - causing crashes?

Post by dualnic »

my logfile on windows xp became 2GB and as a reasult i think it started to cause my sabnzbd to crash several times. i have removed it now and ill see if it still crashes

Version: 0.5.6 and 0.5.5
OS: XP
Install-type: windows installer
Are you using IPV6? yes
Last edited by dualnic on December 24th, 2010, 4:42 am, edited 1 time in total.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 2GB logfile - causing crashes?

Post by shypike »

This is a long-standing issue that we cannot solve.
It helps to set the logging level to errors/warnings only.
2G is probably the limit in your file system (or the runtime libraries we use).
We are looking at an improvement for a future release.
dualnic
Newbie
Newbie
Posts: 8
Joined: October 2nd, 2010, 8:41 am

Re: 2GB logfile - causing crashes?

Post by dualnic »

just for refrence the file was SABnzbd.exe.log and it was just the same few lines repeated over again saying that the file couldnt be clossed. and still the program crashes abit even for small lists. it should be noted that this didnt happen when i first installed sab ~six months ago but only recently.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 2GB logfile - causing crashes?

Post by shypike »

SABnzbd.exe.log is written to when an unhandled error occurs in SABnzbd.
The fact that this file is created signals a problem with SABnzbd.
Can you tell what's exactly in the file?

In my previous message I referred to another problem.
dualnic
Newbie
Newbie
Posts: 8
Joined: October 2nd, 2010, 8:41 am

Re: 2GB logfile - causing crashes?

Post by dualnic »

ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
  File "sabnzbd\utils\kronos.pyo", line 277, in _run
  File "sched.pyo", line 108, in run
  File "sabnzbd\utils\kronos.pyo", line 104, in __delayfunc
  File "sabnzbd\utils\kronos.pyo", line 269, in _getqueuetoptime
IndexError: list index out of range

--------------------
ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
  File "sabnzbd\utils\kronos.pyo", line 277, in _run
  File "sched.pyo", line 108, in run
  File "sabnzbd\utils\kronos.pyo", line 104, in __delayfunc
  File "sabnzbd\utils\kronos.pyo", line 269, in _getqueuetoptime
IndexError: list index out of range

--------------------
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):

"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"

is then repeated thousands of times
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 2GB logfile - causing crashes?

Post by shypike »

This looks like a corrupted line in sabnzbd.ini,
the line containing "schedlines" is not formatted correctly.
FInd sabnzbd.ini and remove the line containing schedlines.
You'll loose any schedule you entered in SABnzbd.

http://wiki.sabnzbd.org/configure-v2
dualnic
Newbie
Newbie
Posts: 8
Joined: October 2nd, 2010, 8:41 am

Re: 2GB logfile - causing crashes?

Post by dualnic »

i tried deleting my config file but it still freezes up i know get this in my log file... with no buffer space available being repeated several times


2010-12-28 05:38:42,765::INFO::[newswrapper:215] Failed to connect: (10060, "(10055, 'No buffer space available')") [email protected]:119
2010-12-28 05:38:42,765::INFO::[newswrapper:215] Failed to connect: (10060, "(10055, 'No buffer space available')") [email protected]:119
2010-12-28 05:40:43,765::INFO::[downloader:465] [email protected]:119: Initiating connection
2010-12-28 05:40:43,765::INFO::[downloader:465] [email protected]:119: Initiating connection
2010-12-28 05:40:43,765::INFO::[downloader:465] [email protected]:119: Initiating connection
2010-12-28 05:40:43,765::INFO::[downloader:465] [email protected]:119: Initiating connection
2010-12-28 05:40:43,765::INFO::[downloader:465] [email protected]:119: Initiating connection
2010-12-28 05:40:43,765::INFO::[downloader:465] [email protected]:119: Initiating connection
2010-12-28 05:40:43,765::INFO::[newswrapper:215] Failed to connect: (10060, "(10055, 'No buffer space available')") [email protected]:119
2010-12-28 05:40:58,765::INFO::[newswrapper:215] Failed to connect: (10060, "(11001, 'getaddrinfo failed')") [email protected]:119
2010-12-28 05:41:13,765::INFO::[newswrapper:215] Failed to connect: (10060, "(11001, 'getaddrinfo failed')") [email protected]:119
2010-12-28 05:41:28,765::INFO::[newswrapper:215] Failed to connect: (10060, "(11001, 'getaddrinfo failed')") [email protected]:119
2010-12-28 05:41:43,765::INFO::[newswrapper:215] Failed to connect: (10060, "(11001, 'getaddrinfo failed')") [email protected]:119
2010-12-28 05:41:58,765::INFO::[newswrapper:215] Failed to connect: (10060, "(11001, 'getaddrinfo failed')")
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 2GB logfile - causing crashes?

Post by shypike »

I'd say there's something wrong with your IPv6 stack.
dualnic
Newbie
Newbie
Posts: 8
Joined: October 2nd, 2010, 8:41 am

Re: 2GB logfile - causing crashes?

Post by dualnic »

ok thank you, ill trying removing ipv6 and see how it goes
dualnic
Newbie
Newbie
Posts: 8
Joined: October 2nd, 2010, 8:41 am

Re: 2GB logfile - causing crashes?

Post by dualnic »

sorry i also got this in my sabnzbd.exe.log

ERROR DURING SCHEDULER EXECUTION list index out of range
Traceback (most recent call last):
  File "sabnzbd\utils\kronos.pyo", line 277, in _run
  File "sched.pyo", line 108, in run
  File "sabnzbd\utils\kronos.pyo", line 104, in __delayfunc
  File "sabnzbd\utils\kronos.pyo", line 269, in _getqueuetoptime
IndexError: list index out of range

--------------------

even after deleting the  sabnzbd.ini. i think ill try a fresh install.
Post Reply