SABnzbd Forums

I'm running the latest level of 0.6.9 and seeing these message " SQL Command Failed, see log " every few seconds. When I look in the log I only see the following:

any idea of how to resolve.

2953850880 : timer : (2011-09-26 / 21:04:03.006569) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:04:33.001520) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:05:03.009253) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:05:33.001759) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:06:03.001368) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:06:33.008397) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:07:03.001328) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:07:33.001862) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:08:03.001688) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:08:33.001153) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:09:03.001859) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:09:33.001117) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:10:03.011501) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:10:33.001871) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:11:03.001508) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:11:33.001263) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:12:03.013844) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:12:33.001871) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:13:03.001805) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:13:33.001231) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:14:03.001272) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:14:33.030487) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:15:03.008005) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:15:33.001085) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:16:03.001900) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:16:33.001123) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:17:03.001845) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:17:33.001881) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:18:03.001874) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:18:33.001221) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:19:03.021444) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers.
2953850880 : timer : (2011-09-26 / 21:19:33.001729) : wg_timer_sys_thread: next timer event at 30. There are 0 active timers

Are you sure this message is from SABnzbd itself? I don't recognize "wg_timer_sys_thread", and I can't find it in SAB's source code.

And: which platform are you running SAB on?

That is what is in the log that I downloaded after clicking Show Logging. Below is what I see in my "Lastest Warning" tab. I am running under Windows 7 Ultimate. I've had sab installed for a while now on this machine and have just upgraded as the newer releases come out, this is the first time I've had any issue.

When Type Warning
2011-09-27 06:57:09,690 ERROR: SQL Command Failed, see log
2011-09-27 06:57:09,684 ERROR: SQL Command Failed, see log
2011-09-27 06:57:06,729 ERROR: SQL Command Failed, see log
2011-09-27 06:57:06,724 ERROR: SQL Command Failed, see log
2011-09-27 06:57:02,315 ERROR: SQL Command Failed, see log
2011-09-27 06:57:02,312 ERROR: SQL Command Failed, see log
2011-09-27 06:56:47,242 ERROR: SQL Command Failed, see log
2011-09-27 06:56:47,236 ERROR: SQL Command Failed, see log
2011-09-27 06:56:32,918 ERROR: SQL Command Failed, see log
2011-09-27 06:56:32,913 ERROR: SQL Command Failed, see log
2011-09-27 06:56:17,216 ERROR: SQL Command Failed, see log
2011-09-27 06:56:17,211 ERROR: SQL Command Failed, see log
2011-09-27 06:56:02,232 ERROR: SQL Command Failed, see log
2011-09-27 06:56:02,227 ERROR: SQL Command Failed, see log
2011-09-27 06:55:47,211 ERROR: SQL Command Failed, see log
2011-09-27 06:55:47,207 ERROR: SQL Command Failed, see log
2011-09-27 06:55:32,240 ERROR: SQL Command Failed, see log
2011-09-27 06:55:32,236 ERROR: SQL Command Failed, see log
2011-09-27 06:55:17,266 ERROR: SQL Command Failed, see log
2011-09-27 06:55:17,262 ERROR: SQL Command Failed, see log

Without more info, there's nothing I can say about this.
At a pinch: stop SABnzbd, find the "admin" folder and remove history1.db and start SABnzbd again.
You will lose your download history.

Shypike, thanks for the suggestion. Doing that appears to have resolved my issue.

shypike wrote:Without more info, there's nothing I can say about this.
At a pinch: stop SABnzbd, find the "admin" folder and remove history1.db and start SABnzbd again.
You will lose your download history.

Possibly your installation is damaged.
Some virus scanners and so-called security suits have a grudge against the sqlite3.dll file