Comments (8)
Hmm so what I notice is that the local log was seemingly wiped after the go-sbot -fsck sequences -repair
command was executed.
If I call sbotcli hist
now I only see one message: the post I made after starting go-sbot
post-repair. That would explain why that message didn't make it across to Patchwork (sequence mismatch).
Let me take another run at this with a fresh start and see if I encounter the error again. I'll try to find duplicate messages if I hit a snag again.
One other detail to mention is that I was running legacy replication when this happened.
Maybe I could try writing a script which looks for duplicates in the log and that would make rooting out the core of this issue easier?
This could be handy. I guess you could create a list of each message key you find and shout if there's a duplicate.
As for connecting this with #40, I'm a bit lost. That seems like the dragons part. Any further info would be great.
Agreed. Could be a good issue to ask cryptix about on a call (if we can).
from go-ssb.
Maybe I could try writing a script which looks for duplicates in the log and that would make rooting out the core of this issue easier?
This could be handy. I guess you could create a list of each message key you find and shout if there's a duplicate.
Approach for checking for duplicates has emerged in #201 (comment) thanks to @mplorentz, scanning for duplicated signatures seems like a simple way to do it.
from go-ssb.
This is related to #40
from go-ssb.
@cryptix I just ran into this error too, and confirm your workaround fixed the issue, thanks!
from go-ssb.
have been running into this error again and again, not sure if i'm doing something wrong but seems to happen occasionally if i stop and restart the service running go-sbot
.
from go-ssb.
Just ran into this with a build from latest code on master
; running on Pi3 B+. Issue occurred after killing the go-sbot
process and then running it again.
The offending feed was that of the go-sbot
itself (ie. the local feed).
go-sbot: fsck returned: ssb/consistency error: message sequence missmatch for feed @Fq0a4uYHoEpYOV29LjQVK8Lt3fDK0epfjMxCa9/8NK4=.ed25519 Stored:6 Logical:4
After running go-sbot -fsck sequences -repair
I was then able to execute go-sbot
without any errors. However, I am no longer seeing replication with my local Patchwork instance.
CC: @decentral1se
from go-ssb.
@mycognosist thanks for the report! Would be great to fix this one.
Are you seeing anything in the go-sbot
logs re: failure to replicate? Patchwork should be sending incoming replication requests.
Do you see any duplicated messages in the output of sbotcli log
? Maybe I could try writing a script which looks for duplicates in the log and that would make rooting out the core of this issue easier? Unsure how hard it is to compare and probably slow, but might be handy. It'd be nice to at least confirm the assumption in #81 (comment) e.g. local duplication.
As for connecting this with #40, I'm a bit lost. That seems like the dragons part. Any further info would be great. Maybe we can still break this up into small parts for debugging / troubleshooting? Try to figure out how to reproduce seems difficult. Even if we could do it manually, it'd be great. Perhaps some small win in the graceful shutdown code can be had...
For the time being, the work-around is probably the one mentioned in https://github.com/ssbc/go-ssb#startup-error--illegal-json-value but that is obviously not ideal. But just in case you need to keep moving for whatever reasons.
from go-ssb.
Potentially also related: #201
from go-ssb.
Related Issues (20)
- TestFSCK flaking HOT 2
- TestNullFetched is flaky
- TestMetafeedIndexes is flaky HOT 4
- TestPrivateGroupsManualDecrypt is flaky HOT 2
- Remove usage of PushSource?
- Fix REUSE badge HOT 3
- Where are the indexes actually being set? HOT 5
- What's the difference between the publish log and the receive log? HOT 3
- Figure out licensing problems
- Figure out why TestStartup seemingly always triggers a 30 second timeout
- Can we get rid of logBuilder?
- Probable race condition in Gossip plugin's FeedManager
- Require tests passing before merge once flaky tests go away HOT 1
- Race condition between index Margaret queries
- Incorrect parsing of high-precision timestamps HOT 17
- TestPrivMsgsFromGo failing HOT 2
- Capitalization in sbotcli's remoteKey flag HOT 2
- Ways forward for go-ssb? HOT 5
- Illegal slice reuse in Badger code HOT 2
- Possible problem with publishing before finishing syncing one's own feed from another node
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-ssb.