WARN

• Ligthouse WARN

WARN [08-20|02:05:36.588] Synchronisation failed, retrying         err="peer is unknown or unhealthy"
WARN [08-20|04:07:33.209] Synchronisation failed, dropping peer    peer=8b5458866fbe946547feXXXXx8c60c64b4950f err=timeout

WARN Local chain is post-merge, waiting for beacon client sync switch-over...

WARN Ignoring already known beacon payload

docker-compose up

WARN[0000] Found orphan containers ([node-exporter]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

WARN Low peer count

WARN[0002] - The remote state S3 bucket your-bucket-name needs to be updated

Related

• INFO
• Elasticsearch troubleshooting: WARN
• Geth logs WARN
• Ligthouse WARN
• Avalanchego logs

See also

• ERR, ERROR
• Lighthouse: logs, WARN, INFO, CRIT, ERRO
• lighthouse: [ account | beacon_node | boot node | account manager | database manager | validator client ], --help, --version, Releases, Ligthouse WARN, Paul Hauner, Lighthouse checkpoint sync, Lighthouse logs, Changelog
• Elasticsearch troubleshooting, Elasticsearch logs, yellow, Low disk watermark, in-memory shard lock, re-running