-
Notifications
You must be signed in to change notification settings - Fork 81
Description
I'm validating on Prater with geth+nimbus, and ran into a missed attestation that I wanted to investigate to rule out any hardware issues with my setup. Finding the logs for my specific epoch+slot was surprisingly difficult, and required bouncing around between rocketpool, docker, and nimbus quite a lot.
Luckily, I got some invaluable help on Discord.
Running this command from jcrtp saved the day
docker-compose --project-directory ~/.rocketpool -f ~/.rocketpool/docker-compose.yml logs eth2 > eth2.log
But my understanding is that this isn't sourcing the logs from the filesystem, but instead from stdin which is a bit more fragile.
I looked at the nimbus documentation, and saw that they suggest leveraging log rotations for more persistent + performant archiving of logs
https://nimbus.guide/log-rotate.html
In their docker documentation, they also mention that the --log-file flag is ignored for their docker image, which is what rocketpool is using. I suspect this logging scenario might be broken.
https://nimbus.guide/docker.html
Summary: Would be awesome if rocketpool launched the nimbus container with log rotation configured correctly. That way client logs would last longer. Also, it would be nice to have documentation that explains how to investigate client logs within docker containers.