yeah, it looks like npd did the trick.
thanks.
Topic: pushpool: time-too-old (Read 1522 times)
Bitcoin requires a reasonably correct time on any system that's creating blocks. If you set the clock manually, it will probably be wrong.
how's npd going to help in anyway ?
whats the difference between setting the clock manually than using npd ?
i had the same pushpoold+bitcoind on another server and everything went just fine...
moved to a new server and now i'm gettint a lot of time-too-old messages..
whats the difference between setting the clock manually than using npd ?
i had the same pushpoold+bitcoind on another server and everything went just fine...
moved to a new server and now i'm gettint a lot of time-too-old messages..
It most likely means the pool's clock is wrong. Setup ntpd.
hey,
I'm running a pushpoold, and sometimes pushpoold uses 100% cpu and I get a lot of "time-too-old" messages from the miners.
What could be causing that ? And what this message means exactly ?
I had ~2500 workers / 2,5GHash/sec, hardware is Core i7 920 @ 12gb ram - 100mbit uplink.
Thanks.
I'm running a pushpoold, and sometimes pushpoold uses 100% cpu and I get a lot of "time-too-old" messages from the miners.
What could be causing that ? And what this message means exactly ?
I had ~2500 workers / 2,5GHash/sec, hardware is Core i7 920 @ 12gb ram - 100mbit uplink.
Thanks.
Jump to: