huge .moneydancesync folder (781mb)
I just cleaned up my sync situation recently (recreated sync hosts and am using Dropbox Folders). All of a sudden, one of my .moneydancesync folders is 781MB. There are a bunch of "conflicted copy" .txt files and under the v3 folder there are a handful of huge .mdtxn files, two are 771mb each.
I had been working with MD (5007) on a Mac Mini containing a sync copy of my MD data and no other copies of MD are open/running.
Should I be worried (again)?
Showing page 2 out of 2. View the first page
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
31 Posted by Milo C on 08 Aug, 2023 12:05 AM
So... I recreated the sync after stopping sync on the Master and then deleting the GUID folders inside the Dropbox ".moneydancesync" folder. Then I went to my Secondary computer and created a new account set and specified DropboxFolder. Waited for it to finish initial sync.
The first strange thing I saw is that, in one of my checking accounts, two duplicate transactions appeared in the Secondary that were not (I think!) in the Master before I setup the sync.
Next, I saw them in the Master. I deleted them in the Master, but only 1 of the 2 disappeared in the Secondary.
Finally, it's only been a few minutes, and I see two "conflicted copy" versions of mdsyncinfo.txt in the sync folder. One is labeled with the Master computer's name, the other with the Secondary's.
I don't see any errors in the Console.
32 Posted by Milo C on 08 Aug, 2023 12:14 AM
With MD open in both computers, I deleted the one dupe txn on the Secondary, saved, then saved in Master (Cmd-S), and I see a new "conflicted copy" mdsyncinfo.txt in the sync folder.
No errors in either Console.
33 Posted by Stuart Beesley ... on 08 Aug, 2023 05:43 AM
Yes. I can see how both online computers are updating that file and potentially causing a conflict. But that file does not matter (too much). And I’m pretty certain that all other files will be unique…. Perhaps… keep an eye on it and both consoles.
34 Posted by Milo C on 08 Aug, 2023 11:21 PM
Here's an exception I got in Console, shortly after starting the Secondary today.
35 Posted by Stuart Beesley ... on 09 Aug, 2023 05:01 AM
This is a problem:
I suspect it will continue to error after each restart. It's a bad mobile app txn file..
Can you grab latest toolbox from:
https://yogi1967.github.io/MoneydancePythonScripts/
and then use advanced, decrypt file from sync. Find this fix, decrypt to file.. Then upload that file here.. By all means look at it in a text editor first. It shouldn't contain anything too secret!
36 Posted by Milo C on 09 Aug, 2023 01:08 PM
Unfortunately (or not), that file is gone (I searched the Secondary dataset (.../safe/tiksync/out folder is empty).
How did you know that this came from mobile app? I have the mobile MD app installed on my iPad but it doesn't really add much value. If it's the cause of any corruption I would be more than happy to uninstall it.
37 Posted by Stuart Beesley ... on 09 Aug, 2023 02:02 PM
Actually you may be right that it’s not mobile app. If you restart MD, do you get the same (ish) error in console?
38 Posted by Milo C on 09 Aug, 2023 02:36 PM
Nope. There's nothing in the "tiksync/out" folder in the Master or
Secondary datasets now. It disappeared. I'm not aware of any adverse
effect, but it's hard for me to track every single action I do in all MD
clients...
39 Posted by Stuart Beesley ... on 09 Aug, 2023 02:37 PM
OK, well the encryption error is not a good thing. This means somehow the txn file got corrupted (not written properly) after a change was made. You need to keep an eye on this.
System closed this discussion on 08 Nov, 2023 02:40 PM.