zuperdoge
New member
Has anyone seen this behavior in the debug.log on the masternode? I got an alert from AWS about space issues and when I checked, the debug.log was full of these repeating lines:
Notice how it starts at block 43186 and stops at 44685, then loops back around to 43186?
I am running DarkCoin version v0.10.3.4-18-g0f787e5-beta. The darkcoind getblockcount is accurate.
This is the darkcoind getinfo results:
Any help is greatly appreciated!
Notice how it starts at block 43186 and stops at 44685, then loops back around to 43186?
I am running DarkCoin version v0.10.3.4-18-g0f787e5-beta. The darkcoind getblockcount is accurate.
This is the darkcoind getinfo results:
Code:
{
"version" : 100305,
"protocolversion" : 70012,
"walletversion" : 60000,
"balance" : 1000.00000000,
"blocks" : 51594,
"timeoffset" : 0,
"connections" : 11,
"proxy" : "",
"difficulty" : 503.84287345,
"testnet" : false,
"keypoololdest" : 1397520093,
"keypoolsize" : 99,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
Any help is greatly appreciated!