You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The document states 2 options to fix the issue with the litefs consul. Issue error example is: cannot become primary, local node has no cluster ID and \"consul\" lease already initialized with cluster ID ...
The solution to the problem was working just fine before. But it doesn't work for me anymore, and both assigning the new key or removing the old one doesn't help.
The text was updated successfully, but these errors were encountered:
I found an issue with this document.
Title: Disaster Recovery from LiteFS Cloud
Location: https://fly.io/docs/litefs/disaster-recovery/
Source: https://github.com/superfly/docs/blob/main/litefs/disaster-recovery.html.markerb
Describe the issue
The document states 2 options to fix the issue with the litefs consul. Issue error example is:
cannot become primary, local node has no cluster ID and \"consul\" lease already initialized with cluster ID ...
The solution to the problem was working just fine before. But it doesn't work for me anymore, and both assigning the new key or removing the old one doesn't help.
The text was updated successfully, but these errors were encountered: