Propulsion
The buck stops here.
I'm so sorry... :sad:
Mandatory : All users must update to v0.11.1.x
- Thread starter eduffield
- Start date
TaoOfSatoshi
Well-known member
Tweeted, officially and unofficially...now to get to work updating!
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.
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.
crowning
Well-known member
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
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
Same here.
Always on protocol change delete peers.dat just in case
I always delete peers.dat. It's in my update script.
No you will not lose them.
maky
Member
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)
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)
M
MangledBlue
Guest
small note for everyone who is confused by rescan/reindex options :smile:
when wallet stuck you need to rebuild blockchain -> -reindex
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
...
drkhouse
Member
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.
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)