NEM Beta 0.5.16


#1

Beta 0.5.16 is here!

FORK coming at 43000

There's not much of "visible" changes.
Changes:


    [li]We've changed the way transactions are validated (simplified it a lot, this will make testing validators much easier and more sensible), upcoming fork is related to that[/li]
    [li]The point above is actually HUGE change, and it also alters the way transactions are "executed"[/li]
    [li]We've made final adjustment to PoI parameters, after BTC blockchain analysis[/li]
    [li]There are new and updated docs for NIS[/li]
    [li]Excluding btc analysis data the DIFF since 0.5.13 is 800k[/li]


    DOCS: [url=http://bob.nem.ninja/docs/]http://bob.nem.ninja/docs/, besides lots of structures used, there are some valuable descriptions there, so you're encouraged to take a look at it.

    Especially chapters starting from 6.4 [url=http://bob.nem.ninja/docs/#converting-an-account-to-a-multisig-account]http://bob.nem.ninja/docs/#converting-an-account-to-a-multisig-account might be interesting.

    [hr]

    NEM requires Java 8
    You can start NCC and NIS with an installer from the following link:
    http://bob.nem.ninja/installer/
    Standalone version: http://bob.nem.ninja/

    [hr]

    Enjoy the new version :slight_smile:

#2

Great work on the ninja docs.

I really suggest everyone take a look.


#3

TC5HHL-3HFFMN-GHO33X-RQPJI3-RFLGDH-3CKQC4-3AYP

trying new client …anybody got NEM?


#4

There are starting harvest without accessing the GUI?


#5

Wow http://bob.nem.ninja/docs/. This is really written professionally  and was a pleasure to read. KUDOS devs :slight_smile:
Now we can redirect users to this document if they are having any problems :slight_smile:


#6

nice job devs. :slight_smile: updating nodes now.


#7

If you entered all information, then there shouldn't be a warning about missing information of course. Seems like a bug.

The activation of remote harvesting takes 1440 blocks. I have no idea, why this information is not displayed for the user…


#8

Can't send transaction, error "Oooops, 306 error". Did nothing, client fully synchronized. Restarted everything, getting same error.

Logs at https://www.dropbox.com/sh/llgmz8xnicvmc1j/AACW1VyNBNMHapb8TyWcieNKa?dl=0


#9

Can't send transaction, error "Oooops, 306 error". Did nothing, client fully synchronized. Restarted everything, getting same error.

Logs at https://www.dropbox.com/sh/llgmz8xnicvmc1j/AACW1VyNBNMHapb8TyWcieNKa?dl=0


I see in the logs:


2015-03-04 07:15:56.254 INFO Http Status Code 400: address must be valid (org.nem.core.connect.ErrorResponse <init>)


Seems the address you provided in not valid. Can you check on that?

#10


Can't send transaction, error "Oooops, 306 error". Did nothing, client fully synchronized. Restarted everything, getting same error.

Logs at https://www.dropbox.com/sh/llgmz8xnicvmc1j/AACW1VyNBNMHapb8TyWcieNKa?dl=0


I see in the logs:


2015-03-04 07:15:56.254 INFO Http Status Code 400: address must be valid (org.nem.core.connect.ErrorResponse <init>)


Seems the address you provided in not valid. Can you check on that?


Sorry, I'm back now. I see the problem, somebody asked to send test XEM but gave real address. I tried to send XEM to real address :)
Good news, checking of account working properly :)

#11

My node is delayed, i have just start it after fall, but do not synchronize with the last block.
In this case i can not harvest?
http://mountains.no-ip.biz:7890/node/info
Here logs today, nis-0.log.1 is the most recent period.

https://drive.bitcasa.com/send/e-595cOb3omUqypyYnkBoilGShopya1UbFRqrXlsnNPT

I try now to resync of blockchain of the bob.nem.ninja


#12

My node is delayed, i have just start it after fall, but do not synchronize with the last block.
In this case i can not harvest?
http://mountains.no-ip.biz:7890/node/info
Here logs today, nis-0.log.1 is the most recent period.

https://drive.bitcasa.com/send/e-595cOb3omUqypyYnkBoilGShopya1UbFRqrXlsnNPT

I try now to resync of blockchain of the bob.nem.ninja


Your node had indeed problems syncing with the other nodes. I guess you deleted the database with which you could not sync? If yes, please don't delete it next time. Would be interesting for me to take a look at it.

#13


My node is delayed, i have just start it after fall, but do not synchronize with the last block.
In this case i can not harvest?
http://mountains.no-ip.biz:7890/node/info
Here logs today, nis-0.log.1 is the most recent period.
....
I try now to resync of blockchain of the bob.nem.ninja


Your node had indeed problems syncing with the other nodes. I guess you deleted the database with which you could not sync? If yes, please don't delete it next time. Would be interesting for me to take a look at it.
I keep a copy of the .db, after resync it still does not work, i tried a few times without success.
Here .db and last logs
https://drive.bitcasa.com/send/_qBCeuNncbfCMCr83S4AKLoNNmroF_M7piO_JO0sEP39

#14



My node is delayed, i have just start it after fall, but do not synchronize with the last block.
In this case i can not harvest?
http://mountains.no-ip.biz:7890/node/info
Here logs today, nis-0.log.1 is the most recent period.
....
I try now to resync of blockchain of the bob.nem.ninja


Your node had indeed problems syncing with the other nodes. I guess you deleted the database with which you could not sync? If yes, please don't delete it next time. Would be interesting for me to take a look at it.
I keep a copy of the .db, after resync it still does not work, i tried a few times without success.
Here .db and last logs
https://drive.bitcasa.com/send/_qBCeuNncbfCMCr83S4AKLoNNmroF_M7piO_JO0sEP39


Just skimming the logs it looks like something is off with timesync.

#15

I keep a copy of the .db, after resync it still does not work, i tried a few times without success.
Here .db and last logs
https://drive.bitcasa.com/send/_qBCeuNncbfCMCr83S4AKLoNNmroF_M7piO_JO0sEP39


Seems that your node cannot take the heavy load due to the spamming. Probably low memory makes the node very slow (spending most of the time for garbage collection) and thus is unable to serve all the requests. Finally the apache i/o reactor shuts down and the node is dead.
I guess it is a node with only little memory, right?

#16


I keep a copy of the .db, after resync it still does not work, i tried a few times without success.
Here .db and last logs
https://drive.bitcasa.com/send/_qBCeuNncbfCMCr83S4AKLoNNmroF_M7piO_JO0sEP39


Seems that your node cannot take the heavy load due to the spamming. Probably low memory makes the node very slow (spending most of the time for garbage collection) and thus is unable to serve all the requests. Finally the apache i/o reactor shuts down and the node is dead.
I guess it is a node with only little memory, right?


Yes, i had left a script sending every 10 seconds and disposal of about 500MB ram, and most of the time it uses the swap. So that's it?
I tried to re-sync .db from scratch, and use the default memory values of the nis, it worked for a while but then fell, im not sending XEM more. How return to default?

#17

Yes, i had left a script sending every 10 seconds and disposal of about 500MB ram, and most of the time it uses the swap. So that's it?
I tried to re-sync .db from scratch, and use the default memory values of the nis, it worked for a while but then fell, im not sending XEM more. How return to default?


When trying to sync from scratch, i would not harvest and not let run any script. Maybe it is the easiest to download a db from bob.nem.ninja. The memory settings to use with NIS depend on the memory the vps has. Just use the settings that have worked for you best so far. But as long as the network gets spammed very hard your node might get killed again and again.
I can upload the current db but it will take a while ^^
So you can check if there is a new db on bob.nem.ninja in 1-2 hours.

#18


Yes, i had left a script sending every 10 seconds and disposal of about 500MB ram, and most of the time it uses the swap. So that's it?
I tried to re-sync .db from scratch, and use the default memory values of the nis, it worked for a while but then fell, im not sending XEM more. How return to default?


When trying to sync from scratch, i would not harvest and not let run any script. Maybe it is the easiest to download a db from bob.nem.ninja. The memory settings to use with NIS depend on the memory the vps has. Just use the settings that have worked for you best so far. But as long as the network gets spammed very hard your node might get killed again and again.
I can upload the current db but it will take a while ^^
So you can check if there is a new db on bob.nem.ninja in 1-2 hours.

OK, seems that it is working now, i set less memory because 1G consumes nearly VPS limit.
I will moderate the time of sending XEM to not fall again. :)

#19



Yes, i had left a script sending every 10 seconds and disposal of about 500MB ram, and most of the time it uses the swap. So that's it?
I tried to re-sync .db from scratch, and use the default memory values of the nis, it worked for a while but then fell, im not sending XEM more. How return to default?


When trying to sync from scratch, i would not harvest and not let run any script. Maybe it is the easiest to download a db from bob.nem.ninja. The memory settings to use with NIS depend on the memory the vps has. Just use the settings that have worked for you best so far. But as long as the network gets spammed very hard your node might get killed again and again.
I can upload the current db but it will take a while ^^
So you can check if there is a new db on bob.nem.ninja in 1-2 hours.

OK, seems that it is working now, i set less memory because 1G consumes nearly VPS limit.
I will moderate the time of sending XEM to not fall again. :)
it was online for a while but then fell.
If you want the files just ask. :)

#20

i have run 768mb, 1024mb and 2048mb ran servers with only nis… only the 2048mb ram server seems to be stable… the smallest one lost connection to nis(when looking as ncc) quite frequently… 1024mb was better but still an issue… 2048mb ram server is running a spam bot flawlessly without any error 500's… i suppose this wont be the case after launch though seeing as the blocks wont be nearly/actually full…? 2gb servers are expensive :smiley: