I will make the official post for the release tomorrow, just wanted to let it run for a few days so I am sure it works.
For supernodes it will be mandatory since supernodes should run the most recent version.
Installed Version 0.6.95
Problems continue. (((
Configuration
Windows Server 2012 R2 Datacenter
Plan: G2.4GB
CPU: 2 vCPU
RAM: 4 GB
Disk: 100 GB
Term: On-Demand
Transfer: 4096 GB
How can I fix this?
figured out … I fixed the problem with ports 7778,7880,7890
i can see much higher supernode payouts
what happened?`
from ~ 320
to ~420
dont get me wrong i like it but i want to know the reason
or is it many take profits and break their required 3 million balance?
Maybe more supernodes didn’t pass tests?
Reason is that ~100 supernodes owners did not realize that their supernode have memory problems.
There are two identical inquiries currently to me.
When changing from 0.6.93 to 0.6.95, the following error appears.
In addition, returning to 0.6.93 will work normally.
Are there any points you have noticed?
[nem@sn package]$ ./nix.runNis.sh
Exception in thread “main” java.lang.ExceptionInInitializerError
at org.nem.deploy.b.(CommonConfiguration.java:84)
at org.nem.deploy.b.(CommonConfiguration.java:51)
at org.nem.deploy.b.(CommonConfiguration.java:34)
at org.nem.deploy.CommonStarter.(CommonStarter.java:53)
Caused by: org.nem.core.crypto.CryptoException: java.security.NoSuchAlgorithmException: no such algorithm: Keccak-256 for provider BC
at org.nem.core.utils.ExceptionUtils.propagate(ExceptionUtils.java:85)
at org.nem.core.crypto.Hashes.hash(Hashes.java:51)
at org.nem.core.crypto.Hashes.sha3_256(Hashes.java:25)
at org.nem.core.model.Address.generateEncoded(Address.java:83)
at org.nem.core.model.Address.(Address.java:78)
at org.nem.core.model.Address.fromPublicKey(Address.java:42)
at org.nem.core.model.NetworkInfos.createMainNetworkInfo(NetworkInfos.java:111)
at org.nem.core.model.NetworkInfos.(NetworkInfos.java:12)
… 4 more
Caused by: java.security.NoSuchAlgorithmException: no such algorithm: Keccak-256 for provider BC
at sun.security.jca.GetInstance.getService(GetInstance.java:87)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:206)
at java.security.Security.getImpl(Security.java:698)
at java.security.MessageDigest.getInstance(MessageDigest.java:227)
at org.nem.core.crypto.Hashes.lambda$hash$0(Hashes.java:52)
at org.nem.core.utils.ExceptionUtils.propagate(ExceptionUtils.java:73)
… 11 more
Hello.
I have upgraded my vps a week ago from 3 cores to 4 cores and from 6GB to 8GB ram because it was still experiencing FAILS once per round.
I switched from 0.6.93 to 0.6.95 2 days ago.
I have changed the script to start with following parameters:
java -Xms$MINRAM -Xmx$MAXRAM -XX:+UseG1GC
where MINRAM and MAXRAM is seto to 5G.
Servant is set to start with 256M .
But now it seems to be even worse:
https://supernodes.nem.io/details/801
All fails on computing power.
I can’t upgrade my vps any more I can only switch to a dedicated server or try to change vps hosting provider.
I will restart the nis and reduce the MINRAM MAXRAM 4.5G to leave more memory for the system.
I know it will pass the tests few times after restart but after one round it starts failing again. 
It happened so last few times i have restarted.
Lets see. :
That looks like you mixed the jars. You have to fully replace 0.6.93 with 0.6.95, not only the nem jars.
I would change the provider, go for vultr, they got KVM virtualization which guarantees your server is fast enough to pass the tests.
OK thank you.
I will have to do this it seems there is nt other solution.
Only thing on this vultr is they have only credit card payment which i dislike. :-1
Btw. do you know if is possibile to have 2 supernodes linked to 1 account(address) or the stake
should be split into 2 two separate accounts (addresses) to run 2 super nodes?
Thanks.
You can pay with btc.
You need to split the account if you want to run 2 supernodes.
unn, They had the following command executed.
find . -name "*0.6.93-BETA.jar" -exec rm -rf {}¥;
That is not enough, you need to replace every jar. The error you got is due to the jar “bcprov-jdk15on-1.50.jar” not being replaced by the newer version “bcprov-jdk15on-1.58.jar”.
1 Like
Maybe that! I will tell it.
It moved. It looks like that jar file.
BTW,
Servant has the same jar file in the Servant’s directory, is not it updating it as it is planned?
the servant uses its own set of jars, no need to update.
1 Like
Please upgrade the server to 4GB and adjust the parameter for the heap in the startup script. Then restart NIS.