Skip to main content

Johan Bové

maximum call stack exceeded, then sbot is missing · Issue #957 · ssbc/patchwork · GitHub

The steps described by Christian Bundy help me restore the corrupted stream data in my Scuttlebutt "server" data today.

Are you able to use any version of ssb-server or Patchwork? This looks to me like your flumedb views are corrupted (see flumedb/flumedb#32), but I've only ever personally seen this when running my flumedb deletion scripts. You can regenerate all of your views by deleting everything in ~/.ssb/flume/ except for log.offset, but I might make a backup so that we can try to debug them. Sorry, that's a total pain for Scuttlebutt to just randomly explode without warning, hopefully just moving/removing your view files will help? I'm sure you already know, but I'd recommend that you make a backup of ~/.ssb/secret and ~/.ssb/gossip.json before running rm anywhere near your SSB folder. It wouldn't hurt to make a backup of ~/.ssb/flume/log.offset either, but it's not quite as important as the first two.