Sorry, wasn´t sure if ncc is involved. It seemed to be related to servant doing pingpong.
It`s a Computer at home. I thought it would work while NEM is in its early Phase. But maybe I have to stop, at least every third Test is a Fail…
Sorry, wasn´t sure if ncc is involved. It seemed to be related to servant doing pingpong.
It`s a Computer at home. I thought it would work while NEM is in its early Phase. But maybe I have to stop, at least every third Test is a Fail…
@teletobi75: Since it is a computer at home i would like to ask:
Edit: Maybe I should consider setting up a VPS…
No worries , happy to help
Owner of the following nodes, please check your supernode’s NIS/Servant:
I restarted the master with a new version. The new version has two improvements:
Nodes that failed the responsiveness test due to timing are given a second chance. If the fail a second time the tests is considered as failure.
A new algorithm for adjusting the round timing is used. It should quickly converge to the target time of 6 hours. Thus the payouts should be indeed once a day.
I decided to go with that approach since too many nodes failed the responsiveness tests. Thx for the suggestion.
Great, I’m glad to help ;-). (and yes, it probably works, I hadn’t any “fail responsiveness test” since this change). Anyway, to your previous post/question: Unfortunately I’m not so familiar with Java (I’m working mostly in bash or Perl, sometimes with pure C), so I cannot help you with this kind of code too much. But if something will be necessary with Linux servers or “network issue brainstorming”, I’d try to help as much as I can. It’s really nice to see, how NEM developers hardly work and how NEM as a community and as a project continuously grows. Let’s rock!
OK BR, I give up. The Version Test keeps failing. I´ll try to set up a VPS the next Days. What do you need from me to update your Database? Where should it be located for best NEM Performance?
What do you need from me to update your Database?
See first post in this thread. you need to send a correctly formatted message to the node rewards account.
Where should it be located for best NEM Performance?
Node in Australia/Singapore/Korea/HongKong are most welcome. But if you want it cheap then a node in the US is probably the way to go.
OK BR, I give up
Wait…what have you got in the NIS config.properties for the entry “host”?
nem.host = 127.0.0.1
host name = bob.nem.ninja (this is not activated)
@teletobi75: after i talked to Leon who had similar problems i have an idea:
Copy the config.properties to config-user.properties. Then in that file make the changes:
nem.host = nem.noip.me
nis.ipDetectionMode = Disabled
Then restart NIS. Let’s see if that solves the problems
And upgrade NIS to 0.6.76 before doing that.
Everyone please upgrade to 0.6.76 please. In about one week i will upgrade the reference server and then old nis versions will fail the node version test!
It’s currently not possible to download from download.nem.io or bob.nem.ninja - both are either down or extremely slow.
But the downloads are pointing to version 0.6.77 not 0.6.76. Furthermore, the zip archive seems to be corrupted. It has a size of only 300 Bytes
It´s working on bob.nem.ninja now.
Just downloaded nis 0.6.77 and changed config-user.properties.
let´s wait and see…
Everyone please upgrade to 0.6.76 please. In about one week i will upgrade the reference server and then old nis versions will fail the node version test!
What’s the main update/difference between 0.6.75 and 0.6.76 (or 0.6.77) - is some changelog over there ? And, anyway, why 0.6.77 was here so quickly after 0.6.76 … was it a “problem of a missing semicolon”, as I’m saying sometimes (in my programs, about the mistakes, those are too small and too uneasy to find and fix) ? Thanks.
The main difference was a fix of a bug which lead to error messages when importance transactions where included in a block. 0.6.77 was released because 0.6.76 had a wrong config file.