Page 1 of 1

error log keeps filling up with same error

Posted: August 31st, 2012, 12:01 pm
by bobbintb
every download i get this error a bunch. what does it mean?

Code: Select all

Traceback (most recent call last):
  File "/boot/sabnzbd/sabnzbd/database.py", line 83, in execute
    self.c.execute(command, args)
OperationalError: database is locked
2012-08-31 10:59:21,267::ERROR::[database:90] SQL Command Failed, see log
2012-08-31 10:59:21,268::INFO::[database:92] Traceback: 
Traceback (most recent call last):
  File "/boot/sabnzbd/sabnzbd/database.py", line 83, in execute
    self.c.execute(command, args)
OperationalError: database is locked
2012-08-31 10:59:22,289::ERROR::[database:90] SQL Command Failed, see log
2012-08-31 10:59:22,290::INFO::[database:92] Traceback: 
Traceback (most recent call last):
  File "/boot/sabnzbd/sabnzbd/database.py", line 83, in execute
    self.c.execute(command, args)
OperationalError: database is locked
2012-08-31 10:59:23,267::ERROR::[database:90] SQL Command Failed, see log
2012-08-31 10:59:23,267::INFO::[database:92] Traceback: 
Traceback (most recent call last):
  File "/boot/sabnzbd/sabnzbd/database.py", line 83, in execute
    self.c.execute(command, args)
OperationalError: database is locked
2012-08-31 10:59:23,827::ERROR::[database:90] SQL Command Failed, see log
2012-08-31 10:59:23,827::INFO::[database:92] Traceback: 
Traceback (most recent call last):
  File "/boot/sabnzbd/sabnzbd/database.py", line 83, in execute
    self.c.execute(command, args)
OperationalError: database is locked

Re: error log keeps filling up with same error

Posted: August 31st, 2012, 12:57 pm
by shypike
Some problem with the sqlite database file access that contains the history.
Restart SABnzbd.

Re: error log keeps filling up with same error

Posted: August 31st, 2012, 3:44 pm
by bobbintb
yes, but it does it every time i download. doesnt matter how many times i restart.

Re: error log keeps filling up with same error

Posted: August 31st, 2012, 3:58 pm
by shypike
Possibly a minor corruption of the file.
If you don't mind losing your history, you can simply delete the history1.db file.
Otherwise you'll need to use a sqlite tool to unlock.
http://www.sqlite.org/download.html

Re: error log keeps filling up with same error

Posted: August 31st, 2012, 4:04 pm
by bobbintb
i just tried deleting the history file and no change. i am using it on an unraid system which i think installs sabnzbd everytime the system is started. so would i have to unlock it everytime? i would just ignore it but i can get upwards of 20 errors for one file. that can get annoying after a few downloads to see all those errors.

Re: error log keeps filling up with same error

Posted: August 31st, 2012, 5:14 pm
by shypike
Hmm, sounds more like an unraid issue.
I'm afraid I know nothing about that.

Re: error log keeps filling up with same error

Posted: September 3rd, 2012, 6:11 pm
by Influence
Bobbintb, first off I must point out, your data directory is set in /boot which is NOT good, /boot is the mount point for the flash drive you have unraid installed on, and sab will quickly kill the flash drive unless you have manually set the download directories to a different location(relative paths will remain on the flash). This could be part of your issue.

Re: error log keeps filling up with same error

Posted: November 29th, 2012, 6:53 am
by piposmile
Same problem, get it sometimes when klicking on remove for a history entry, at that moment it isn't removed and generates this error,
Normally after klick to remove again, everything works fine again.

Part of the log:

2012-11-29 09:50:42,726::ERROR::[database:111] SQL Command Failed, see log
2012-11-29 09:50:43,263::INFO::[database:113] Traceback:
Traceback (most recent call last):
File "/usr/share/sabnzbdplus/sabnzbd/database.py", line 104, in execute
self.c.execute(command, args)
OperationalError: database is locked

Re: error log keeps filling up with same error

Posted: November 29th, 2012, 2:29 pm
by shypike
Likely a bug in the sqlite library.
It's sometimes reported for Linux, never for Windows or OSX.
Usually a reboot fixes things.
I have looked at it in the past, but still don't have a clue why it happens.