SABnzbd Forums

Posted: **February 24th, 2014, 10:28 am**

I added some shows to the queue and noticed about 30 of these:

09:26:18,119::ERROR::[database:111] SQL Command Failed, see log

Here is the rest surrounding that error:

Code: Select all

2014-02-24 09:26:18,119::ERROR::[database:111] SQL Command Failed, see log
2014-02-24 09:26:18,123::DEBUG::[database:112] SQL: select count(*) from History WHERE name LIKE ?
2014-02-24 09:26:18,123::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)
DatabaseError: database disk image is malformed
2014-02-24 09:26:18,124::ERROR::[database:111] SQL Command Failed, see log
2014-02-24 09:26:18,124::DEBUG::[database:112] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2014-02-24 09:26:18,125::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)
DatabaseError: database disk image is malformed

Posted: **February 24th, 2014, 10:39 am**

Had you already answered my question 'What is the output of "mount"?' ?

I really think the problem is in your filesystem, or some other proces accessing SAB's files/directories.

Posted: **February 24th, 2014, 10:53 am**

I'm not sure this is the same issue, but I added to this thread since it was DB related.

I did not get the permissions issue this time. Just the DB disk image issue, which is new.

I stopped the service, removed the existing history1.db and restarted. Not seeing the error, but that doesn't really help us get to the root of all this.

P.S. I moved the folder that was causing the "cannot read" error before to a new location that is not encrypted, and I haven't seen the error since.

SABnzbd Forums

permission error followed by DB error then crash

Re: permission error followed by DB error then crash

Re: permission error followed by DB error then crash

Re: permission error followed by DB error then crash