Errors occurred.

Get help with all aspects of 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.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Errors occurred.

Post by thora »

Hi.

Each time I tried to download a largest file, I have after a  various period of downloading an "errors occurred" windows with the advice to see the "SABnzbd.exe.log file" for details.

Here is the content of the log file, hope you could help me because i don't know about this error  ???

Code: Select all

Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in <module>
  File "SABnzbd.py", line 1199, in main
  File "sabnzbd\__init__.pyo", line 756, in check_all_tasks
  File "sabnzbd\downloader.pyo", line 100, in check
  File "sabnzbd\decorators.pyo", line 31, in newFunction
  File "sabnzbd\downloader.pyo", line 831, in check_timers
  File "sabnzbd\downloader.pyo", line 315, in init_server
IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
Exception in thread Thread-3 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
  File "sabnzbd\downloader.pyo", line 431, in run
<type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'has_articles_for'
Thank's for help  ;)

Version: 0.5.5
OS: Win 7 64 bits.
Install-type: Windows Installer
Skin (if applicable): Plush
Firewall Software: None
Are you using IPV6? : yes
Is the issue reproducible? : ?
Last edited by thora on November 10th, 2010, 2:46 pm, edited 1 time in total.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Errors occurred.

Post by shypike »

It looks like a severe case of queue corruption.
Does the same happen with 0.5.4 ?

You can try to clean your queue by starting once like this:
WindowsKey-R
"c:\program files (x86)\SABnzbd\SABnzbd.exe" --clean

That will erase the whole queue.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

Hi Shypike, thank's for the fastest reply  :)

I think I had the same problem with previous version.

I'll try to clean the queue and will post the result tomorrow  ;)

Regards.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

Same issue after cleanning the queue.

I tried with 0.5.0 version, it's seem working (actually downloading since more than3 hours without error) but I obtain a largest "SABnzbd.exe.log" file (84 Mo in 3 hours)

Here is a part of the content :

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] Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus
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
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
Error always on the same line : 73 and 147.

Hope you could help me  ;)
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Errors occurred.

Post by shypike »

This is a known issue that we cannot solve (see ISSUES.txt in SABnzbd's program folder).
Other than filling up the file, it does no harm.
It helps to set the logging level to Warnings/Errors-only in the Connections page.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

Thank's for the advice  ;)

I will upgrade from 0.5.0 to 0.5.2 - 0.5.3 - 0.5.4 to see when appear the problem and report in this topic.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

Hi.

Upgrade today from 0.5.2 to 0.5.3 and the windows "Errors occured" is here.
I tried to dowload a 7.5 Gb file and it's stopped after 961 mo with this log :

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] Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus
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
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 "SABnzbd.py", line 1240, in <module>
  File "SABnzbd.py", line 1182, in main
  File "sabnzbd\__init__.pyo", line 747, in check_all_tasks
  File "sabnzbd\downloader.pyo", line 100, in check
  File "sabnzbd\decorators.pyo", line 31, in newFunction
  File "sabnzbd\downloader.pyo", line 831, in check_timers
  File "sabnzbd\downloader.pyo", line 319, in init_server
IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
Hope you could help me  ;)
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Errors occurred.

Post by shypike »

Known problem: http://wiki.sabnzbd.org/known-issues (bottom issue).
Unfortunate, but harmless.
Set logging to the minimum level (Warnings/Errors) in Connections, to limit file growth.

So the problem you're having is not caused by this, but something else.
Which isn't logged because of the logging bug.

What happens if you just restart SABnzbd?
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

If I restart SABnzbd, download restart until the next "Errors occurred"

I will try with the last version 0.5.6.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Errors occurred.

Post by shypike »

Wait a minute, I missed the last line of your log file.

IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.

This is the CherryPy webserver that's crapping out.
It could be that it reacts like this when you stop SABnzbd (or it stops itself or Windows stops it).

How does SABnzbd stop?
Does Windows come up with a "This program stopped" pop up window?
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

