ERROR: SQL Command Failed, see log

[stgarf]

The error:

Code: Select all

2010-01-19 03:53:56,917 ERROR: SQL Command Failed, see log

See bottom of post for LINK to error logs and history1.db

Version: (Ex: 0.5.0 beta 4)
OS: MS Server 2008 R2
Install-type: Windows Installer
Skin (if applicable): n/a
Firewall Software: None
Are you using IPV6? on
Is the issue reproducible? Yes, for me. Every beta build has done this on this server.

History in SAB web interface doesn't show when you click on the history page
Also, everytime you click "History" it causes the amount of warnings on the "Connections" page to increase by one.
In the "Connections" page under "Warnings" I have:

Code: Select all

2010-01-19 04:00:01,380 ERROR: SQL Command Failed, see log
2010-01-19 04:00:01,568 ERROR: SQL Command Failed, see log
2010-01-19 04:00:01,786 ERROR: SQL Command Failed, see log

This is from my log file:

Code: Select all

2010-01-19 04:06:04,836::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:04,836::DEBUG::[database:91] SQL: VACUUM
2010-01-19 04:06:04,836::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 85, in execute
OperationalError: unable to open database file
2010-01-19 04:06:04,901::INFO::[_cplogging:55] [19/Jan/2010:04:06:04] ENGINE Serving on 0.0.0.0:8080
2010-01-19 04:06:04,901::INFO::[_cplogging:55] [19/Jan/2010:04:06:04] ENGINE Bus STARTED
2010-01-19 04:06:04,982::DEBUG::[misc:575] Checked for a new release, cur= 50046, latest= 41299 (on http://sourceforge.net/projects/sabnzbdplus/files/)
2010-01-19 04:06:22,812::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:22,812::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:22,813::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:29,157::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:29,157::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:29,157::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:30,990::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:30,992::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:30,992::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:31,561::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:31,561::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:31,561::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:33,252::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:33,253::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:33,253::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:33,930::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:33,930::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:33,930::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:36,213::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:36,213::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:36,213::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file
2010-01-19 04:06:39,046::ERROR::[database:90] SQL Command Failed, see log
2010-01-19 04:06:39,048::DEBUG::[database:91] SQL: SELECT * FROM history WHERE name LIKE ? ORDER BY completed desc LIMIT ?, ?
2010-01-19 04:06:39,048::DEBUG::[database:92] Traceback: 
Traceback (most recent call last):
  File "sabnzbd\database.pyo", line 83, in execute
OperationalError: unable to open database file

Is there any more advanced debugging that can be enabled, no one else seems to have this problem but me.

http://rapidshare.com/files/337648480/S ... istory1.db

[shypike]

Did you complain about this on the IRC channel before?

One team member and one Beta tester tested on Server2008R2
but could not find any issue.
The only thing I can think of is that the OS doesn't allow you
to open the db file. Access rights?
Did you check the Windows system logs, especially logs
about access violations?
Do you have a virus scanner or other security program that's trying to be clever?

[stgarf]

Did you complain about this on the IRC channel before?

One team member and one Beta tester tested on Server2008R2
but could not find any issue.

Yea that was me,
Do you think it matters that it was 64-bit?

The only thing I can think of is that the OS doesn't allow you
to open the db file. Access rights?

This shouldn't be the problem, SAB was installed with an admin account and is being run by an account with enterprise administrator rights.

Did you check the Windows system logs, especially logs
about access violations?

I wouldn't know where to start looking, server 2008 has so many different logs that I can look at.
Heh, at least they are all in one window.

Do you have a virus scanner or other security program that's trying to be clever?

This could be the problem, the server is running ESET Smart Security. I've completely disabled it at the moment and I'll try to reproduce my errors.

Thanks for replying and trying to help.

[shypike]

This could be the problem, the server is running ESET Smart Security. I've completely disabled it at the moment and I'll try to reproduce my errors.

You'll find many more ESET related complaints in this forum

On a personal note: my opinion is that all these security programs cause more problems than they solve.
I now rely on the Microsoft Virusscanner/Firewall/Defender only and Firefox with NoScript.

[stgarf]

This could be the problem, the server is running ESET Smart Security. I've completely disabled it at the moment and I'll try to reproduce my errors.

You'll find many more ESET related complaints in this forum

On a personal note: my opinion is that all these security programs cause more problems than they solve.
I now rely on the Microsoft Virusscanner/Firewall/Defender only and Firefox with NoScript.

Disabling ESET doesn't make a difference with this bug.

[shypike]

Which exact paths are you using?
The database file will be in the sub-folder "admin" of the folder where the sabnzbd.ini file is.
Can you use any tools (e.g. sysinternals collection) to see if another
program might be accessing the history1.db file?

[stgarf]

Which exact paths are you using?
The database file will be in the sub-folder "admin" of the folder where the sabnzbd.ini file is.
Can you use any tools (e.g. sysinternals collection) to see if another
program might be accessing the history1.db file?

The default paths:
C:\Users\steve\AppData\Local\sabnzbd\admin\

I could use a sysinternals tool to check it out but there's no program installed on the server that should be messing around or doing anything in SAB's appdata folder...

What sysinternals utility did you have in mind?

[inpheaux]

The default paths:
C:\Users\steve\AppData\Local\sabnzbd\admin\

A couple nights ago on IRC didn't we move your cache (where history1.db lives) to something like C:\cache ? Did that help, or did it do the same thing as before: work for awhile and then stop working?

[stgarf]

The default paths:
C:\Users\steve\AppData\Local\sabnzbd\admin\

A couple nights ago on IRC didn't we move your cache (where history1.db lives) to something like C:\cache ? Did that help, or did it do the same thing as before: work for awhile and then stop working?

Yea, correct, it worked for a while and stopped working.
I moved it back to "cache" and again, it worked for a while and stopped again.