Teku
Last updated
Last updated
By default, Teku uses a recently finalized checkpoint state from a community source, and only need to catch up to the current head of the blockchain. This process is relatively fast, usually taking only a few minutes to no more than an hour.
Teku's DApp and the Logs provide useful information about it's activities. To observe the syncing progress:
Check the status in the Teku DApp. The status will change from syncing to in sync when it is fully synced.
Inspect the Logs. Familiarizing yourself with the Logs enables you to confidently assess whether the process is running smoothly or if any issues require attention. To access the Logs, open the Teku Management Page from the My Dapps menu and scroll to the bottom.
Once Teku has started up and initialized, you should start to see the following lines in the Logs:
This indicates that Teku is in "Syncing" mode. You will notice the Target slot counting up, and the Remaining slots counting down, until eventually Teku reports "Syncing completed":
The "Slot Event" messages indicate that Teku is fully synced and enters normal operation.
If you notice that the status in the DApp remains stuck at "Waiting for beacon chain to become ready" without any progress, or if you come across error messages in the Logs, Teku might have a problem syncing.
The most common problems are:
Teku fails to connect to sufficient number of peers. If you are getting a low peer count, there may be a problem with your network setting. See Opening Network Ports to learn how to resolve this by "opening port 9000" on the router (port 9006 for Gnosis Teku).
Teku fails to find the Execution Client. It may be the case that you have not yet installed the Execution Client, in which case once you have set up the Execution Client this error will go away.
If you have already installed an Execution Client but this error persists, check that you have correctly selected the Execution Engine (Geth or Nethermind) on Teku's Settings page, to match with your installed Execution Client. Remember to click Apply changes to update the setting.
If the error persists, check the Logs of the Execution Client to see what is going on there. Sometimes a Restart of the Execution Client and the Consensus Client is all that is needed to resolve the issue. Please also feel free to reach out to our Discord channel for support.
Here is an example of how the Teku Logs should look like when:
Teku is fully synced;
The Execution Client is fully synced;
You have loaded Validator Keys into Teku, and the Validators have become active on the Beacon Chain; and
You have installed and configured MEV-Boost.
Key observations:
White, blue, and green lines indicate positive activity.
Red texts require attention and may indicate issues.
Teku diligently tracks each slot ("Slot Event") and each epoch ("Epoch Event").
Blue lines represent your validator producing attestations ("Published attestation").
Every epoch, Teku reports the "Attestation performance" of previous epochs.
Empty blocks ("... empty"), "Late Block Import", or "Reorg Event" occasionally appear, which are normal and related to Ethereum network activities. However, if you see excessive empty or late blocks, it may indicate a syncing issue with your node.
If MEV-Boost is installed and working as expected, Teku registers your validators on the "builder network" every epoch, indicated by a line similar to: "Validator *** 6 out of 6 validator registration(s) were successfully sent to the builder network via the Beacon Node".
If you notice that your validators are missing attestations, it is often beneficial to inspect the Logs for any abnormal behavior or issues.
