ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

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.
Post Reply
rorrantia
Newbie
Newbie
Posts: 7
Joined: February 12th, 2018, 7:14 am

ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

Post by rorrantia »

Hello, been using SABnzb for a while on a QNAP 453 mini, without incident but suddenly started getting this error message:
SQL Command Failed, see log
.
My Discs are NOT full and all the files are set to 777.

When i checked my logs I get the following:

Code: Select all

2018-02-10 08:43:00,452::INFO::[database:155] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2018-02-10 08:43:00,452::INFO::[database:156] Arguments: ('%%', 0, 1000000)
2018-02-10 08:43:00,453::INFO::[database:157] Traceback: 
Traceback (most recent call last):
  File "/share/CACHEDEV1_DATA/.qpkg/SABnzbdplus/SABnzbdplus/sabnzbd/database.py", line 125, in execute
    self.c.execute(command, args)
OperationalError: database or disk is full
2018-02-10 08:43:21,725::ERROR::[database:154] SQL Command Failed, see log
2018-02-10 08:43:21,726::INFO::[database:155] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2018-02-10 08:43:21,726::INFO::[database:156] Arguments: ('%%', 0, 1000000)
2018-02-10 08:43:21,727::INFO::[database:157] Traceback: 
Traceback (most recent call last):
  File "/share/CACHEDEV1_DATA/.qpkg/SABnzbdplus/SABnzbdplus/sabnzbd/database.py", line 125, in execute
    self.c.execute(command, args)
OperationalError: database or disk is full
2018-02-10 08:43:21,902::ERROR::[database:154] SQL Command Failed, see log
2018-02-10 08:43:21,903::INFO::[database:155] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2018-02-10 08:43:21,903::INFO::[database:156] Arguments: ('%%', 0, 1000000)
2018-02-10 08:43:21,904::INFO::[database:157] Traceback: 
Traceback (most recent call last):
  File "/share/CACHEDEV1_DATA/.qpkg/SABnzbdplus/SABnzbdplus/sabnzbd/database.py", line 125, in execute
    self.c.execute(command, args) 
Thank you in advanced for any help provided.
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: ERROR: SQL Command Failed, see log

Post by sander »

/share/CACHEDEV1_DATA/... ... what kind of disk is that? A NAS?
rorrantia
Newbie
Newbie
Posts: 7
Joined: February 12th, 2018, 7:14 am

Re: ERROR: SQL Command Failed, see log

Post by rorrantia »

sander wrote: February 12th, 2018, 9:01 am /share/CACHEDEV1_DATA/... ... what kind of disk is that? A NAS?
Yes it is a QNAP 453 Mini running Raid 5
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: ERROR: SQL Command Failed, see log

Post by sander »

rorrantia wrote: February 12th, 2018, 9:29 am
sander wrote: February 12th, 2018, 9:01 am /share/CACHEDEV1_DATA/... ... what kind of disk is that? A NAS?
Yes it is a QNAP 453 Mini running Raid 5
Ah, I see.

It's best practise to put SAB's Incomplete and the 'system' directory on a local disk. Otherwise you can expect problems, like you're experiencing now; if there is a glitch in the NAS connection, all kinds of things can happen.
User avatar
OneCD
Hero Member
Hero Member
Posts: 557
Joined: March 4th, 2017, 3:47 pm

Re: ERROR: SQL Command Failed, see log

Post by OneCD »

CACHEDEV1_DATA is QNAP’s name for the first array. It’s where all data is stored. There’s no-where else to put it. ;)
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: ERROR: SQL Command Failed, see log

Post by sander »

OneCD wrote: February 12th, 2018, 10:05 am CACHEDEV1_DATA is QNAP’s name for the first array. It’s where all data is stored. There’s no-where else to put it. ;)
Do you mean SABnzbd is running on that NAS? So the disk is local?
User avatar
OneCD
Hero Member
Hero Member
Posts: 557
Joined: March 4th, 2017, 3:47 pm

Re: ERROR: SQL Command Failed, see log

Post by OneCD »

If by local you mean not remote, then yes.
Stuff I like: Apache bash cron DD-WRT Debian DNSMasq Entware FireFox GitHub ImageMagick Kate KDE LibreELEC Netrunner NFS NVIDIA OpenVPN Orvibo-S20 pfSense Python Raspberry-Pi RAID SABnzbd Transmission Usenet VirtualBox Watcher3 XFCE
rorrantia
Newbie
Newbie
Posts: 7
Joined: February 12th, 2018, 7:14 am

Re: ERROR: SQL Command Failed, see log

Post by rorrantia »

sander wrote: February 12th, 2018, 10:08 am
OneCD wrote: February 12th, 2018, 10:05 am CACHEDEV1_DATA is QNAP’s name for the first array. It’s where all data is stored. There’s no-where else to put it. ;)
Do you mean SABnzbd is running on that NAS? So the disk is local?
Yes it is running on the NAS, it is local.
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

Post by sander »

If you google "OperationalError: database or disk is full", there are a lot of useful links, especially in combination with QNAP

And I would check the size of 'history.db' and the other files in the admin folder.
rorrantia
Newbie
Newbie
Posts: 7
Joined: February 12th, 2018, 7:14 am

Re: ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

Post by rorrantia »

sander wrote: February 12th, 2018, 10:27 am If you google "OperationalError: database or disk is full", there are a lot of useful links, especially in combination with QNAP

And I would check the size of 'history.db' and the other files in the admin folder.
Thank you for all your help sander and thanks to OneCD on both forums :) It is very much appreciated!
It seems fixed for now, had to do a drastic fix but seems to be working correctly...
Will have to wait and see if it is working after a while and a few files.
But for now what I did was delete the history1.db found in

Code: Select all

/share/CACHEDEV1_DATA/.qpkg/SABnzbdplus/config/admin
and reinstalled SABnzb using the GREAT Sherpa script that OneCD has made for QNAP

Code: Select all

https://forum.qnap.com/viewtopic.php?f=320&t=132373
.
Sure you loose the history found on SABnzb, but I at least do not need it.
Have tested a few files and no error, so it might be a DB corruption of some sort? Will post back if it works on a longer term for others who might have the same problems.
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

Post by sander »

But for now what I did was delete the history1.db found in
Ah, yes, good one.

Before deleting, did you check the size of history1.db ?
and reinstalled SABnzb
No need for that; SABnzbd can start without history1.db ... it will create a fresh one.
macvirii
Newbie
Newbie
Posts: 1
Joined: February 14th, 2018, 3:21 am

Re: ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

Post by macvirii »

I had the same problem, actually my history1.db was only 1.023kb
My problem derived from tmpfs /temp/ full (it seems it was a Radarr update unsuccessful that filled the partition.
After deleting both backup and update (with winscp) , my SABnzb started working again.
User avatar
sander
Release Testers
Release Testers
Posts: 8811
Joined: January 22nd, 2008, 2:22 pm

Re: ERROR: SQL Command Failed, see log: OperationalError: database or disk is full

Post by sander »

macvirii wrote: February 14th, 2018, 3:25 am I had the same problem, actually my history1.db was only 1.023kb
My problem derived from tmpfs /temp/ full (it seems it was a Radarr update unsuccessful that filled the partition.
After deleting both backup and update (with winscp) , my SABnzb started working again.
Yep, full temp is one of the reasons for sqlite to fail.

Thanks for your post.
Post Reply