Indeed. I deactivated the old db entry and added a new one:
BloodyRookie, thanks you!
thank you.
Hello everyone,
Im having connections problems at the rounds checks. The server is online and serving as a remote harvester for 2 other people. But the test fails on the page,
https://supernodes.nem.io/details/605
2017-12-29 17:07:36.642 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:37.080 INFO entering /time-sync/network-time [190.56.75.78] (org.nem.nis.controller.interceptors.AuditInterceptor preHandle)
2017-12-29 17:07:37.081 INFO exiting /time-sync/network-time [190.56.75.78] (org.nem.nis.controller.interceptors.AuditInterceptor afterCompletion)
2017-12-29 17:07:37.568 INFO received 1 blocks (2 transactions) in 179 ms from remote (89500 μs/tx) (org.nem.nis.sync.BlockChainUpdater c)
2017-12-29 17:07:37.644 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:40.044 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:42.743 INFO 2 harvesters are attempting to harvest a new block. (org.nem.nis.ld.gah cH)
2017-12-29 17:07:42.773 INFO validated 1 blocks (2 transactions) in 5203 ms (2601500 μs/tx) (org.nem.nis.sync.BlockChainUpdateContext fz)
2017-12-29 17:07:42.773 INFO new block’s score: 119770424750693 (org.nem.nis.sync.BlockChainUpdateContext a)
2017-12-29 17:07:42.798 INFO chain update of 1 blocks (2 transactions) needed 25 ms (12500 μs/tx) (org.nem.nis.sync.BlockChainUpdateContext fz)
Can you please help me out, thanks
Maybe the server was offline and you recently started it? It will pass all tests next round.
Thanks for your response.
I have my nano wallet linked to it, and it shows my balance etc. Its been online for the last few months, I only restart the OS after a new NEM version is intalled. After I notice the problem I restarted it around 4am, and everything seems fine in the log.
But it has already failed two tests today. The connection port looks fine, Im thinking maybe there are more transactions now and the servers needs more CPU or RAM??
thanks again
As i said, it will pass the next round. However, if your supernode got less than 2 GB, I would suggest upgrading it to 4GB and adjusting the startup script to give NIS 2800MB heap.
Thank you sir!
I switched from NCC to nano wallet, but the reward check came to fail. I tried various investigations because I do not know the cause. One of the reasons is that since the delegation public key has changed even at the same address, I heard that it is necessary to change the setting manually now.
In that case, how can I ask for it?
Should I just write SN names and public keys directly in this forum? Or should I contact someone?
IP address and delegation public key are here.
http://153.122.60.153: 7890/node/info
Here is the server name and the review status
https://supernodes.nem.io/details/283
This is the old delegation public key we used with NCC.
6d2ef1b7aa9cb974fa668a8b12c4d056286e37fc3dd06d7d54b46433d77c0894
Send a message to NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3 from the account you used to enroll that supernode. Message should be something like “please change the public key to 6d2ef1b7aa9cb974fa668a8b12c4d056286e37fc3dd06d7d54b46433d77c0894”. I will then disable the old supernodes db entry and add a new one.
Thank you so much, I count on you. I have just sent a message.
Hi , BloodyRookie.
I changed 3 SNs 2GB to 8GB,and changed nis startupscript to Xmx5G,Xms5G. 24hrs ago.
they did not change IP-address,deligated-keys,and so on.
I think they works fine,isn’t it?
http://157.7.197.62:7890/node/extended-info/
http://157.7.197.62:7880/nr/metaData
http://157.7.198.84:7890/node/extended-info/
http://157.7.198.84:7880/nr/metaData
http://157.7.196.200:7890/node/extended-info/
http://157.7.196.200:7880/nr/metaData
but NEM node reward says fails. have I any problems?or just be waiting?
https://supernodes.nem.io/details/754 755 756
The public key displayed in the links above is different from the public key that is in the database. For example
http://157.7.197.62:7890/node/extended-info/
shows
b5a0564d757a31d58e6c093f3f86206a0c5df078714f4e9c0b529cada3a0a4df
which is your main account’s public key while in the database is see
b973cb6b2659cd6d33cd60b14d8e9c7c89e0d09f4cc5a8d3c7af6a688b4cbef2
which is the delgated public key of the account. Don’t use the main private key on the supernode, that is risky!
So change the config and use the delgated private key please.
Same goes for the other two servers of yours.
I see,
I check it soon. thank you.
Hi @BloodyRookie - wanted to add my new super node in.
My enroll txHash is d795a292f97f9108301868090cbb54d166a351ec7929c80a0808fc967ddfe6e6, can you please check if the TX is fine?
It was successfully judged and passed on the correctly registered node. Thank you very much.
Hi, neverminded, was the change (to -Xms3G -Xmx3G) successful for you ? There is absolutely the same problem by me – I have “rock solid” node, passed all the test for couple of months, 16GB RAM (just on Linux), and last week I have repeatedly troubles with Height and Chain part in the measuring (and thus my node is failing the tests). Upgrade from 0.6.93 to 0.6.95 doesn’t solve the situation.
I guess it was since he didn’t state the opposite 