Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Block rejected by chain - Invalid Timestamp in future #168

Open
erik777 opened this issue Mar 26, 2024 · 0 comments
Open

Block rejected by chain - Invalid Timestamp in future #168

erik777 opened this issue Mar 26, 2024 · 0 comments

Comments

@erik777
Copy link

erik777 commented Mar 26, 2024

Can someone please provide clarity? Is this saying that the block the person mining via the node is invalid, or that it just happened to reject a block introduced on the network?

This error is output by a node with 1 connected miner. chronyc tracking output

$ chronyc tracking
Reference ID    : AE35A945 (c-174-53-169-69.hsd1.mn.comcast.net)
Stratum         : 3
Ref time (UTC)  : Mon Mar 25 19:40:47 2024
System time     : 0.000000000 seconds fast of NTP time
Last offset     : +0.000204285 seconds
RMS offset      : 0.000483814 seconds
Frequency       : 22.774 ppm fast
Residual freq   : +0.002 ppm
Skew            : 0.077 ppm
Root delay      : 0.068933137 seconds
Root dispersion : 0.005265711 seconds
Update interval : 1041.7 seconds
Leap status     : Normal

Running sudo chronyc -a makestep didn't change the numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant