v0.10.16 - Onyx v2

JGCMiner · Nov 16, 2014

Have people successfully mixed on mainnet with version 16.6 (or above)? Just tried a fresh wallet.dat, but still am having the "last Darksend was too recent" problem.

Any advice is appreciated. Also, I am assuming that only masternodes needed to upgrade to 16.11 so I am still on 16.6...

tungfa · Nov 16, 2014

Well done team
all back on track and payments rolling in ....>

crowning · Nov 16, 2014

Masternodes still getting inactive after 60 minutes, even with v0.10.16.11.

A script automatically starts them again once they are down, but it's still annoying.

This is how my log looks like for the last 30 hours or so, the big dip in the middle was the update to v0.10.16.11 last night:

flare · Nov 16, 2014

crowning said:
Masternodes still getting inactive after 60 minutes, even with v0.10.16.11.

A script automatically starts them again once they are down, but it's still annoying.

This is how my log looks like for the last 30 hours or so, the big dip in the middle was the update to v0.10.16.11 last night:
View attachment 629

Can't reproduce this as per now - my nodes are active since 12hrs now, no drop since "remote dseep update"

UdjinM6 · Nov 16, 2014

crowning said:
Masternodes still getting inactive after 60 minutes, even with v0.10.16.11.

A script automatically starts them again once they are down, but it's still annoying.

This is how my log looks like for the last 30 hours or so, the big dip in the middle was the update to v0.10.16.11 last night:
View attachment 630

How do you check them for being inactive?

crowning · Nov 16, 2014

UdjinM6 said:
How do you check them for being inactive?

I have a darkcoind running 24/7 which checks the output of "masternode list", "masternode count", "masternode winners" and whatnot and does, besides logging all that stuff, restart the Masternodes with "masternode start "<passphrase>" for those which are down.
Works like a charm, but shouldn't be necessary at all.

And yes, the results of my logging darkcoind match with elbereth's site and the log of the Masternodes itself.

Edit: the log above displays 5 minute intervals, so when a node went down in between it might be already restarted before it gets displayed in that graph.

UdjinM6 · Nov 16, 2014

crowning said:
I have a darkcoind running 24/7 which checks the output of "masternode list", "masternode count", "masternode winners" and whatnot and does, besides logging all that stuff, restart the Masternodes with "masternode start "<passphrase>" for those which are down.
Works like a charm, but shouldn't be necessary at all.

And yes, the results of my logging darkcoind match with elbereth's site and the log of the Masternodes itself.

Well, if this darkcoind updated to 16.11 too then I have no suggestions so far...

crowning · Nov 16, 2014

UdjinM6 said:
Well, if this darkcoind updated to 16.11 too then I have no suggestions so far...

Yep, everything is running 16.11...

UdjinM6 · Nov 16, 2014

crowning said:
Yep, everything is running 16.11...

Did you use start-many to run them?
There are still some odd MNs.... not sure how it's possible with 16.11..

Code:

darkcoind masternode list lastseen | grep ": 2"

...
 "178.62.129.7:9999" : 2112031083,
    "95.85.12.33:9999" : 2054552806,
    "188.226.224.233:9999" : 2054726048,
    "178.62.149.233:9999" : 2054899532,
...

crowning · Nov 16, 2014

UdjinM6 said:
Did you use start-many to run them?
There are still some odd MNs.... not sure how it's possible with 16.11..

Code:

darkcoind masternode list lastseen | grep ": 2" ... "178.62.129.7:9999" : 2112031083, "95.85.12.33:9999" : 2054552806, "188.226.224.233:9999" : 2054726048, "178.62.149.233:9999" : 2054899532, ...

Noticed the odd lastseen-values as well, but none of them are mine.

And no, no start-many, every Masternode has its own local wallet with 1000DRK. I prefer to have NOT all eggs in one basket

UdjinM6 · Nov 16, 2014

crowning said:
Noticed the odd lastseen-values as well, but none of them are mine.

And no, no start-many, every Masternode has its own local wallet with 1000DRK. I prefer to have NOT all eggs in one basket

grep debug.log on some of your remote nodes that was going inactive

Code:

cat ~/.darkcoin/debug.log | grep "CActiveMasternode::RegisterAsMasterNode() - Masternode input =" | tail

there must be one line for every 20 minutes

flare · Nov 16, 2014

crowning said:
Noticed the odd lastseen-values as well, but none of them are mine.

And no, no start-many, every Masternode has its own local wallet with 1000DRK. I prefer to have NOT all eggs in one basket

Are your nodes really dropping off, or are you anticipating that they are on the brink of dropping and restart them upfront?

