I was just setting up Mpsync on a third system, and I didn't get it to work.
Somehow, when I wanted to sync folders, mpsync wouldn't remember them for some reason, and it went in an infinite loop (don't know exactly which, didn't enable debug logging).
Could very well be that I messed it up a bit, will dive into that when a more urgent problem is solved.
Don't know how I got it as it is right now, but when I sync my (master)client to my server it doesn't get out of the loop
You said a couple of pages earlier that when that was the case, that probably one of the databases (actually I only sync movingpictures) is corrupt, and deleting it from the server and syncing again would solve the problem.
When I did that, I got a lot of errors that tables and such could not be found, and a movingpictures.db3 with filesize 0.
Then I thought to be clever and manually copied the movingpictures.db3 from the (master)client to the server, and did a sync again. This resulted in the same (infinite?) loop of waiting for background threads to finish.
Any ideas?
Edit: Moving pictures doesn't seem to have any problem running on my (master)client, so does that mean that at least my source database isn't corrupt?
Edit2: renamed server/nas to more appropriate terms. In this described case, I'm syncing from (master)client to server
Somehow, when I wanted to sync folders, mpsync wouldn't remember them for some reason, and it went in an infinite loop (don't know exactly which, didn't enable debug logging).
Could very well be that I messed it up a bit, will dive into that when a more urgent problem is solved.
Don't know how I got it as it is right now, but when I sync my (master)client to my server it doesn't get out of the loop
Code:
[DEBUG] MPSync: [Process_DB_folder] waiting for background threads to finish... 1 threads remaining processing {movingpictures.db3}.
You said a couple of pages earlier that when that was the case, that probably one of the databases (actually I only sync movingpictures) is corrupt, and deleting it from the server and syncing again would solve the problem.
When I did that, I got a lot of errors that tables and such could not be found, and a movingpictures.db3 with filesize 0.
Then I thought to be clever and manually copied the movingpictures.db3 from the (master)client to the server, and did a sync again. This resulted in the same (infinite?) loop of waiting for background threads to finish.
Any ideas?
Edit: Moving pictures doesn't seem to have any problem running on my (master)client, so does that mean that at least my source database isn't corrupt?
Edit2: renamed server/nas to more appropriate terms. In this described case, I'm syncing from (master)client to server
Attachments
Last edited: