In my opinion, nodes forking occurred around 3 pm on the 24th (UTC).
A node that does not capture the block observed that it occurred on a server with up time of 6 days or less when the cause occurred.
(Super)nodes measuring failing again and again, now, beside the Height/Chain Part, with the Balance item too. Do we already know, why this is occured and why it’s still happening ?
Height / Chain Part yes.
The balance is not affected. Maybe someone change his Balance of xem. It´s only one SN.
Date Sun Feb 26 2017 02:50:30 GMT+0000
Expected Min Balance 3000000
Reported Balance 2999912
Well, but do we know, why there is still fork (or some outage) in the network? When I’m connected with my local NCC to my supernode, it’s still writes: “NIS is synchronizing. At block 997307, est. 1 day behind. (at block 997307)” … it looks quite the same as yesterday. Restart of supernode didn’t change anything.
We should wait until the developers found the reason.
Just keep your SN running. I’ll do the same.
It may be something of the reward lost, but that is ok( I think ).
NIS version 0.6.84 is available
This upgrade is mandatory!
Please upgrade till next sunday, i will upgrade the referende NIS on monday
Hi,
I updated to last one version and everything is fine, but still get fail results (Height, Chain part and Version)
ip - 13.113.99.29
https://supernodes.nem.io/details/515
Could you please help to fix it?
Thanks in advance
your node is showing a wrong public key:
9852c578a878f7cc739247ad19c1e801f73257e3deba3d11c5cb2e8957932b54
http://13.113.99.29:7890/node/info
probably you have overwritten your config when installing the new version?
whats the easiest way to update my Node? is there any tutorial? Everytime i have to delete and install when there is no version
Easiest way is to copy the 4 nem jars and then restarte NIS.
Try this tutorial, then scroll down to the ‘4. Update Guide’ section
Hi, thanks for the help.
My node crashed cause of the known issue, so I switched to another (for delegated harvesting only).
Now I installed last one version made all configurations, but forgot to switch IP on my node,
Thanks for the help.
I I was participating in the SuperNode program.
This time exporting from NCC to Nanowallet and changed the server, so IP, and Delegated Key has been altered.
Is additional enroll message that I sent accepted?
If it was not accepted, I would like required solusion.
My address is NBIXPW-LQS3QN-KRRKXM-5WUAGM-DGEZOP-2TMK3R-DB5V
i have to check tomorrow morning, no time now.
Thank you!!
Hi,
How much time need to wait for the 1st payment?
https://supernodes.nem.io/history/search/XemXemXem
Thanks
Here you can see payout rounds. (that explorer have some trouble in other areas)
You sent 2 enroll messages with different IPs. Which one is valid?
Could you please help me to fix my supernode?
https://supernodes.nem.io/details/214 I sent a meassage to enroll it again, and its appeard on Nembex as Kooream2 (I just asked to change the alias back to Budapest today) but after 24+ hour it still hadn’t been tested.
Should I set up a new hostname and alias?