flare · Nov 16, 2014

UdjinM6 said:
grep debug.log on some of your remote nodes that was going inactive

Code:

cat ~/.darkcoin/debug.log | grep "CActiveMasternode::RegisterAsMasterNode() - Masternode input =" | tail

there must be one line for every 20 minutes

I am getting this instead - each 20mins, like clockwork. 54.171.75.34 is the nodes own IP

Code:

2014-11-16 08:13:16 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 08:33:16 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 08:53:16 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 09:13:17 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 09:33:17 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 09:53:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 10:13:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 10:33:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 10:53:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 11:13:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 11:33:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 11:53:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 12:13:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 12:33:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 12:53:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 13:13:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 13:33:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 13:53:20 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 14:13:20 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'

crowning · Nov 16, 2014

flare said:
Are your nodes really dropping off, or are you anticipating that they are on the brink of dropping and restart them upfront?

My script looks for both. When "masternode list" reports a Masternode as inactive (=0) or when it doesn't show up at all it gets restarted. No anticipation...

UdjinM6 said:
grep debug.log on some of your remote nodes that was going inactive

Code:

cat ~/.darkcoin/debug.log | grep "CActiveMasternode::RegisterAsMasterNode() - Masternode input =" | tail

there must be one line for every 20 minutes

Good idea. I'll change them to log (right now they log everything to my good friend /dev/null. There's lotta space there :smile: ) and report bag.

flare · Nov 16, 2014

crowning said:
My script looks for both. When "masternode list" reports a Masternode as inactive (=0) or when it doesn't show up at all it gets restarted. No anticipation...

Maybe your criteria "=0" is a bit to harsh to restart on immediately...

crowning · Nov 16, 2014

]

flare said:
Maybe your criteria "=0" is a bit to harsh to restart on immediately...

When I don't restart they _always_ fall off the list after a while.

But let's wait what CActiveMasternode::RegisterAsMasterNode() reports...

jiggytom · Nov 16, 2014

UdjinM6 said:
grep debug.log on some of your remote nodes that was going inactive

Code:

cat ~/.darkcoin/debug.log | grep "CActiveMasternode::RegisterAsMasterNode() - Masternode input =" | tail

there must be one line for every 20 minutes

I'm getting somethign different from flare....

Code:

2014-11-16 10:22:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 10:42:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 11:02:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 11:22:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 11:42:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 12:02:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 12:22:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 12:42:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 13:02:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 13:22:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 13:42:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 14:02:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 14:22:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)

Is that normal?

UdjinM6 · Nov 16, 2014

flare said:

I am getting this instead - each 20mins, like clockwork. 54.171.75.34 is the nodes own IP

Code:

2014-11-16 08:13:16 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 08:33:16 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 08:53:16 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 09:13:17 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 09:33:17 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 09:53:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 10:13:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 10:33:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 10:53:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 11:13:18 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 11:33:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 11:53:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 12:13:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 12:33:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 12:53:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 13:13:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 13:33:19 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 13:53:20 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'
2014-11-16 14:13:20 CActiveMasternode::RegisterAsMasterNode() - Checking inbound connection to '54.171.75.34:9999'

that's weird...
what's your output for this:

Code:

cat ~/.darkcoin/debug.log | grep "CActiveMasternode::RegisterAsMasterNode()" | tail -n 20

?
You should have a lot of "....Is capable masternode!" too which is again weird...

UdjinM6 · Nov 16, 2014

jiggytom said:

I'm getting somethign different from flare....

Code:

2014-11-16 10:22:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 10:42:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 11:02:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 11:22:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 11:42:55 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 12:02:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 12:22:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 12:42:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 13:02:56 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 13:22:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 13:42:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 14:02:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)
2014-11-16 14:22:57 CActiveMasternode::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(2874256e548dd285f58b50e01dd2ae5de31f064edab0c14b749de62f64701f1d, 1), scriptSig=)

Is that normal?

Yes, that is how it should look like
https://github.com/darkcoin/darkcoin/blob/master/src/activemasternode.cpp#L158
That's the log output right before sending dseep

jiggytom · Nov 16, 2014

UdjinM6 said:
Yes, that is how it should look like
https://github.com/darkcoin/darkcoin/blob/master/src/activemasternode.cpp#L158
That's the log output right before sending dseep

awesome, thanks.

Flare, you sure you are on v11?

v0.10.16 - Onyx v2

Active member

Well-known member

Well-known member

Well-known member

Official Dash Dev

Well-known member

Official Dash Dev

Well-known member

Official Dash Dev

Well-known member

Official Dash Dev

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Member

Official Dash Dev

Official Dash Dev

Member