NEM Supernode Rewards Program

Blog Posts
#812

All ips were changed i think.

1 Like
#813

Can somebody give me advice why my node is failing all the tests except the balance test?
My server name is meyns2 and the ip is 148.251.255.171

I checked if the servant is running with this: http://148.251.255.171:7880/nr/metaData
http://148.251.255.171:7890/node/info seams fine as well

#814

check configuration:
to noderewards supplied public key: 611f80b4eeeda533ce66ae00cb154b8cb9db6e8f5274df459afe078e3b7979d8
reported public key by NIS: dd3f1c7dd8f61bfdc0bf65437ebb25c11d311f9d9ec7d6cab6b5ee4e49c08df7
reported public key by servant: 46909ec762a33d73f9af4b94e39a02dae787833c1299912be96a333a835973c8

#815

Thanks for checking bloodyrookie, checked all the keys, and changed it to the proper ones

#816

@BloodyRookie
Node rewards payout: round 1477-1480
Node rewards payout: round 1481-1484
was not paid. Please check. not only my SuperNode. many SN didnā€™t received.
It seems stopped since Block Height 907949, 2016-12-24 13:25:51.

#817

Confirmed, payout not active. I will inform QM. The payout is not lost, just delayed.

#818

Thanks for your prompt confirmation!! :grinning:

#819

I have changed IP of supernode ā€œTrayā€, and sent a new activation request.
Thanks @BloodyRookie

#820

node rewards payout is working again

#821

Thanks! confirmed PAYOUT: round 1477-1480.
Waiting for 1481-1484.

#822

All delayed payouts were confirmed. Thanks for your support :slight_smile:

1 Like
#823

did increases the supernodes?

is lot of months with same amount

#824

The number of supernodes passing the tests is relatively stable around 345.

2 Likes
#825

@BloodyRookie
Happy new year, sir!

Excuse me, my bandwidth test is failins since for approx the last week. See:

Screenshot from 2017-01-02 11-09-56.png1061Ɨ601 80.5 KB

I checked connectivity of the VPS server and even investigated with the Operator.

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
-> /dev/null 100%[==========>] 100.00M 11.0MB/s in 9.0s

wget -O /dev/null http://speedtest.dal01.softlayer.com/downloads/test100.zip
/dev/null 100%[=======>] 100.02M 5.13MB/s in 24s

wget -O /dev/null http://speedtest.ams01.softlayer.com/downloads/test500.zip
/dev/null 100%[========>] 500.00M 8.76MB/s in 68s

wget -O /dev/null http://speedtest.sea01.softlayer.com/downloads/test100.zip
/dev/null 100%[=========>] 100.02M 4.56MB/s in 27s

Means: I get >20Mbit/s stable thereā€¦
Where exactly is the speedtest of the supernode servant testing module testing against?
Can I traceroute the destination to track down the problem?

Thanks for any assistance with this.
I donā€™t want to move the server out of Africa, I want to be further supporting NEM adoption there!!

R.

#826

The master tries to pick a node that has a good connection to the node getting tested. In your case that is most likely one of the nodes Africa1 and Africa2. But those are only 1GB nodes and that means they have to restart NIS from time to time, else the garbage collector will be invoked too often.
I have restarted NIS on the two nodes, hopefully your node is doing better now.

#827

ok thanksā€¦ will check back on this tomorrow. R.

#828

It didnā€™t help. Still failing.

Screenshot from 2017-01-03 12-30-50.png1095Ɨ354 55.6 KB

What do you suggest to do? Investigat in supernode-servant logs? PM you ssh access into my Supernode? :blush:
I can move away from that datacentre but as mentioned, i like their actually quite good connectivity, price and friendly service. Itā€™s http://clickworks.co.za/

R.

#829

I donā€™t know. The funny thing is that it used to work very well and then suddenly our african nodes all didnā€™t do well any more.
i will take a look at the logs today, not sure that it helps thoughā€¦

#830

I just sent the ā€˜change ip 216.189.147.226 to 216.189.147.024ā€™ message.

#831

I think it worked.