rmfakecloud Problems with initial sync

I just got rmfakecloud installed using docker with a reverse nginx proxy. I was able to connect just fine, create a user and enable the sync15 feature.

When doing the initial sync, however, my device keeps failing. On the server side I see:

$ docker-compose logs --follow rmfakecloud | grep -v info
Attaching to rmfakecloud
rmfakecloud     | time="2022-04-13T11:44:02Z" level=warning msg="wrong gen, has 1649840718847689 but is 0"
rmfakecloud     | time="2022-04-13T11:46:30Z" level=warning msg="wrong gen, has 1649840718847689 but is 0"
rmfakecloud     | time="2022-04-13T11:49:18Z" level=warning msg="wrong gen, has 1649840718847689 but is 0"

and on the client side I see:

reMarkable: ~/ journalctl -u sync.service --follow
Apr 13 11:44:14 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of c40eb32c-f6e2-4b31-942e-cda1cf0fcb94.pdf took 1321.551697ms
Apr 13 11:44:15 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of c40eb32c-f6e2-4b31-942e-cda1cf0fcb94.epub took 704.233338ms
Apr 13 11:44:19 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of e6b98593-d135-419b-9121-0f2bc2b353f4.pdf took 3058.871286ms
Apr 13 11:44:21 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of e6b98593-d135-419b-9121-0f2bc2b353f4.epub took 1685.903579ms
Apr 13 11:46:30 reMarkable sync[199]: rm.synchronizer: Root Hash Upload failed, requesting resync
Apr 13 11:46:30 reMarkable sync[199]: rm.synchronizer: Oh no!!!, Sync failed.. reason='Server has more recent updates, re-syncing.', detail='Error transferring https://XXXXXXX/blobstorage?blobid=root&exp=1649850690&scope=write&signature=8f0XXXXX90&uid=XXXX - server replied: '
Apr 13 11:46:30 reMarkable sync[199]: rm.synchronizer:  - no server, uploading local
Apr 13 11:46:38 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of b20839d2-9c99-464e-8d32-3782a0de228f.pdf took 3079.127019ms
Apr 13 11:46:40 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of b20839d2-9c99-464e-8d32-3782a0de228f.epub took 1687.622364ms
Apr 13 11:46:41 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of c40eb32c-f6e2-4b31-942e-cda1cf0fcb94.pdf took 1326.726462ms
Apr 13 11:46:42 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of c40eb32c-f6e2-4b31-942e-cda1cf0fcb94.epub took 705.302333ms
Apr 13 11:46:46 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of e6b98593-d135-419b-9121-0f2bc2b353f4.pdf took 3059.645047ms
Apr 13 11:46:47 reMarkable sync[199]: rm.synchronizer.tree:  - time consuming hash of e6b98593-d135-419b-9121-0f2bc2b353f4.epub took 1673.502568ms
Apr 13 11:49:18 reMarkable sync[199]: rm.synchronizer: Root Hash Upload failed, requesting resync
Apr 13 11:49:18 reMarkable sync[199]: rm.synchronizer: Oh no!!!, Sync failed.. reason='Server has more recent updates, re-syncing.', detail='Error transferring https://XXXXXX/blobstorage?blobid=root&exp=1649850858&scope=write&signature=12f5f3XXXXXfdc2a&uid=XXXXX - server replied: '

So the connection between host and device seems to be working just fine but something is wrong with checking file integrity?

I am running software 2.12.3.606-patch_32.2.02-0-geeb0667 on the device and rmfakecloud-proxy - 0.0.3-2 from opkg.

Any thoughts?

Apr 13 '22 11:04 mynameisfiber

It seems this is happening because of one file in particular. This file is a notebook with about 20 pages in it. I remember a bit ago I was having sync issues with this file with the remarkable cloud, but making a copy of it and deleting the original fixed the issue. This fix isn't resolving the issue for rmfakecloud.

Apr 13 '22 12:04 mynameisfiber

Digging a bit deeper it seems that the generation being received is from the client. I don't know what this means but it seems important

$ docker-compose logs --tail 50 --follow rmfakecloud | grep "gen"
rmfakecloud     | time="2022-04-13T12:49:10Z" level=info msg="Client sent generation:1649840718847689"
rmfakecloud     | time="2022-04-13T12:49:10Z" level=warning msg="wrong gen, has 1649840718847689 but is 0"
rmfakecloud     | time="2022-04-13T12:49:12Z" level=info msg="Client sent generation:1649840718847689"
rmfakecloud     | time="2022-04-13T12:49:12Z" level=warning msg="wrong gen, has 1649840718847689 but is 0"

Apr 13 '22 12:04 mynameisfiber

This problem goes away if I disable sync15

Apr 13 '22 15:04 mynameisfiber

can you do journalctl -x -u sync and check if there are any crash messages. it may be connected to the https://github.com/ddvk/rmfakecloud/issues/145

the error means that the server has no files, the tablet is sending a wrong generation, and it should an initial sync.

sync15 is a better, uses less bandwidth, but is not fully tested

Apr 13 '22 21:04 ddvk

@ddvk no crashes, just really the messages from my first post repeated over and over!

Apr 13 '22 21:04 mynameisfiber

you can try deleting .local/share/remarkable/xochitl/.tree and restarting sync

Apr 13 '22 21:04 ddvk