Michael Sproul

If you're getting an address-already-in-use error then you've probably already got Lighthouse running in another tab somewhere. You can look for the process ID using `ps` like this: ``` ps...

@Sajjon You'll need to run v3.0.0 for the merge, do you get anything different when you change Lighthouse's port with e.g. `--port 9001`?

If you could also send me the debug logs from `~.lighthouse/mainnet/beacon/logs/beacon.log` that would be helpful. I'm `@sproul#3907` on the Lighthouse Discord, or my email is `@sigmaprime.io`.

Closing in favour of https://github.com/sigp/lighthouse/issues/2254 which has more detailed discussion about possible root causes.

I've fixed the notifier in this PR: https://github.com/sigp/lighthouse/pull/3519 I'm less sure of how to fix the slasher because it doesn't run every slot but instead runs on an arbitrary `update_period`....

Re-opening for the slasher

Closing as resolved

Syncing a new node with this code to see a) how big the database ends up and b) what the I/O pattern is like once backfill completes.

This is looking good from a disk usage point of view, using only 48.1 GB after a few days (less than half what we currently use). However the impact on...

Closing as this is now merged into https://github.com/sigp/lighthouse/pull/3206.