Hi.

I use SABnzbd associated with the Browser Google Chrome.
Usually, when SABnzbd is working, I close Google Chrome.

After a while when it's down, I have a pop up windows named "Error Occured" with the advice to see the "SABnzbd.exe.log file" for details with a ok button.

After ok select to close the window, I can lunch SABnzb until the next "Error Occured"

Thank's for your support  ;)
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Errors occurred.

Post by shypike »

What's inside the file SABnzbd.exe.log ?
It should be in SABnzbd's program folder.
If not, it could be that access rights prevent it from being written.
As a work-around you can copy the whole SABnzbd program folder to
a location where you can write (Like Documents) and run it from there.
That way it should be able to write to the file.
That usually gives important clues.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

shypike wrote: What's inside the file SABnzbd.exe.log ?

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] Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus
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
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 "SABnzbd.py", line 1240, in <module>
  File "SABnzbd.py", line 1182, in main
  File "sabnzbd\__init__.pyo", line 747, in check_all_tasks
  File "sabnzbd\downloader.pyo", line 100, in check
  File "sabnzbd\decorators.pyo", line 31, in newFunction
  File "sabnzbd\downloader.pyo", line 831, in check_timers
  File "sabnzbd\downloader.pyo", line 319, in init_server
IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
shypike wrote:It should be in SABnzbd's program folder.
Yes, the "SABnzbd.exe.log" file is located in SABnzbd's program folder.

shypike wrote:If not, it could be that access rights prevent it from being written.
As a work-around you can copy the whole SABnzbd program folder to
a location where you can write (Like Documents) and run it from there.
That way it should be able to write to the file.
That usually gives important clues.
I tried last version this afternoon without problems, so will tell you in fews days if all work correctly  ;)

Thank's for help.
thora
Release Testers
Release Testers
Posts: 12
Joined: August 27th, 2009, 5:53 am

Re: Errors occurred.

Post by thora »

Hi.

Again, I have the same problem when I download a largest file (9307 Mb) here, with the lasted version of Sabnzbd.
[url=http://[URL=http://img824.imageshack.us/i/capturewe.jpg/]Image]

Here is the content of the log file :

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] Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus
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
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 "SABnzbd.py", line 1240, in <module>
  File "SABnzbd.py", line 1182, in main
  File "sabnzbd\__init__.pyo", line 747, in check_all_tasks
  File "sabnzbd\downloader.pyo", line 100, in check
  File "sabnzbd\decorators.pyo", line 31, in newFunction
  File "sabnzbd\downloader.pyo", line 831, in check_timers
  File "sabnzbd\downloader.pyo", line 319, in init_server
IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in <module>
  File "SABnzbd.py", line 1199, in main
  File "sabnzbd\__init__.pyo", line 756, in check_all_tasks
  File "sabnzbd\downloader.pyo", line 100, in check
  File "sabnzbd\decorators.pyo", line 31, in newFunction
  File "sabnzbd\downloader.pyo", line 831, in check_timers
  File "sabnzbd\downloader.pyo", line 315, in init_server
IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
Traceback (most recent call last):
  File "SABnzbd.py", line 1257, in <module>
  File "SABnzbd.py", line 1199, in main
  File "sabnzbd\__init__.pyo", line 756, in check_all_tasks
  File "sabnzbd\downloader.pyo", line 100, in check
  File "sabnzbd\decorators.pyo", line 31, in newFunction
  File "sabnzbd\downloader.pyo", line 831, in check_timers
  File "sabnzbd\downloader.pyo", line 315, in init_server
IndexError: list index out of range
C:\Program Files (x86)\SABnzbd\lib\sabnzbd.zip\cherrypy\process\wspbus.py:174: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.
Exception in thread Thread-3 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "threading.pyo", line 488, in __bootstrap_inner
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Errors occurred.

Post by shypike »

Did you do any server changes during the downloading?
Post Reply