Closed slipperybeluga closed 1 year ago
This is unrelated to the format of .env
. All relays have been struggling the past two days. You can add more relays and see whether that helps. A list is at https://ethstaker.cc/mev-relay-list/
When you ./ethd logs -f mev-boost
you should see it connect to relays, and give you a list of configured relays on startup
Hello,
I am running a teku/erigon eth-docker node with MEV boost enabled ( eth-docker v2.2.6.3). I didn't see any changelogs regarding security updates or mev boost so I have not updated yet. I have over 99% uptime however I find that my node is having a hard time staying connected to the mev boost relays. I have several selected in the .env file and find that after several hours or a day of running the node, teku gives the following error in the logs:
If I restart the container, I usually get a success message for the relays in the log:
This is particularly frustrating as an independent node operator. I have only a couple blocks to my name and they each have gotten < 10% of the rewards of neighboring blocks because of this failure. Any ideas? Is this a potential issue with my .env file? My relays listed in the .env file are comma separated but I noticed that the COMPOSE_FILE line is colon separated.
eg: