From 37c3c3877cb3d2b6ab8d8ddb44f87fba11b143e0 Mon Sep 17 00:00:00 2001 From: Sacha Saint-Leger Date: Wed, 13 Jan 2021 11:41:47 +0100 Subject: [PATCH] add troubleshooting section on time (#2232) --- docs/the_nimbus_book/src/troubleshooting.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/docs/the_nimbus_book/src/troubleshooting.md b/docs/the_nimbus_book/src/troubleshooting.md index 9c589ba8b..ff6e6f590 100644 --- a/docs/the_nimbus_book/src/troubleshooting.md +++ b/docs/the_nimbus_book/src/troubleshooting.md @@ -1,6 +1,6 @@ # Troubleshooting -> ⚠️ This page concerns the Pyrmont testnet. If you're running mainnet, replace `pyrmont` with `mainnet` in the commands below. +> ⚠️ The commands on this page refer to the Pyrmont testnet. If you're running mainnet, replace `pyrmont` with `mainnet` in the commands below. As it stands, we are continuously making improvements to both stability and memory usage. So please make sure you keep your client up to date! This means restarting your node and updating your software regularly from the `master` branch. If you can't find a solution to your problem here, feel free to hit us up on our [discord](https://discord.com/invite/XRxWahP)! @@ -73,6 +73,22 @@ To change the base port, run: If you're being flooded with `Catching up on validator duties` messages, then your CPU is probably too slow to run Nimbus. Please check that your setup matches our [system requirements](./hardware.md). +### Local timer is broken error + +If you cannot start your validator because you are seeing logs that look like the following: + +``` +WRN 2021-01-08 06:32:46.975+00:00 Local timer is broken or peer's status information is invalid topics="beacnde" tid=120491 file=sync_manager.nim:752 wall_clock_slot=271961 remote_head_slot=271962 local_head_slot=269254 peer=16U*mELUgu index=0 tolerance_value=0 peer_speed=2795.0 peer_score=200 +``` + +This is likely due to the fact that your local clock is off. To compare your local time with a internet time, run: + +``` +cat