~sarlev-sarsen

FWIW, I have `eth-watcher` pointed at my own infura enbpoint and have not appeared to suffer from this issue.

I was stuck at `+azimuth-block` ~14.651.300 for about the last 5 weeks. Waited to see if the most recent ota would rectify this, but to no avail. So I tried...

I am now getting a growing stack of dropped packets: ``` ames: packet dropped (1000 total) ames: packet dropped (2000 total) ames: packet dropped (3000 total) ``` Update: bailed again...

Just pulled my ship off my droplet and onto a local machine, `meld`ed, and tried `:azimuth|kick` which got me: ``` >> %no-logs-in-azimuth-state [%jael-listen {} [%.n p=%azimuth]] ship: processing azimuth snapshot...

@joemfb it was suggested by @yosoyubik that you might be able to help with the memory stuff here? He was going to try building a custom snapshot as well but...

I don't think so. I just rebooted and ran a `ctrl-c` interrupt and got this: https://pastebin.com/5kMwM079 Not sure if that is because of when / how quickly after getting the...

I have uninstalled astrolabe; what should I do next to kickstart the next stage? I'm over a million blocks behind--will I be able to make it through all of those...

Pre-meld: https://pastebin.com/PbWvEAgB output during meld: ``` ~sarlev-sarsen:dojo> hash-cons arena: root: B/160 atoms (3554444): refs: MB/114.057.740 data: MB/336.290.884 dict: MB/281.966.240 total: MB/732.314.864 cells (26842676): refs: MB/781.763.380 dict: GB/1.932.625.360 total: GB/2.714.388.740 total:...

FTR, this worked smoothly ~ 10 hours later. All original attempts happened within ~60 mins of each other.

Thanks for looking into this. Looks like the right solution to me but will defer to @pkova to review/merge/deploy.