070b3: ERROR: SQL Command Failed, see log

[sander]

Running 070b3, although I don't know if this is 070b3 related. But I must say it did not happen in the past (AFAIK).

Tips? Should I clean up the SQL database?

Code: Select all

sander@R540:~/.sabnzbd/logs$ grep -i sql sabnzbd.log
2012-04-19 21:47:25,119::ERROR::[database:90] SQL Command Failed, see log
2012-04-19 21:47:25,120::DEBUG::[database:91] SQL: select count(*) from History WHERE name LIKE ?
2012-04-19 21:47:30,128::ERROR::[database:90] SQL Command Failed, see log
2012-04-19 21:47:30,128::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
sander@R540:~/.sabnzbd/logs$ 

[shypike]

No idea.
Nothing has changed in database handling for quite some time.

[sander]

Checking: the only database is history1.db, right? So the problem is in there? And if move that file history1.db, I can start fresh?

What's the format of the .sab files? Not SQLIte3, or is it?

[shypike]

The db file is a regular SQLite3 database, unrelated to any SAB file (which are mostly Python pickle files).
You can always remove the DB file, it only contains your history.
Although some unfinished items may end up in the orphanage in Status.

[sander]

OK, thanks. I'll try.

BTW: I just used sqlitebrowser (on Ubuntu) to have a look at the .db. Nice browser. And it did not discover problems in the .db file.

[shypike]

The sqlite library sometimes gives error messages, without giving insight in what's the actual cause (or remedy).

[sander]

The sqlite library sometimes gives error messages, without giving insight in what's the actual cause (or remedy).

And what does SAB do in case of an error? Does it retry? In one of the SQL-error cases, the items was missing from History.