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

V12 Release

I would delete peers.dat and debug.log if the debug log is so large from the previous version, and restart.

If you get "Synchronization failed ... synchronizing masternode winners 75%.." , stop the wallet, delete peers.dat and debug.log again, and RESTART.
 
i just hope its related with the migration from .47 to .48 and not a common problem because a lot of users dont know where to look for number of masternodes and if they are connected to them correctly or not
 
i just hope its related with the migration from .47 to .48 and not a common problem because a lot of users dont know where to look for number of masternodes and if they are connected to them correctly or not
I think it's a problem with the previous version's memory leak ... and the transition is still going from v11 to v12.. last time i checked there were still about 260 masternodes on v11, which may be the cause for synchronization to masternode winners list to fail randomly ?
 
I have v.47 MN that crashed every hour but since v.48 is out it is working ( @v.47) 30 hrs already. Looks like with small number v.47 nodes problem disappears.
 
I have v.47 MN that crashed every hour but since v.48 is out it is working ( @v.47) 30 hrs already. Looks like with small number v.47 nodes problem disappears.
So you're saying your MN is on v47 and it's doing fine?
 
Since .49 came out, I'm seeing masternode count go down 1 by 1 instead of up.

anybody else seeing this?

For me I noticed that the masternode node list take more time than before to populate. After the ./dashd start of the deamon.
 
Help !

My Masternode pubkey shows :

{
"vin" : "CTxIn(COutPoint(1c6e218ceca6f3aedf55e48a6d7e2d4295a5c40955f24c0fb3fc96ac315b6c1b, 1), scriptSig=)",
"service" : "37.142.217.238:9999",
"pubKeyMasternode" : "XtEGzjn4HXeWpGZCMzafLy9mjUrNWyxmq6",
"status" : "Masternode successfully started"
}

but my pubkey as published by Dash Ninja

1000 DASH Vin (Hash-Index)1c6e218ceca6f3aedf55e48a6d7e2d4295a5c40955f24c0fb3fc96ac315b6c1b-1
Pubkey
XhvcsgJNZBvgneLxywPTkP9wWN2ZNnfL7D
IP:port37.142.217.238:9999
StatusActive (100%)
Port Check StatusOpen
Port Check Next TryRe-check pending
Daemon Version0.12.0.49 (Protocol=70103)
Balance1,000.000 DASH
Last Paid
Total Paid (Last month)15.461 DASH (5 times / 0 missed / 1 hijacked)
Active Duration4 days 20 hours 40 minutes 12 seconds
Last Seen1 minute 44 seconds
Country
il.png
Israel


how can i fix this ?


It's been looked at
You'll still get paid correctly
No fix that I know of
 
just FYI

The first few minutes after doing the v49 update. Running dash-cli masternode status on each node gives the following message:
"Not capable masternode: Hot node, waiting for remote activation."

After freaking out a bit and letting a few minutes (5? 10?) pass i now get:
"Masternode successfully started"

Whew!
 
Help !

My Masternode pubkey shows :

{
"vin" : "CTxIn(COutPoint(1c6e218ceca6f3aedf55e48a6d7e2d4295a5c40955f24c0fb3fc96ac315b6c1b, 1), scriptSig=)",
"service" : "37.142.217.238:9999",
"pubKeyMasternode" : "XtEGzjn4HXeWpGZCMzafLy9mjUrNWyxmq6",
"status" : "Masternode successfully started"
}

but my pubkey as published by Dash Ninja

1000 DASH Vin (Hash-Index)1c6e218ceca6f3aedf55e48a6d7e2d4295a5c40955f24c0fb3fc96ac315b6c1b-1
Pubkey
XhvcsgJNZBvgneLxywPTkP9wWN2ZNnfL7D
IP:port37.142.217.238:9999
StatusActive (100%)
Port Check StatusOpen
Port Check Next TryRe-check pending
Daemon Version0.12.0.49 (Protocol=70103)
Balance1,000.000 DASH
Last Paid
Total Paid (Last month)15.461 DASH (5 times / 0 missed / 1 hijacked)
Active Duration4 days 20 hours 40 minutes 12 seconds
Last Seen1 minute 44 seconds
Country
il.png
Israel


how can i fix this ?
Just ignore that, that's a pubkey that corresponds to masternodeprivkey (i.e. technical communication key and not 1000 DASH key)

just FYI

The first few minutes after doing the v49 update. Running dash-cli masternode status on each node gives the following message:
"Not capable masternode: Hot node, waiting for remote activation."

After freaking out a bit and letting a few minutes (5? 10?) pass i now get:
"Masternode successfully started"

Whew!
Yep, it was waiting for activation. However it can self-activate by finding itself in (network) mn list (which can take some time) if it was not down for too long (up to ~1 hour is ok)
 
all my MNs just crashed on 12.0.49 1 hour after updating from 12.0.48

where can i get info on how to startmany
 
Last edited by a moderator:
see you guys in about an hour - off work now - WOOHOO!!!!




GOT PI?
 
all my MNs just crashed on 12.0.49 1 hour after updating from 12.0.48

where can i get info on how to startmany
All mine are ok, since more than 3, 4 hours...

Crashed? Or delisted?
If delisted check version of your cold wallet where you launch the start.

Edit..hmmm no protocol bump so no cold start was needed ;)
 
Back
Top