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.

Sign up for GitHub

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

Jump to bottom

Not producing block because head block time is in the future (is the system clock set correctly?). #244

Closed
bytemaster opened this issue Aug 18, 2015 · 2 comments
Closed

Not producing block because head block time is in the future (is the system clock set correctly?). #244

bytemaster opened this issue Aug 18, 2015 · 2 comments
Labels
bug High Priority
Milestone
DevShares 2.0

Comments

@bytemaster
Copy link
Contributor 

2700993ms th_a       witness.cpp:242               block_production_loo ] Witness 1.6.3 production slot has arrived; generating a block now...
2701040ms th_a       witness.cpp:255               block_production_loo ] Generated block #8234 with timestamp 2015-08-18T14:45:01 at time 2015-08-18T14:45:01
2701993ms th_a       witness.cpp:239               block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-18T14:45:02
2701993ms th_a       witness.cpp:207               operator()           ] Not producing block because head block time is in the future (is the system clock set correctly?).
2702994ms th_a       witness.cpp:239               block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-18T14:45:03
2702994ms th_a       witness.cpp:207               operator()           ] Not producing block because head block time is in the future (is the system clock set correctly?).
2703997ms th_a       witness.cpp:239               block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-18T14:45:04
2703997ms th_a       witness.cpp:207               operator()           ] Not producing block because head block time is in the future (is the system clock set correctly?).
2704993ms th_a       witness.cpp:239               block_production_loo ] slot: 1 scheduled_witness: 1.6.4 scheduled_time: 2015-08-18T14:45:05 now: 2015-08-18T14:45:05
2704993ms th_a       witness.cpp:242               block_production_loo ] Witness 1.6.4 production slot has arrived; generating a block now...

It appears that the "scheduled_time" is null 1970-01-01T00:00:00 which is causing it to skip the scheduled_witness 1.6.0 3 times at 3 different time slots.
@bytemaster bytemaster added this to the DevShares 2.0 milestone Aug 18, 2015
@bytemaster
Copy link
Contributor Author

It happens on a regular basis:

3000998ms th_a       witness.cpp:207               operator()           ] Not producing block because head block time is in the future (is the system clock set correctly?).
3001995ms th_a       witness.cpp:239               block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-18T14:50:02
3001995ms th_a       witness.cpp:207               operator()           ] Not producing block because head block time is in the future (is the system clock set correctly?).
3002998ms th_a       witness.cpp:239               block_production_loo ] slot: 0 scheduled_witness: 1.6.0 scheduled_time: 1970-01-01T00:00:00 now: 2015-08-18T14:50:03
3002998ms th_a       witness.cpp:207               operator()           ] Not producing block because head block time is in the future (is the system clock set correctly?).
3003998ms th_a       witness.cpp:239               block_production_loo ] slot: 1 scheduled_witness: 1.6.10 scheduled_time: 2015-08-18T14:50:04 now: 2015-08-18T14:50:04
3004994ms th_a       witness.cpp:239               block_production_loo ] slot: 2 scheduled_witness: 1.6.3 scheduled_time: 2015-08-18T14:50:05 now: 2015-08-18T14:50:05

This is from the same run. Looks like it is 5 minutes apart which is the maintenance interval.

@bytemaster
Copy link
Contributor Author

It is skipping 3 blocks, which is how many blocks should be skipped on a maintenance interval. So I suspect that this is just a bad error message.

bytemaster referenced this issue Aug 18, 2015
@bytemaster
Fix #224 - Improve log messages
80f007f 
- it is not an error to have the next slot be in the future, it happens
every maitenance interval when the skip slots is greater than 0.

- re-order the failure conditions to report configuration issues first,
   then other issues second.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug High Priority
Projects
None yet
Milestone
DevShares 2.0
Development

No branches or pull requests
1 participant
@bytemaster