SyncDb: failed to execute query to save file info

Dantounet · July 17, 2013

Hi,

I have a lot of "SyncDb: failed to execute query to save file info" in my logs on my arm machines since I upgraded to version 1.1.42.

Is it something I should ignore?

Cheers

Swisstengu · July 18, 2013

Hello,

Same problem in here - and it seems to prevent Sync to work normaly - I have about 340G to sync (from a "master" host to 2 "slaves", and it did only 6.8 on one, 6.2 on the second…

These 340G represent about 149541 files (yes, that much… And this is only a part of the directory I want to keep sync-ed between 20 hosts once it's in production).

I don't know if both problems are related.

Cheers,

C.

GreatMarko · July 18, 2013

I have a lot of "SyncDb: failed to execute query to save file info" in my logs on my arm machines since I upgraded to version 1.1.42.

What version of Sync were you using prior to 1.1.42? If it was a much earlier version, it may be that the database hasn't upgraded properly when you updated to 1.1.42, or that the database has somehow become corrupt.

You may be able to resolve it by simply removing the folder(s) in question from Sync, and then re-adding it again. This will cause a re-index of the folder, and therefore should rebuild the associated database.

Dantounet · July 18, 2013

Ah indeed, upgraded from 1.1.27. How can I guess what folder is corrupted ?

Dantounet · July 18, 2013

Hi,

I am working on the ARM version with a config file. I stopped btsync, removed the .SyncID and restarted it but I still have the same error.

Should I remove the folder from btsync and start btsync without it and then re-add it and restart btsync ?

Swisstengu · July 18, 2013

ok - indexing is running (fast) right now - we will see if this solves the problem.

@dantounet: how many files do you manage through sync? Maybe we (or I) reached some limit somewhere?

Cheers,

C.

GreatMarko · July 18, 2013

@dantounet: how many files do you manage through sync? Maybe we (or I) reached some limit somewhere?

Unlikely, as there are no restrictions (other than the physical space on your drive) on the number of files you can Sync

miouhpi · July 18, 2013

Getting a lot of these messages as well, on all 3 my machines.

All machines are Archlinux x86_64 (fully up to date) running 1.1.42 (upgraded from 1.1.15 a few days ago)

Since the upgrade sync has stopped working entirely for certain shares,

tried deleting all the metadata in the storage_path and rebuilding the indexes, but same problem shows up.

Haven't tried deleting the .SyncId in the shares themselves, would that make a difference?

Swisstengu · July 18, 2013

I didn't upgrade Sync on the servers I'm testing. Not really sure it's due to the update itself, seems to be a application problem in the 1.1.42 itself.

Swisstengu · July 19, 2013

hmm… seems there's really some issue:

my sync was stuck this night at ~38-40G (about 10%), sync.log was full of SyncDB errors…

I looked in the DB, there are about 3k+ file entries missing in the "files" table - this, for sure, doesn't make 300G, but…

Any hint from the Team would be welcome .

Cheers,

C.

sergey@bt · July 19, 2013

What platform do you use? Is it Linux specific? We added more logging into recent builds. It may be the reason why you started to see it in log.

Dantounet · July 19, 2013

Hi,

As said above it happens on my ARM (yes linux) machines. I have two of them and it happened on both of them.

I have no pb on my linux 64bit though.

I have cleaned the metadata and SyncID on both machines but the error is still logged on the raspberry pi (but it's fine on the synology).

Should I send the logs ?

sergey@bt · July 19, 2013

Do you use config file or run Sync with default configuration? Do you use single UID/GID for btsync binary and files?

We saw such error on Android when sqlite was not able to find folder for temporary files. In Linux we set it to the same path where database itself is stored (storage_path in config file or .sync in current process folder by default).

Dantounet · July 19, 2013

Hi,

I use the config file to setup btsync and the folders (web ui is off). I have not moved the default folder (it's in ~/.sync as for default configuration). btsync is ran with pi uid and ~/.sync belongs to pi user (I'm on raspbian).

As it is on a raspberry the performance is very poor (I do not mind but maybe it's the issue).

sergey@bt · July 19, 2013

Could you please try this ARM build: http://syncapp.bittorrent.com/4test/btsync_arm.gz ?

I've added error codes to all DB related log messages.

Dantounet · July 19, 2013

Hi Sergey,

Alright, I am using it. However I have cleaned up the whole btsync setup on my raspberry pi and also stopped using zfs and back to ext4 as it was overkill.

No error for now, I'll send logs if I see any error.

cheers,

root · July 21, 2013

The same issue:

FreeBSD 9.1

BTsync: 1.1.42

Fresh install, just a few test folders and up to 20 files all together.

config:


{
  "device_name"       : "fs754",
  "listening_port"    : 12345,
  "storage_path"      : "/var/db/btsync/s01",
  "pid_file"          : "/var/run/btsync.pid",
  "check_for_updates" : false,
  "use_upnp"          : false,
  "download_limit"    : 0,
  "upload_limit"      : 0,
  "webui" :
  {
    // "listen" : "0.0.0.0:8888", // remove "listen" field to disable WebUI
    "login"    : "admin",         // remove "login" and "password" fields to disable credentials check
    "password" : "password"
  },
  "shared_folders" : 
  [
    {
      "secret" : "Supper-Dupper-key",
      "dir" : "/usr/home/share",
      "use_relay_server" : false,
      "use_tracker" : false,
      "use_dht" : false,
      "search_lan" : false,
      "use_sync_trash" : true,
      "known_hosts" : [
        "FQDN:12345"
      ]
    }
  ]

}

sync.log:


[20130621 03:57:15.026] Loading config file version 1.1.42
[20130621 03:57:15.048] SyncDb: Failed to init db
[20130621 03:57:15.048] Loaded folder /usr/home/share
[20130621 03:57:15.051] SyncDb: Failed to init db
[20130621 03:57:15.051] Loaded folder /usr/home/share
[20130621 03:57:15.052] SyncDb: Failed to init db
[20130621 03:57:15.052] Loaded folder /usr/home/share
[20130621 03:57:15.053] SyncDb: Failed to init db
[20130621 03:57:15.053] Loaded folder /usr/home/share
[20130621 03:57:15.054] SyncDb: Failed to init db
[20130621 03:57:15.054] Loaded folder /usr/home/share
[20130621 03:57:16.120] SyncDb: failed to prepare query to save metadata
[20130621 03:57:16.123] SyncDb: failed to prepare query to save metadata
....
[20130621 04:07:15.134] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.134] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.134] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.134] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.134] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.134] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.135] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.136] SyncDb: failed to prepare query to save file info
[20130621 04:07:15.136] SyncDb: failed to prepare query to save file info

