Hello.
Can you change ip for this node
from 37.59.120.16
to 161.97.64.90
Thanks.
Did you sent the ip change message to the node rewards account? If yes, can you paste the hash of the transaction?
No sorry I’ve forgot that this should be done as I haven’t made changes to the node for years
except for the NIS version and server upgrades.
Should I send the message in unencrypted format?
Yes.
Done!
tx hash is: ab2381d26d4def889432908c5470d7c8318e1346b12cbfbf17095ac2be54c23f
@all,
I have made an important update on the Supernode’s fund here. Symbol Launch - NIS1 Future Strategy Recommendation
2 Likes
Hi, I was trying to enroll nodes tdxem01 & tdxem02
But it is stated that they are inactive in nodes’ list.
What’ wrong with them?
Can you please paste the hashes for the enroll transactions?
0fddd31cdb3d1210776ca6a80d4cf653ad5e13de6e3e8445d73b493760040b7e
and
a25b80570eb5fec598a1f5913a861d28ca904e76449b7cf0a4096ca6c11adef1
You are trying to enroll with ips that have already been used. Are those nodes old nodes you want to reactivate with a different delegated keys and different names?
Yes, we have changed keys and names also
Ok, i added the nodes manually to the database.
1 Like
@teodor: tdxem02 does not have the needed xem in its account. Are you sure you provided the corrected delegated key?
It matches with the ones in NanoWallet
public is in https://explorer.nemtool.com/#/s_tx?hash=a25b80570eb5fec598a1f5913a861d28ca904e76449b7cf0a4096ca6c11adef1
(I’ve sent another enroll message)
private is 879…d16f
vested balance is above 3m
97ab62039b30e015e8fe8c87090d1bae170177e709f85656afd44248c93c2068
sorry, here is another one enroll hash
But balance seems to be 0:
https://supernodes.nem.io/archive/1118/6627
what is the main account’s public key for tdxem02?
Edit: the delegated key appears to be 049877675c2e24013832a741f2d6c3890ea81b14303f1a0bd91afe4ba11df501
as can be seen here:
http://chain.nem.ninja/#/account/NBGXUFTY75MI3N7HYGZMPFIEQBIDGPHRGQG2MFUI/0
I inadvertently removed the /nem/nis/data/nis5_mainnet.h2.db file and so did a reboot to regenerate it. But once my supernode (KingsLandingUsesNEM2) starting passing, I noticed it was no longer auto harvesting. Nothing changed in my config-user.properties file. I got this message in the log file for one of the accounts:
2020-07-17 13:23:14.737 INFO auto harvesting with ‘NCLRWZ45BGYGUZP7BAKQ4DXST6XXPMDDGZ2ENM5X’ -> ‘FAILURE_UNKNOWN_ACCOUNT’ (org.nem.nis.boot.HarvestAwareNetworkHostBootstrapper b)
That was the address that xem were sent to activate delegated harvesting back in 2017. Does regenerating the nis5_mainnet.h2.db file on a reboot change auto harvesting?
The account was created after the nemesis block, therefore when resyncing, the NIS does not recognize the account in the beginning and therefore outputs that message. If your node is synced now, you need to restart NIS and it should work.
Hello, we’ve changed the delegated key and I have tried to enroll node, but still no success for tdxem02. tdxem01 is fine.
Can you please paste the enroll tx hash here?