• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Mandatory : All users must update to v0.11.1.x

Strange, that's what I use. And I fear when I build the datase again Abe gets stuck at the same block.

So for me it's now a complete blockchain rebuild followed by a complete Abe rebuild. Aaargl...

Anyway, thanks.
I'm so sorry... :sad:
 
Just got version 11006 to sync with -reindex, but then it crashed a minute or so after it synced, (windows 32-bit).

Will try v.11007.
 
I just picked this up today after opening my version 10 wallet. Some drk was sent last night and I revived it. Do I need to reindex when I install v11?
 
All of my nodes dropped offline about 15 minutes after updating to 11.0.7.

getinfo reveals they are on the correct block and I don't see any errors. But none of my nodes show up in masternode list.
 
All of my nodes dropped offline about 15 minutes after updating to 11.0.7.

getinfo reveals they are on the correct block and I don't see any errors. But none of my nodes show up in masternode list.

I had this when I went from v0.10.17.26 to v0.11.0.6.

Stopping the Masternode(s), removing peers.dat and starting the Mastenodes with -reindex fixed it, not a single drop since then.
 
I had this when I went from v0.10.17.26 to v0.11.0.6.

Stopping the Masternode(s), removing peers.dat and starting the Mastenodes with -reindex fixed it, not a single drop since then.
Same here.
Always on protocol change delete peers.dat just in case ;) in the past I have never had any issues or deamons down. 99,9% of the time ;)
 
I had this when I went from v0.10.17.26 to v0.11.0.6.

Stopping the Masternode(s), removing peers.dat and starting the Mastenodes with -reindex fixed it, not a single drop since then.

After reindex, did you have to start from QT again?

I'm reindexing now, but it's going to take a little bit. On 155878 right now. Thankfully I have a bunch of nodes to update so I'm not twiddling my thumbs :)
 
Darkcoin server stopping
xxx@install:~$ ./darkcoind -rescan
Darkcoin server starting
xxx@install:~$ ./darkcoind getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1415488991,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."

Rescan does not work, stuck on 204572 block after 11.0.6 -> 11.0.7 change. (peers.dat deleted)
 
Darkcoin server stopping
xxx@install:~$ ./darkcoind -rescan
Darkcoin server starting
xxx@install:~$ ./darkcoind getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1415488991,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."

Rescan does not work, stuck on 204572 block after 11.0.6 -> 11.0.7 change. (peers.dat deleted)


use -reindex

./darkcoind -reindex
 
small note for everyone who is confused by rescan/reindex options :smile:
Code:
> darkcoind --help
...
  -reindex               Rebuild block chain index from current blk000??.dat files on startup
...
  -rescan                Rescan the block chain for missing wallet transactions on startup

...
when wallet stuck you need to rebuild blockchain -> -reindex
 
Do it thousand times with bitcoin, hundread with darkcoin and do mistake. Maybe is because of too much whiskey. ;)
Now everything is OK with all my masternodes. Only this one I does it harder way. But it works too. ;)
 
small note for everyone who is confused by rescan/reindex options :smile:
Code:
> darkcoind --help
...
  -reindex               Rebuild block chain index from current blk000??.dat files on startup
...
  -rescan                Rescan the block chain for missing wallet transactions on startup

...
when wallet stuck you need to rebuild blockchain -> -reindex
could that be programmed in?
 
Is there or could there be some kind of walletnotify event that tells you your daemon has given up being a MN? Even without a given reason, it would be handy to script yourself an email. I know you can monitor it in other ways, but it would be nice to hear direct from the daemon.
 
could that be programmed in?
Not sure if it's a good idea to auto-reindex but until then I guess you can use a bash script and this
Code:
-alertnotify=<cmd>     Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
 
Anyone?

I can't get v11 to work with p2pool - so I can't upgrade......Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999:

2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty)
2015-01-16 16:38:13.821724
2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to 'REMOVED' with username 'IYFTechDRK'...
2015-01-16 16:38:13.850612 ...success!
2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47
2015-01-16 16:38:13.850753 Current block height: 204176
2015-01-16 16:38:13.850777
2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'...
2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...

If I revert to v10 I have no problem..........it just won't connect on 9999

I'd really like to get my node back online.........
 
Back
Top