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

orbitdb is not replicated after a while #189

Open
gitaaron opened this issue May 20, 2022 · 2 comments
Open

orbitdb is not replicated after a while #189

gitaaron opened this issue May 20, 2022 · 2 comments
Assignees
Milestone

Comments

@gitaaron
Copy link
Contributor

This may be hard to reproduce but creating this issue now -

Steps to reproduce

  1. Setup Box/IPFS/IPFS-Cluster on two separate machines (in my case it was two rPis)
  2. Connect fsync to Box0
  3. Connect fuludocs to Box1 and see change events propagated to it
  4. After a while the events stop getting propagated to Box1 (even if I reload the browser)
  5. The only fix was to restart the nodejs 'Box' app on Box0.
@gitaaron gitaaron added this to the fula 0.7.0 milestone May 20, 2022
@farhoud farhoud assigned farhoud and mehdibalouchi and unassigned farhoud May 23, 2022
@mehdibalouchi
Copy link
Contributor

I created two instances of Box on two ubuntu VMs using ansible playbooks (ipfs + ipfs-cluster + box). After doing the steps above, everything works and I can see the changes I make in the file reflected in the browser.
However, after a while it seems that fula-client gets disconnected. The cloud icon changes to a loading animation and it can't reconnect to the box again. Even when I refresh the browser it can't connect. I restarted Box service (the one fuludocs was trying to connect to) and the browser gets connected again.
@gitaaron is it possible that the issue is about fula-client getting disconnected and unable to connect again? Are you sure that fula-client was connected when you saw that changes aren't getting reflected in the browser?

@gitaaron
Copy link
Contributor Author

gitaaron commented May 28, 2022 via email

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

No branches or pull requests

3 participants