Nembex’s node list has not been updated.
The message will also be displayed in the NanoWallet.
It is displayed when you try to transfer money to Deligate Account (Remote Account).
1 Like
Strange…could you shutdown NIS, backup the db, restart NIS and see if it is syncing then?
I would be interested to get that db to analyze what the problem is.
This is the db
http://88.99.87.132/nis5_mainnet.h2.db
NIS is restarting now with FINER log
and db from scratch by bob
Test1: restarted NIS with db from Bob, db was at height ~1002000. My node synced without problems.
Test2: restarted NIS with db quasarblue supplied. The fork was resolved immediately and NIS synced without problems.
Not sure what the problem with your node is/was. Can you check that the node is using all 0.6.87 jars and there are no old 0.6.84 jars around in your installation?
Done.
Thanks @BlookyRookie
Solved rewriting package NIS binaries directory using tar archive.
Can you send that message to NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3 from the account that you used to enroll the node?
I am only hosting the supernode and do not have control of the account but will ask the owner. He’s selling 500k XEM and I’ve been unable to figure out how to use mine to top him off in a trustless fashion.
Sent: http://chain.nem.ninja/#/transfer/06ec946e34921f51e08a9668b654f3687f04411012d3d908c88066258ffbe3a2
Sorry to be pedantic but this is the account that enrolled https://supernodes.nem.io/details/226
1 Like
Oops yes there must be some miscommunication on our end. Apparently he defunded TehSuperNode2 (https://supernodes.nem.io/details/226). You’ll see it no longer has 3 million XEM. TehSuperNode3 will remain operational.
Glad you are thorough!
ok, done.
1 Like
Thank you. Sad to see it go but it will live on as on non-super node 
I see nodes that have a balance between 2M and 3M which obviously don’t pass the balance test. Either refill or your node will temporarily be disabled since it doesn’t make sense to do other tests if the balance is below 3M
I also see nodes that have not upgraded to 0.6.87. Either upgrade or your node will be disabled
Not yet but still researching…
Please let me understand if I’m right interpreting NIS log on a block gen.
first hit:
2017-05-21 18:22:42.440 INFO [HIT] harvester: NDW5VFXFZXNMANFOXYFDNZPDLLWOTKHX746L23AG (org.nem.nis.harvesting.BlockGenerator a)
2017-05-21 18:22:42.441 INFO [HIT] harvester effective importance: 3043207 (org.nem.nis.harvesting.BlockGenerator a)
2017-05-21 18:22:42.441 INFO [HIT] last block: 7fa774735ec6a73f63cc8f0b0e90dbc297081b0d9ad993f1e9bd4614af7a46a9 (org.nem.nis.harvesting.BlockGenerator a)
2017-05-21 18:22:42.446 INFO [HIT] timestamp diff: 227 (org.nem.nis.harvesting.BlockGenerator a)
2017-05-21 18:22:42.446 INFO [HIT] block diff: 143384578997421 (org.nem.nis.harvesting.BlockGenerator a)
this is correct as block
7fa774735ec6a73f63cc8f0b0e90dbc297081b0d9ad993f1e9bd4614af7a46a9
is number 1119535
then next block
http://chain.nem.ninja/#/block/1119536
is harvested by
NDW5VFXFZXNMANFOXYFDNZPDLLWOTKHX746L23AG
This case hereunder the next block harvested
does not belong to NDW5VFXFZXNMANFOXYFDNZPDLLWOTKHX746L23AG
contrary to the log…could you explain?
2017-05-22 03:31:49.740 INFO [HIT] harvester: NDW5VFXFZXNMANFOXYFDNZPDLLWOTKHX746L23AG (org.nem.nis.harvesting.BlockGenerator a)
2017-05-22 03:31:49.741 INFO [HIT] harvester effective importance: 3053417 (org.nem.nis.harvesting.BlockGenerator a)
2017-05-22 03:31:49.741 INFO [HIT] last block: 0caea3ecf16a51f1ffab94ec7be8a5e21747dd7f133292060950ae4b84f96f66 (org.nem.nis.harvesting.BlockGenerator a)
2017-05-22 03:31:49.741 INFO [HIT] timestamp diff: 31 (org.nem.nis.harvesting.BlockGenerator a)
2017-05-22 03:31:49.742 INFO [HIT] block diff: 124393875810670 (org.nem.nis.harvesting.BlockGenerator a)