Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 Synchronisation does not sync any files between Windows and Android #520

Open
Toastgeraet opened this issue Oct 23, 2024 · 1 comment

Comments

@Toastgeraet
Copy link

Abstract

Trying to sami-manually setup synchronisation between Windows and Android Platform using an AWS S3 Bucket via Tigris/Fly.io.

  1. Manually setup tigris on PC.
  2. Test connection -> works!
  3. Copy Setup URL
  4. Switch to mobile app
  5. Have to create a vault first, before we can access settings
  6. Setup LiveSync using Setup URL from 3.
  7. Check Settings and Test Connection on mobile -> works

Expected behaviour

  • Synchronisation ends with the message Replication completed
  • Everything synchronised

Actually happened

  • Log seems fine
  • No files synchronised in either direction

Example excerpt from log from PC after creating files. Looks like they are being uploaded.

23.10.2024, 21:21:51->Chunks saved (with fixed): doc: hello world.md ,chunks: 1 (new:1, recycled:0, cached:0) 23.10.2024, 21:21:51->STORAGE -> DB (plain) hello world.md 23.10.2024, 21:22:03->Chunks saved (with fixed): doc: .obsidian/workspace.json ,chunks: 1 (new:1, recycled:0, cached:0) 23.10.2024, 21:22:03->STORAGE --> DB:.obsidian/workspace.json: (hidden) Done 23.10.2024, 21:22:05->Replication closed

but Tigris dashboard doesn't show any change in database size or any of the supposedly uploaded files.

Summarization

Within the app and the plugin and log everything looks perfectly fine and seems to work. But apparently, no files are actually being uploaded?!

@vrtmrz
Copy link
Owner

vrtmrz commented Nov 5, 2024

Sorry for being late!
Would you mind share me the report which can be created on the 🧰Hatch pane?
And, sorry for confusingly, Replication closed is a message that appears whenever the replicator is successfully closed (and disabled), and does not mean that replication is taking place.
Actual bucket sync log should be like following This log is the one that has started on pressing replication icon):

2024/11/5 20:01:02->Receiving Journal: Getting list of remote journal
2024/11/5 20:01:02->Processing journal: Queue run out, but process is running. wait for the next.
2024/11/5 20:01:02->Receiving Journal: No journals needs to be downloaded
2024/11/5 20:01:02->Processing journal: No files needs to be processed!
2024/11/5 20:01:02->Uploading journal: Queue run out, but process is running. wait for the next.
2024/11/5 20:01:02->Packing Journal: Start sending
2024/11/5 20:01:02->Journal reading from seq:3779
2024/11/5 20:01:02->Packing Journal: No journals to be packed!
2024/11/5 20:01:02->No files needs to be uploaded!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants