icloud issues, brctl log files and privacy
Hey all,
I work on three computers and the prospect of syncing them with macOS Sierra in a multi-directional way was a nice new feature for me. Transfer of the first 140 GBs (1TB subscription) went smoothly albeit not really fast. Then things got stuck, so that every day perhaps only 10 files a 1 MB are transferred since probably three weeks. As for transfer strategy, the bulk of data is uploaded from this iMac with a very good connection to the internet. From the other computers I transferred only few files, and they are ok on every Mac. Changing files on the unaffected Macs leads to arriving almost instantly on the affected one, so this direction works.
I tried everything I could find on the web, including restarting, resetting RAMs, signing in/out, stopping timemachine, removing external drives... . I completely wiped everything and started from scratch (I originally copied everything into the icloud folder with rsync -av, so this was easily doable). The same. I assume there are some corrupt/incompatible files that mess things up. I did not try to delete the icloud database in the Library yet, I hoped that this is not required, since I don't really know what will happen if doing so and whether this would wreck the system completely.
When logging the sync with
brctl log -s --wait
I encounter a lot of errors, beside some warnings that also happen now and then on the good Macs. Mostly like this every 2 mins:
[ERROR] 235.689 [2016-12-01 13:28:15.673] send metadata error: <private>
[ERROR] 235.838 [2016-12-01 13:28:15.822] Sync: requestID:4066 failed sending: <private>
Due to the new privacy regulations of macOS, it is not possible to track down which files are affected and clogging the process. I tried to make an rsync --dry-run to check which files are missing, but it's still thousands that do, so no help here in finding the bad ones.
Has anyone a suggestion how to enable the brctl log to include file and path information so that I can take care of these files? I tried to use sudo, but does'nt change a thing. Why is Apple censoring logs that are not written into files but called directly?
Will appreciate any advice. Thanks in advance,
Chi
iMac + MacBookPro, null