Masternode started successfully but activeseconds is 0

Hello

I moved my masternodes to new servers (new ip addresses) after initializing the new masternodes all looks good. In qt wallet the masternodes are enabled, on the vps masternode status gives “successfully started” but if I check “activeseconds” with “masternodelist activeseconds”, the value is 0.

I don’t recived any rewards since 6 days…what is the problem?

Hi CryptoTank,

My guess is, your masternodes are still in the grace period they have to pass through after each initialization.

They should receive their first rewards roughly 132 hours (at the time of this writing) after initialization. Once that has happened, they should also get non-zero activeseconds values.

Could you check back in and mark this answer as the solution if your masternodes come to live and report back if you don’t see any change after 140 hours?

Best regards,
Alex

Hi

Ok I will do that.

I read in your discord channel that the grace period can be calculated with activeseconds:

VALIDATION PERIOD FOR NODE REWARDS

Nodes can’t receive blockrewards before they are online for (No of masternodes * 4) / 60 in hours . You > can check the uptime of your masternode by running syscoin-cli masternodelist activeseconds | grep > yourIP and the number of masternodes by running syscoin-cli masternode count

So if there are 1300 total masternodes, that means (1300 *4) / 60 = 86.6hrs

Hi :slight_smile:
yes that formula is correct, but the console command has a bug.

You get the uptime more easily from the My Masternodes tab, but if you want to use the command line or debug console try:
masternodelist json [YOUR_IP] where you replace [YOUR_IP] with your vps IP.
Look for the activeseconds field.

I just created a bug report on github for this:

got the first reward, took a little bit longer than my calculation and the 0 seconds on activeseconds output confused me.

great job syscoin team, the new support method over this forum works very well!

1 Like