@Swordsman20: since the transaction volume is still quite low in our chain, such a server is serious overkill 
If you make many VPSes out of that and can assign 1 ip per vps you could run many nodes of course. But usually the ips are the problem to get. Also a supernode requires a balance of 3M xem which is a lot these days too.
Since I changed my Remote account,
I want to abolish # 453 and register newly.
However, I sent enroll commands etc. I made a mistake in various ways.
Even if you send the correct one, it will not be reflected.
I was told to mizunashi that if it is a server with the same IP it needs to be written here and processed.
please send the data for your node in a message to
NALICE-PFLZQR-ZGPRIJ-TMJOCP-WDNECX-TNNG7Q-LSG3
Use the account you used to enroll node #453.
OK, I sent that node data.
I appreciate quick response.
1 Like
REWARDS HISTORY and etc has not been updated. Please check the operation.
Perhaps in a matter of hours, people in Europe begin to get up.
Yup there is an issue. Last performance results of my node was around Wed Aug 02 2017 02:00:00 GMT+0000.
does anyone paid for supernodes yesterday?
Sorry guys, the master had problem, fixed now
1 Like
These 3 supernodes each failed at different rounds. Does the new update require more computing power? My current plan on HostUS is KVM-3. Do I need to upgrade my hosting plan? If so, which plan do you recommend?
The three nodes are below:
Gambit_WI
Cyclops_WI
Tiger_WI
Those nodes are more than fine. Looks to me that it rather was a network problem. since the responsiveness test failed. That can happen and has happened to my nodes too in the past. I expect your nodes to pass subsequent rounds. So i would not worry about it.
1 Like
They continue to fail, do you think it’s the service provider issue? Should I change it or should I just continue to wait to see if this passes?
https://supernodes.nem.io/details/653
https://supernodes.nem.io/details/771
https://supernodes.nem.io/details/785
It is strange, the nodes are certainly strong enough. How much RAM do you give to NIS / Servant?
I didn’t specifically configure it so whatever the default is. The host plan gives 3GB Ram. The OS is CentOS with GNome as GUI.
First 2 nodes have been working relatively stable until a few days ago, the only change I made was the upgrade. The last node is a new node.
With 3GB RAM i would change the startup scripts to have something like
-Xms2000M -Xmx2000M
for NIS and
-Xms256M -Xmx256M
for the servant.
If you have RAM then let the vps use it ^^
Ok, I will do that, thank you. Wish me luck
I changed the start up scripts, 2 of them still failed today. I am going to change service provider for one of them to see if it makes any difference. Do you have any recommendation for another provider?