Topic: time data bitcoind crash (Read 1077 times)
Now known as issue #589
Apparently it's not fixed in v0.4 I encountered the same problem again this morning. Here's the last part of debug.log ("..." is omitted time data)
Code:
Added time data, samples 38677, offset -5 (+0 minutes)
-1002019412 -1001336709 -1001335688 -999731070 -749169022 ... -1 -1 -1 -1 -1
-1002019412 -1001336709 -1001335688 -999731070 -749169022 ... -1 -1 -1 -1 -1
Since upgrading to v0.4.0 about 10 days ago, the problem hasn't happened again
I'm running "Bitcoin version 0.3.24-beta" on a couple Linux servers. About once a week, the daemon crashes and I have to restart it. In every instance, the last entry in debug.log is something like the following:
The daemon seems to crash while it's printing the entire list of time samples. In the above quote, the median offset was "+0" but "-1940" was the last sample it printed.
I haven't noticed any other patterns. What else can I do to help narrow down the problem?
Quote
Added time data, samples 28503, offset +0 (+0 minutes)
-747598944 -747551416 -747428248 ... -201976 -1940
-747598944 -747551416 -747428248 ... -201976 -1940
The daemon seems to crash while it's printing the entire list of time samples. In the above quote, the median offset was "+0" but "-1940" was the last sample it printed.
I haven't noticed any other patterns. What else can I do to help narrow down the problem?
Jump to: