“Failed to connect: SQLite error no such table: LogData”

I am getting the following message when trying to review the error messages from my backup (the pop up that comes up on the bottom center of the scree).

“Failed to connect: SQLite error no such table: LogData”

The db for the actual backup is not in the default location, but is correct. I can see some logs when I click on “Logs” on the left hand side, but not when I click on “Show” on the message that pops up after a backup. Seems to be happening to all backups… I am trying to resolve some inconsistencies with the backups.

Anyone got any ideas to resolve this error?

Also always getting “connection lost” not a big issue, just gets annoying. By the way, this is installed on my Synology NAS…

Normally this happens when the database is new, as it has not yet created the table. Once a backup has run it should go away.

Do you still have the problem?

Yea, still happening… Its backed up several times…I also manually ran it and it comes back with same message.

Very odd. If you use something like SQLite Browser to open the database, do you see the log tables?

yea it does have the table and has data in it. Last entry is below for Apps. I do not see this when I click logs, unless I am blind and missing it

DeletedFiles: 0
DeletedFolders: 0
ModifiedFiles: 0
ExaminedFiles: 114706
OpenedFiles: 0
AddedFiles: 0
SizeOfModifiedFiles: 0
SizeOfAddedFiles: 0
SizeOfExaminedFiles: 1005219887684
SizeOfOpenedFiles: 0
NotProcessedFiles: 0
AddedFolders: 0
TooLargeFiles: 0
FilesWithError: 0
ModifiedFolders: 0
ModifiedSymlinks: 0
AddedSymlinks: 0
DeletedSymlinks: 0
PartialBackup: False
Dryrun: False
MainOperation: Backup
CompactResults: null
DeleteResults:
DeletedSets:
Dryrun: False
MainOperation: Delete
CompactResults: null
ParsedResult: Success
EndTime: 12/10/2017 18:36:02
BeginTime: 12/10/2017 18:33:09
Duration: 00:02:53.2486460
BackendStatistics:
RemoteCalls: 5
BytesUploaded: 0
BytesDownloaded: 217626519
FilesUploaded: 0
FilesDownloaded: 3
FilesDeleted: 0
FoldersCreated: 0
RetryAttempts: 0
UnknownFileSize: 0
UnknownFileCount: 0
KnownFileCount: 7081
KnownFileSize: 742226086341
LastBackupDate: 12/08/2017 01:48:32
BackupListCount: 3
TotalQuotaSpace: 0
FreeQuotaSpace: 0
AssignedQuotaSpace: -1
ParsedResult: Success
RepairResults: null
TestResults:
MainOperation: Test
Verifications: [
Key: duplicati-20171208T114832Z.dlist.zip.aes
Value: ,
Key: duplicati-i7b206a73564546b1b6362d89f058ec13.dindex.zip.aes
Value: ,
Key: duplicati-be241bc4e74a646558fd5ac6ebef859d8.dblock.zip.aes
Value:
]
ParsedResult: Success
EndTime: 12/10/2017 18:37:47
BeginTime: 12/10/2017 18:36:23
Duration: 00:01:24.3183790
ParsedResult: Success
EndTime: 12/10/2017 18:37:48
BeginTime: 12/10/2017 18:26:11
Duration: 00:11:36.1658610
Messages: [
No remote filesets were deleted,
removing file listed as Temporary: duplicati-b634d4590c945444ebc838c0998407895.dblock.zip.aes,
removing file listed as Temporary: duplicati-id724d393dd424ae39a39915910c54f20.dindex.zip.aes
]
Warnings:
Errors:

here is what I see in my logs (all are dated today)…

Dec 10, 2017 8:46 AM: Request for http://192.168.3.7:5000/api/v1/backup/8/log?pagesize=100 gave error
Mono.Data.Sqlite.SqliteException (0x80004005): SQLite error
no such table: LogData
at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, System.UInt32 timeoutMS, System.String& strRemain) [0x00236] in <62e44d67e13348a795e30fd7dd8622df>:0
at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00059] in <62e44d67e13348a795e30fd7dd8622df>:0

Dec 10, 2017 8:46 AM: Reporting error gave error
System.ObjectDisposedException: Cannot write to a closed TextWriter.
at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0
at System.IO.StreamWriter.Flush () [0x00006] in <8f2c484307284b51944a1a13a14c0266>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x003aa] in :0

Dec 10, 2017 8:44 AM: Request for http://192.168.3.7:5000/api/v1/backup/11/log?pagesize=100 gave error
Mono.Data.Sqlite.SqliteException (0x80004005): SQLite error
no such table: LogData
at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, System.UInt32 timeoutMS, System.String& strRemain) [0x00236] in <62e44d67e13348a795e30fd7dd8622df>:0
at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00059] in <62e44d67e13348a795e30fd7dd8622df>:0

Dec 10, 2017 8:44 AM: Reporting error gave error
System.ObjectDisposedException: Cannot write to a closed TextWriter.
at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0
at System.IO.StreamWriter.Flush () [0x00006] in <8f2c484307284b51944a1a13a14c0266>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x003aa] in :0

Dec 10, 2017 8:35 AM: Reporting error gave error
System.ObjectDisposedException: Cannot write to a closed TextWriter.
at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0
at System.IO.StreamWriter.Flush () [0x00006] in <8f2c484307284b51944a1a13a14c0266>:0
at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMethods.RequestInfo info, System.String method, System.String module, System.String key) [0x003aa] in :0

Dec 10, 2017 8:35 AM: Request for http://192.168.3.7:5000/api/v1/backup/5/log?pagesize=100 gave error
Mono.Data.Sqlite.SqliteException (0x80004005): SQLite error
no such table: LogData
at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, System.UInt32 timeoutMS, System.String& strRemain) [0x00236] in <62e44d67e13348a795e30fd7dd8622df>:0
at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00059] in <62e44d67e13348a795e30fd7dd8622df>:0

Let me know if you need any other info or logs… Thanks for your help :slight_smile:

I see you have backups 5, 11, and 8 showing up with the error.
Do you know what ID the “Apps” backup has?

Yes, its all my software… alos of software install files and ISO.

If you click on it and “edit” the job, what is the last number you see in the URL ?

Hi Ken,

Sorry for the delay… I am running it on a Synology NAS. But exporting and opening it, id is 9… Not sure what default port is… 8200, 8300, 8400, 8500 not working… From what I read, 8200 is default but might be higher. Am I wrong?

I should note, and realized, I made one job, exported it, and edited the files, then imported them… Should I edit the IDs and re-order it? It looks like it changed it automatically.

The Connection lost is kind of irritating, is there a reason I keep getting that when working with the jobs?

Also noticed when trying to restore any of the backups, I get the error “Failed to connect: Gateway Time-out” …

I am thinking something else is going wrong here. There are no errors from backup 9 in your list above. I don’t know why you “export” anything here.

The ID’s are assigned internally, you cannot change them (and it would cause problems if you could).

Not fully sure. Usually “connection lost” means that the server has crashed.

I am using the Synology version… Opening up dupliciti does not open in a separate window, therefore I cannot see the id number in the address bar

This is an old thread, but I just encountered almost exactly the same error. The olnly difference is that the message is: “Failed to connect: SQL logic error or missing database no such table: LogData”. New Duplicati installation on PC Windows 10 1803 x64, backing up to a “local” folder that’s actually a QNAP NAS folder, using \NAS0\folder syntax. Database and temporary path folders are custom using Advanced Options.

Was there ever a resolution of this problem please? Thanks!

Hello @FlyingBear, welcome to the forum!

The “no such table: LogData” error usually happens in the rare case where you have a new job where an error / warning happens BEFORE the database has been fully populated. Since the LogData table hasn’t yet been created attempting to log the event causes a critical error resulting in what you experienced.

Of course I could be wrong and there is something else going on - can you confirm that the message is “…SQL logic error…” as you posted and not “…SQLite error…” as the original post has?

Has this job ever run correctly (in which case maybe your custom database path is at fault) or has it always failed?

Yes, I cut and paste the message from the popup, so it is different from the original in this thread. The job ran correctly twice, but now fails consistently with this message. The backup itself appears correct. I’m still just testing before using Duplicati in anger, so no lost data here.

Deleting and rebuilding the database doesn’t fix the problem.

Just in case I’m doing something stupid, the dbpath is D:\Main\Duplicati\Secure\Secure.sqlite

Is this a forward-slash, backwards=slash thing perhaps?

I deleted the backup job, uninstalled Duplicati, deleted all files, and reinstalled Duplicati. The same problem occurred. When I create a new job that does NOT use a custom dpath, all is well.

That looks like a valid Windows path to me, so I don’t think that’s the issue.

If you go into the now working / non-customized dbpath job and use the Database link it should take you to a page with database maintenance type buttons on it.

Try changing the “Local database path” field to where you want the database to be stored then clicking the “Move existing database” button. Does that work (yay) or give you an error (perhaps the account Duplicati is running under doesn’t have permission to your “Secure” folder)?

Yay! It worked. Many thanks.

Glad to hear it!

So it sounds like either the manually entered custom dbpath wasn’t quite matching the actual one OR manually moving the file didn’t give the same permissions as having Duplicati do it.

Either way, I’ve flagged my post as the “Solution” - please let me know if you disagree.