Hello,
I currently run SABNZBD 0.6.14 on an Unraid box. It is connected to a Sickbeard installation to automatically download shows. How ever it has not worked properly for a few days now. If I manually add an NZB it works fine but the NZB's I receive from Sickbeard are failing with the following message
» URL Fetching failed; (Problem accessing nzbmatrix server (error:no_nzb_found)), Try again
When I try again it still doesn't work.
The sabnzbd also displays the following warning
2012-04-03 11:18:07,131 ERROR: SQL Command Failed, see log
2012-04-03 11:18:07,130::INFO::[__init__:829] /mnt/disk1/.custom/sabnzbd/admin/future/SABnzbd_nzo_cbbz-i removed
2012-04-03 11:18:07,131::ERROR::[database:89] SQL Command Failed, see log
2012-04-03 11:18:07,131::INFO::[database:91] Traceback:
Traceback (most recent call last):
File "/mnt/disk1/.custom/sabnzbd/sabnzbd/database.py", line 82, in execute
self.c.execute(command, args)
OperationalError: database is locked
2012-04-03 11:18:07,279::INFO::[nzbqueue:167] Saving queue
2012-04-03 11:18:07,279::INFO::[__init__:840] Saving data for queue9.sab in /mnt/disk1/.custom/sabnzbd/admin/queue9.sab
Any suggestions as what could be wrong. I tried a reboot but it did not make a difference.
Please let me know if you require any further information.
Thanks in advance.
SQL Command Failed, see log
Forum rules
Help us help you:
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.
Re: SQL Command Failed, see log
The nzbmatrix problems are known. nzbmatrix is very reliable currently and SABnzbd gives up too fast.
The sql error can be resolved by stopping SABnzbd and removing the file admin/history1.db
That is, if you don't mind losing the download history.
If not, possibly a sqlite tool can help to unlock the database.
The sql error can be resolved by stopping SABnzbd and removing the file admin/history1.db
That is, if you don't mind losing the download history.
If not, possibly a sqlite tool can help to unlock the database.