paperdigits · July 21, 2013

I am having this same problem.

I tried removing the .SyncID, but that didn't help. Finally, I commented out the "storage_path" in my config file, and it is still not working.

I am using the i386 linux build trying to sync from OS X 10.6.8. Using btsync 1.1.42.

What is the best way to exit btsync, since I'm not using the web gui? I've just been using "pkill btsync" but I'm thinking that might cause the problem?

axllent · July 22, 2013

I'm getting this exact same issue with the LInux i386 build on a Debian Squeeze VPS. It's causing all kinds of sync issues - new files not all getting added etc. I have another amd64 box (also with Squeeze) which works fine - both running 1.1.42

The only noticeable difference is that the i386 machine doesn't run the web interface - configured through a config file. The other box is configured through the web.

{
		"device_name": "Data Server",
		"listening_port" : 0,
		"storage_path" : "/home/user/.sync",
		"check_for_updates" : true,
		"use_upnp" : true,
		"download_limit" : 0,
		"upload_limit" : 0,
		"shared_folders" :
				[
						{
								"secret" : "xxxx",
								"dir" : "/home/user/data/",
								"use_relay_server" : true,
								"use_dht" : false,
								"search_lan" : false,
								"use_sync_trash" : false
						}
				]
}

Dantounet · July 22, 2013

Error is reoccuring on my synology NAS after I restarted btsync because I added a folder.

sergey: I was using your binary. Log file can be found here: http://dante.kollok.org/sync.log

Restarting btsync with debug activated now.

sergey@bt · July 22, 2013

Dantounet, can you please try new new build from here: http://syncapp.bittorrent.com/1.1.43/ ?

paperdigits · July 23, 2013

The above 1.1.43 seems to have fixed my problem.

axllent · July 23, 2013

1.1.43 Seems to have fixed mine too, though with no debug output at all it's hard to tell, but 24h later I haven't noticed any issues yet.

sergey@bt · July 23, 2013

1.1.43 does not fully fix it. Please use http://syncapp.bittorrent.com/1.1.46/ if you see this issue. There was a race condition when working with config file which could cause adding the same folder twice.

Dantounet · July 23, 2013

No issue with 1.1.46 for now.

Sign In

SyncDb: failed to execute query to save file info

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation