Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on January 25, 2016, 12:20:23 pm

Title: NRS v1.7.5
Post by: Jean-Luc on January 25, 2016, 12:20:23 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.5

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.5.zip

sha256:

4b29107dede6fc3f576d9a56ecd4b1580e6131ed995775647d07b9347df31e54  nxt-client-1.7.5.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.5.jar

sha256:

d426f614f9407e0b0da3a73fbaf84b5ce2f0a2ad5326a1fa80567ecc9e42eb29  nxt-client-1.7.5.jar

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.5.exe

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.5.dmg

The exe, dmg, and jar packages must have a digital signature by "Stichting NXT".


Change log:

Code cleanup and removal of logic no longer needed after the 1.7 hard fork has
been passed. Added checkpoint at block 622000.

Peers running versions older than 1.7 are now blacklisted.

Allow disabling of specific API or groups of API using the nxt.disabledAPIs and
nxt.disabledAPITags properties, each taking a list of API request names, or API
tag names, separated with ';'. For example:

nxt.disabledAPIs=startForging; startShuffler
nxt.disabledAPITags=Create Transaction; Tagged Data

will disable the startForging and startShuffler API, and all API that are listed
under the Create Transaction or Tagged Data tabs on the API test page.

The enabled/disabled status of each API or APITag is exposed in getConstants.

The client UI hides menus related to disabled API tags and the "Send NXT",
"Send Currency" and "Send Message" buttons are hidden automatically when
their corresponding API is disabled.

The getAccountLedger API has been fixed to always apply the firstIndex,
lastIndex pagination to the final list of entries matching the query, rather
than to all entries for the given account or based on block height.

Use fixed shuffling transaction timestamps. To prevent timestamp correlation
attacks, all shufflers now use the same transaction timestamp, set to the last
block timestamp.

Performance optimizations. Account public keys are now cached in memory. This
cache currently takes around 12 MB at most, and can be disabled by setting
nxt.enablePublicKeyCache=false.

Back button added to the transaction info, account info, block info and ledger
info modals. Use the back button to return to the previous info modal.

Updated H2 to version 1.4.191. The MVStore storage engine is disabled by default
as it is still in beta, PageStore continues to be used. As this version no
longer accepts implicitly relative jdbc URLs, if you have configured a custom db
location in nxt.properties, make sure to prefix the path with ./ if it is not
absolute, e.g. nxt.dbUrl=jdbc:h2:./nxt_db/nxt... instead of
nxt.dbUrl=jdbc:h2:nxt_db/nxt... . If unpacking on top of existing installation,
delete the old lib folder first.

Token generation is now supported when using the "Remember Passphrase" option
and the NRS.signBytes() method now uses the remembered passphrase in case the
passphrase parameter is not specified.

The transition effect displayed when hiding the left menu was disabled since
it is causing UI rendering problems under certain conditions.

"Switch Account" button added to the account info dialog. Clicking it would
switch the wallet to this account.

"Refresh Search Index" option added to the "Settings" menu. Use it to rebuild
the search index in case you are no longer getting correct search results.

Added UI for issuing singleton asset.

run.bat now works on Windows XP and Windows 2003. Database, configuration
files and logs are stored in the roaming folder under the user folder and
tray icon is operational.

Nodes that update from version older than 1.7.3e to this release after the hard
fork block will have blocks after 621000 deleted, to make sure they switch to
the 1.7.4 fork.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWpfu4AAoJENqvaxkWiP4Z6UsP/1hsvVZP/IIp6BPog5va+leY
sAx0pzAXxdKJrINRtYT6DkkX7GwxIhV6T/UOzGqZpVhx73OdGQvHnSI9zmSnCynW
MbCp+saHDchC2N+6ezv2wTqd3wiR2RXGWON+FlU3gAE8ivCU/2eEFGiWfzCUwRST
FpYm7C2aWnJgiYgjI27TKam8Fu1bDgyzHdy3VGaZtfHaRy0b1ivK4975jG9rkUHf
MghnwqKJ4VDcdQ/LM922hTk3OUoWizeyVwa+IR7eg6B9V3xgN1wfhzWFUXx9N0DU
l0+XvbP5yqBf5OsH147TVAMpV1WTo2Ohi+tQbmb3WE3SA+ZXzAAqQVbd/O6NEzNp
gBFXhgnCKBHYL8f+aDHLD/RsRH1C7bZoKhOVN7HoouCYqhKwK3n67WzU2o/fNDvf
DohWJx1aJz+qKxmwaJikNIYiVul6KEO0xl2v0brTtSOr0EQfSdbAre2r4jZ888PI
WWA1xwgh1AIWhRHVXwrumwYpR21zUt4o7OSKMgur+QIl3bhLZQxwk36MhU1PLK+U
Hydt+Bwv81lOTm1BFaIkpTwZ13rCreNKmt0dHnAHtm6B6nNKUq/ubv03DQa2UuXX
oE9qnOxBJr0mznOnVW7Sc4JYs1IY9bZDaR3qvlu1WPGlgnPciwLXDlxY7ne+rsaa
sq3GA2eT/JYwt4RQ53uh
=Dm4t
-----END PGP SIGNATURE-----
Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 25, 2016, 12:28:09 pm
Great work,thanks for listen to fix run.bat.I really like the Back button and switch account button,it's so convenient now.
Title: Re: NRS v1.7.5
Post by: youyou on January 25, 2016, 12:32:11 pm
thx J-L
Title: Re: NRS v1.7.5
Post by: martismartis on January 25, 2016, 12:39:02 pm
DELETED, problem solved
Title: Re: NRS v1.7.5
Post by: blackyblack1 on January 25, 2016, 12:46:23 pm
I saw my NRS 1.7.5 crashing. The reason was I had changed database path in nxt.properties. Here is a hint how to fix it.

With the new H2 engine the configuration format is changed:

Use

# Database connection JDBC url to use with the test network, if isTestnet=true.
nxt.dbDir=./nxt_db/nxt

to change the default blockchain path.
Title: Re: NRS v1.7.5
Post by: farl4bit on January 25, 2016, 02:03:24 pm
Another update, respect guys!  ;D

(http://i67.tinypic.com/1gkqh0.jpg)
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 02:20:57 pm
One of my plugins is showing weird behaviour. (I don't know if I missed something somewhere?)

When connecting to an openapi node I can send out nxt via the "sendmoney api" at http://serverIP/test just fine.
But when trying to do the same via the plugin I receive the error "Could not validate unsigned bytes returned by the server"

The plugin has the below code to send nxt to somewhere

NRS.sendRequest("sendMoney", {"secretPhrase":<secret>,feeNQT:"100000000",deadline:"1440","recipient":<account>,amountNQT:<an amount>,"message":<a message>, "messageIsPrunable": "true"}

The NRS.sendRequest returns the error message received via the json return which states "Could not validate unsigned bytes returned by the server"

When running the plugin on a localhost node it works fine
When running the plugin on a remote host in the same lan it also works

Just seems to be an issue when using an openapi server.
Nothing is shown in the logs or in the console :(

I have checked with 2 different openapi servers and a number of different clients which all results in the same error.

Looking forward to your input!
Title: Re: NRS v1.7.5
Post by: Riker on January 25, 2016, 02:32:21 pm
One of my plugins is showing weird behaviour. (I don't know if I missed something somewhere?)

When connecting to an openapi node I can send out nxt via the "sendmoney api" at http://serverIP/test just fine.
But when trying to do the same via the plugin I receive the error "Could not validate unsigned bytes returned by the server"

The plugin has the below code to send nxt to somewhere

NRS.sendRequest("sendMoney", {"secretPhrase":<secret>,feeNQT:"100000000",deadline:"1440","recipient":<account>,amountNQT:<an amount>,"message":<a message>, "messageIsPrunable": "true"}

The NRS.sendRequest returns the error message received via the json return which states "Could not validate unsigned bytes returned by the server"

When running the plugin on a localhost node it works fine
When running the plugin on a remote host in the same lan it also works

Just seems to be an issue when using an openapi server.
Nothing is shown in the logs or in the console :(

I have checked with 2 different openapi servers and a number of different clients which all results in the same error.

Looking forward to your input!

Try removing the message and messageIsPrunable parameters. If this works we'll take it from there.
Title: Re: NRS v1.7.5
Post by: taggartd on January 25, 2016, 02:36:57 pm
I saw my NRS 1.7.5 crashing. The reason was I had changed database path in nxt.properties. Here is a hint how to fix it.

With the new H2 engine the configuration format is changed:

Use

# Database connection JDBC url to use with the test network, if isTestnet=true.
nxt.dbDir=./nxt_db/nxt

to change the default blockchain path.
Blackyblack1, for common user like me... Actually i have this in nxt.properties:
nxt.dbUrl=jdbc:h2:file:F:/nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE

I must change in:
nxt.dbDir=F:/nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE

??
Thanks
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 02:47:51 pm
Try removing the message and messageIsPrunable parameters. If this works we'll take it from there.

Unfortunatly that did not work. Still the same error message.
I opened up one of my servers with nxt.allowedBotHosts=* (that should be sufficient correct?)

When I browse to the server from the lan the plugin works (http://192.168.1.2:7876)
When I browse to the server from the wan the plugin gives the error message (http://myurl:7876)
When using http://myurl:7876/test and filling in all the parameters in the sendmoney api it works
Title: Re: NRS v1.7.5
Post by: yassin54 on January 25, 2016, 04:00:09 pm
when i install my wallet, i have this: (http://pimg.imagesia.com/fichiers/151/aazq_imagesia-com_151vt_small.png) (http://imagesia.com/aazq_151vt)
Title: Re: NRS v1.7.5
Post by: capodieci on January 25, 2016, 04:12:54 pm
Awesomesauce!
Title: Re: NRS v1.7.5
Post by: crimi on January 25, 2016, 04:14:52 pm
when i install my wallet, i have this: (http://pimg.imagesia.com/fichiers/151/aazq_imagesia-com_151vt_small.png) (http://imagesia.com/aazq_151vt)

probably the run.bat is still running or "in use", so the installer cant delete it? try to close it or delete the old one manually.
Title: Re: NRS v1.7.5
Post by: yassin54 on January 25, 2016, 04:20:24 pm
when i install my wallet, i have this: (http://pimg.imagesia.com/fichiers/151/aazq_imagesia-com_151vt_small.png) (http://imagesia.com/aazq_151vt)

probably the run.bat is still running or "in use", so the installer cant delete it? try to close it or delete the old one manually.
i have all deleted and all it work  :)
Thanks  ;)

edit: I forgot, Thanks Jean-Luc and Riker!!  ;D ;D
Title: Re: NRS v1.7.5
Post by: Riker on January 25, 2016, 06:02:26 pm
Try removing the message and messageIsPrunable parameters. If this works we'll take it from there.

Unfortunatly that did not work. Still the same error message.
I opened up one of my servers with nxt.allowedBotHosts=* (that should be sufficient correct?)

When I browse to the server from the lan the plugin works (http://192.168.1.2:7876)
When I browse to the server from the wan the plugin gives the error message (http://myurl:7876)
When using http://myurl:7876/test and filling in all the parameters in the sendmoney api it works

Please place a breakpoint in nrs.server.js method NRS.verifyTransactionBytes starting at line 507.
Step in the code until you reach a "return false;" statement.
This will tell us which data failed validation. If the problem is not obvious then let me know which line returns the false value.
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 06:59:04 pm
Please place a breakpoint in nrs.server.js method NRS.verifyTransactionBytes starting at line 507.
Step in the code until you reach a "return false;" statement.
This will tell us which data failed validation. If the problem is not obvious then let me know which line returns the false value.

It appears to be here (when sending 1 nxt to one of my accounts)

if (transaction.amountNQT !== data.amountNQT) {
            return false;
        }

Local data:

data: Object
amountNQT: 100000000
deadline: "1440"
feeNQT: "100000000"
message: "Dividend from asset: SPEC(15622038886556621803)"
messageIsPrunable: "true"
publicKey: "88d51b86dfd33c0177e22736bead7c45a3019d714fb6ab01e082185421a74e20"
recipient: "13125632097824428491"
recipientRS: "NXT-NNGD-V8TN-3MZR-DWWBE"
__proto__: Object
pos: undefined
refHash: Array[32]
requestType: "sendMoney"
this: Object
transaction: Object
amountNQT: "100000000"
deadline: "1440"
ecBlockHeight: "624789"
ecBlockId: "3904178616198086227"
feeNQT: "100000000"
flags: 32
publicKey: "88d51b86dfd33c0177e22736bead7c45a3019d714fb6ab01e082185421a74e20"
recipient: "13125632097824428491"
referencedTransactionFullHash: ""
subtype: 0
timestamp: "68453987"
type: 0
version: 1
Title: Re: NRS v1.7.5
Post by: Riker on January 25, 2016, 07:19:46 pm
if (transaction.amountNQT !== data.amountNQT) {
    return false;
}

1. Try to enclose the amountNQT value for the sendRequest call in quotes
2. If this is not it, I need you to use the debugger to tell what's the value of data.amountNQT and the value of transaction.amountNQT
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 07:24:08 pm
1. Try to enclose the amountNQT value for the sendRequest call in quotes
2. If this is not it, I need you to use the debugger to tell what's the value of data.amountNQT and the value of transaction.amountNQT

I enclosed the amountNQT in the debug console and it went further.
Next "false" is on

if (transaction.type !== 0 || transaction.subtype !== 0) {
                    return false;
                }
Title: Re: NRS v1.7.5
Post by: Riker on January 25, 2016, 07:27:10 pm
What are the values of these variables? Anyway suggest you fix the quotes in the code and try again
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 07:49:16 pm
What are the values of these variables? Anyway suggest you fix the quotes in the code and try again

When I add quotes to the amountnqt I get the error (var div = '"' + recalcdiv + '"';)

Incorrect amount&quot;value&quot;100000000.  is not numeric

it's a variable in NRS.sendRequest("sendMoney", {"secretPhrase":<secret>,feeNQT:"100000000",deadline:"1440","recipient":<account>,amountNQT:div,"message":<a message>, "messageIsPrunable": "true"}

How can I add quotes around that without breaking up the nrs.sendrequest?
Title: Re: NRS v1.7.5
Post by: blackyblack1 on January 25, 2016, 07:51:33 pm
What are the values of these variables? Anyway suggest you fix the quotes in the code and try again

When I add quotes to the amountnqt I get the error (var div = '"' + recalcdiv + '"';)

Incorrect amount&quot;value&quot;100000000.  is not numeric

it's a variable in NRS.sendRequest("sendMoney", {"secretPhrase":<secret>,feeNQT:"100000000",deadline:"1440","recipient":<account>,amountNQT:div,"message":<a message>, "messageIsPrunable": "true"}

How can I add quotes around that without breaking up the nrs.sendrequest?
var div = "" + recalcdiv;
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 07:52:02 pm
What are the values of these variables? Anyway suggest you fix the quotes in the code and try again

 if (transaction.type !== 0 || transaction.subtype !== 0) {
                    return false;
                }

transaction: Object
amountNQT: "100000000"
deadline: "1440"
ecBlockHeight: "624844"
ecBlockId: "5500342991802444477"
feeNQT: "100000000"
flags: 32
publicKey: "88d51b86dfd33c0177e22736bead7c45a3019d714fb6ab01e082185421a74e20"
recipient: "13125632097824428491"
referencedTransactionFullHash: ""
subtype: 0
timestamp: "68457075"
type: 0
version: 1
Title: Re: NRS v1.7.5
Post by: blackyblack1 on January 25, 2016, 07:52:27 pm
I saw my NRS 1.7.5 crashing. The reason was I had changed database path in nxt.properties. Here is a hint how to fix it.

With the new H2 engine the configuration format is changed:

Use

# Database connection JDBC url to use with the test network, if isTestnet=true.
nxt.dbDir=./nxt_db/nxt

to change the default blockchain path.
Blackyblack1, for common user like me... Actually i have this in nxt.properties:
nxt.dbUrl=jdbc:h2:file:F:/nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE

I must change in:
nxt.dbDir=F:/nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE

??
Thanks
nxt.dbDir=file:F:/nxt_db/nxt
Title: Re: NRS v1.7.5
Post by: jlauzon on January 25, 2016, 08:06:05 pm
Refresh Search Index" option added to the "Settings" menu. Use it to rebuild
the search index in case you are no longer getting correct search results.


Awesome new feature^^^

Thanks!
Title: Re: NRS v1.7.5
Post by: coinomat on January 25, 2016, 08:56:56 pm
API function getAccountTransactionIds no longer works, right?
what should be used instead?
Title: Re: NRS v1.7.5
Post by: testdruif on January 25, 2016, 09:55:55 pm
What are the values of these variables? Anyway suggest you fix the quotes in the code and try again

Thanks riker!
Your "go to this" and "check that" helped me figure it out :)

a few .toString() here and there and a "messageIsText":"true" in the nrs.sendRequest solved the issue
Title: Re: NRS v1.7.5
Post by: Riker on January 25, 2016, 10:05:24 pm
API function getAccountTransactionIds no longer works, right?
what should be used instead?

Copied from changelogs/changelog.txt line 1205:
"The getAccountTransactions and getAccountTransactionIds APIs have been restricted to always return only the non-phased transactions.
Those APIs have also been deprecated and will be removed in 1.6.
The getBlockchainTransactions API should be used instead, which has the same behavior but returns both phased and non-phased transactions (by default, unless either phasedOnly or
nonPhasedOnly parameters is specified).
Do not simply replace getAccountTransactions with getBlockchainTransactions in your client code without an understanding of how phased transactions work and without being prepared to handle them correctly."
Title: Re: NRS v1.7.5
Post by: jd1959 on January 25, 2016, 11:15:11 pm
Hi guys how many coins do I need to forge?

Have updated to NRS v1.7.5

I'm only asking as I now have message telling me my effective balance is zero. My balance is 9.02041386 plus assets value 4'960.647797

Cheers Jon  ;)

EDIT:  Just read elsewhere that I need 1000+ coins to forge now...Doh

Cheers Jon  :-[
Title: Re: NRS v1.7.5
Post by: Tosch110 on January 26, 2016, 01:14:56 am
Hi guys how many coins do I need to forge?

Have updated to NRS v1.7.5

I'm only asking as I now have message telling me my effective balance is zero. My balance is 9.02041386 plus assets value 4'960.647797

Cheers Jon  ;)

EDIT:  Just read elsewhere that I need 1000+ coins to forge now...Doh

Cheers Jon  :-[

1'000 coins is about 7 Dollars... should not be too expensive to get there ;)
Title: Re: NRS v1.7.5
Post by: TheCoinWizard on January 26, 2016, 01:54:13 am
1'000 coins is about 7 Dollars... should not be too expensive to get there ;)

with 1000 nxt you will have 1000/440000000 chance to forge the next block every time. In other words, you might be lucky and forge 2 blocks a year, or unlucky and forge none, but on average one.
 ;)
Title: Re: NRS v1.7.5
Post by: jd1959 on January 26, 2016, 05:18:40 am
1'000 coins is about 7 Dollars... should not be too expensive to get there ;)

with 1000 nxt you will have 1000/440000000 chance to forge the next block every time. In other words, you might be lucky and forge 2 blocks a year, or unlucky and forge none, but on average one.
 ;)

So it might have taken a while with 9 NXt ?......I might not have that many years left in me ..... lol

Cheers Jon  ;D

Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 26, 2016, 06:41:59 am
Use my raspberry to run NRS1.7.5 mainnet and testnet at same time, ;D ;D ;D

Didn't success run NRS1.7.4 testnet on raspberry,I suspicion because of nxt_test_db folder.

(http://i.imgur.com/FC722IK.png) (http://imgur.com/FC722IK)
Title: Re: NRS v1.7.5
Post by: Riker on January 26, 2016, 09:00:33 am
Use my raspberry to run NRS1.7.5 mainnet and testnet at same time, ;D ;D ;D

Very nice, how much Ram do you have in total and how much do you have available after running both mainnet and testnet ?

Title: Re: NRS v1.7.5
Post by: Tosch110 on January 26, 2016, 10:47:24 am
1'000 coins is about 7 Dollars... should not be too expensive to get there ;)

with 1000 nxt you will have 1000/440000000 chance to forge the next block every time. In other words, you might be lucky and forge 2 blocks a year, or unlucky and forge none, but on average one.
 ;)

So it might have taken a while with 9 NXt ?......I might not have that many years left in me ..... lol

Cheers Jon  ;D

You cannot forge with less than 1,000 NXT, that is the minimum. So 9 NXT not possible to forge with.
Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 26, 2016, 12:27:32 pm
Use my raspberry to run NRS1.7.5 mainnet and testnet at same time, ;D ;D ;D

Very nice, how much Ram do you have in total and how much do you have available after running both mainnet and testnet ?

1G Ram,didn't see how many left,will check tomorrow.
16G SD card,after install NRS1.7.5 mainnet,testnet,LAMP,left about 4G free space.
Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 26, 2016, 01:31:19 pm
How are you running both? Two different 1.7.5 directories, running 2x run.sh? I might try.

That's right,I named 2 folders nxtmainnet and nxttestnet,you need change nxttestnet nxt.properties file set nxt.isTestnet=true,you can also do it on your PC.
Title: Re: NRS v1.7.5
Post by: forkedchain on January 26, 2016, 03:05:46 pm
since when can you not forge with < 1000 NXT?
Title: Re: NRS v1.7.5
Post by: lurker10 on January 26, 2016, 03:08:17 pm
since when can you not forge with < 1000 NXT?

since block 621'000
Title: Re: NRS v1.7.5
Post by: Peter2516 on January 26, 2016, 04:40:29 pm
Just out of curiosity, can you forge with a small account (<1000nxt) if there are big accounts that leased their amounts to the small account?
Title: Re: NRS v1.7.5
Post by: Riker on January 26, 2016, 07:45:52 pm
Just out of curiosity, can you forge with a small account (<1000nxt) if there are big accounts that leased their amounts to the small account?

Yes, the code checks that your effective balance (not your account balance) is larger or equal 1000.
You can check your effective balance in the "Account Details" modal.
Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 27, 2016, 06:38:01 am
Very nice, how much Ram do you have in total and how much do you have available after running both mainnet and testnet ?

Total 925Mb Ram,use 549Mb.
Title: Re: NRS v1.7.5
Post by: crimi on January 27, 2016, 03:51:26 pm
just a small compare before and after 1.7 hardfork.

(http://peerexplorer.com/promotion/nxt_blocks.png)
Title: Re: NRS v1.7.5
Post by: esther on January 27, 2016, 05:34:51 pm
Hello

As usual at each update of NRS I come here to complain about the non-functioning home of the new version ... it become boring ... :(

Well today I come to you because I had so far been no problem of this type. Let me explain I download the 1.7.4 version of the new version and start the installation went well but at the end of the installation without a means of identification window appears .... (see the following joit file) I decided to uninstall to remove all the data vase ../AppData\Roaming\NXT directory and start all over from the beginning with version 1.7.5 and I put Java day and as promised it again . I uninstalled everything ... and I run the run.bat after 10 hours of download ... no change. And there I do not know what to do with me as knowing that the site does not show me http://jnxt.org/nxt/ possession of my assets ...

HELP ME..........


http://imageban.net/show/2016/01/27/daa9144973238371577f674507917e64/gif (http://imageban.net/show/2016/01/27/daa9144973238371577f674507917e64/gif)
Title: Re: NRS v1.7.5
Post by: MrV777 on January 27, 2016, 06:02:51 pm
Hello

As usual at each update of NRS I come here to complain about the non-functioning home of the new version ... it become boring ... :(

Well today I come to you because I had so far been no problem of this type. Let me explain I download the 1.7.4 version of the new version and start the installation went well but at the end of the installation without a means of identification window appears .... (see the following joit file) I decided to uninstall to remove all the data vase ../AppData\Roaming\NXT directory and start all over from the beginning with version 1.7.5 and I put Java day and as promised it again . I uninstalled everything ... and I run the run.bat after 10 hours of download ... no change. And there I do not know what to do with me as knowing that the site does not show me http://jnxt.org/nxt/ possession of my assets ...

HELP ME..........


http://imageban.net/show/2016/01/27/daa9144973238371577f674507917e64/gif (http://imageban.net/show/2016/01/27/daa9144973238371577f674507917e64/gif)

Did you clear your browser's cache, quit your browser, and then try again?
Title: Re: NRS v1.7.5
Post by: esther on January 27, 2016, 06:12:16 pm
Hello

As usual at each update of NRS I come here to complain about the non-functioning home of the new version ... it become boring ... :(

Well today I come to you because I had so far been no problem of this type. Let me explain I download the 1.7.4 version of the new version and start the installation went well but at the end of the installation without a means of identification window appears .... (see the following joit file) I decided to uninstall to remove all the data vase ../AppData\Roaming\NXT directory and start all over from the beginning with version 1.7.5 and I put Java day and as promised it again . I uninstalled everything ... and I run the run.bat after 10 hours of download ... no change. And there I do not know what to do with me as knowing that the site does not show me http://jnxt.org/nxt/ possession of my assets ...

HELP ME..........


http://imageban.net/show/2016/01/27/daa9144973238371577f674507917e64/gif (http://imageban.net/show/2016/01/27/daa9144973238371577f674507917e64/gif)

Did you clear your browser's cache, quit your browser, and then try again?


My savior .............. THANKS it works good I must retelecharge my blockchan .... but it works again .....
Title: Re: NRS v1.7.5
Post by: Nexxie on January 27, 2016, 08:52:26 pm
I can't get the Mac client working...
Anybody running successfully with OSX El Capitan?

Title: Re: NRS v1.7.5
Post by: gvans on January 27, 2016, 10:26:28 pm
SHA does not match for the zip 1.7.5 zip-file ?!!
Kinda worried, installed it already and logged in...

with http://onlinemd5.com I get
74BDFC1EEB01A4FF68B6365DBD3B25C5BF81B71E98D055245959EB6772A706D0

and in op it says
sha256:
4b29107dede6fc3f576d9a56ecd4b1580e6131ed995775647d07b9347df31e54  nxt-client-1.7.5.zip

 ???
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 27, 2016, 10:55:16 pm
Some bizarre bug with onlinemd5.com. Interestingly, it gets the correct sha256 for the 1.7.4 zip, but not for 1.7.5. I tried another online calculator, https://md5file.com/calculator and it gets both of them right.
Title: Re: NRS v1.7.5
Post by: gvans on January 27, 2016, 10:56:19 pm
Phew. Thank you!
Title: Re: NRS v1.7.5
Post by: allwelder on January 28, 2016, 02:11:54 am
Some bizarre bug with onlinemd5.com. Interestingly, it gets the correct sha256 for the 1.7.4 zip, but not for 1.7.5. I tried another online calculator, https://md5file.com/calculator and it gets both of them right.
SHA256 Calculators:
http://hash.online-convert.com/sha256-generator
https://md5file.com/calculator
http://www.xorbin.com/tools/sha256-hash-calculator
http://www.convertstring.com/Hash/SHA256
http://www.freeformatter.com/sha256-generator.html
http://passwordsgenerator.net/sha256-hash-generator/
http://www.fileformat.info/tool/hash.htm
http://onlinemd5.com/

http://nxtchina.org/forum.php?mod=viewthread&tid=1359&page=1&extra=#pid2677
 :)
Title: Re: NRS v1.7.5
Post by: forkedchain on January 28, 2016, 02:37:39 am
just a small compare before and after 1.7 hardfork.

(http://peerexplorer.com/promotion/nxt_blocks.png)

is this a direct result of not allowing accounts < 1000 NXT to forge?  I guess this was the main reason for that change?  through what mechanism did you do this?  i recall the formula of how it is determined when an account will be eligible to forge, but I cant think of how you did it.  but you guys are the smart ones - so how did you do it?  do we have that drastically different of a HIT calc now?
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 28, 2016, 09:28:53 am
Not really, it is the base target adjustment algorithm that was improved. See BlockImpl.calculateBaseTarget().
Title: Re: NRS v1.7.5
Post by: crimi on January 28, 2016, 09:44:33 am
Not really, it is the base target adjustment algorithm that was improved. See BlockImpl.calculateBaseTarget().

this
Title: Re: NRS v1.7.5
Post by: Riker on January 28, 2016, 10:04:45 am
Any ideas about the 100 minutes+ block on Jan 27th.
Was it just freak accident, technical problem, measurement problem ?
What was the block number ?
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 28, 2016, 10:36:36 am
Those plots are of unconfirmed transaction numbers, not block times. There is some correlation because when there is a long block, more unconfirmed transactions accumulate. But another reason for a peak would be somebody doing a dividend payment sending hundreds of transactions at once, probably what happened.
Title: Re: NRS v1.7.5
Post by: crimi on January 28, 2016, 10:37:31 am
Any ideas about the 100 minutes+ block on Jan 27th.
Was it just freak accident, technical problem, measurement problem ?
What was the block number ?

Normal almost every day, its just the measurement of unconfirmed transactions.
If someone sends for example 100 transactions like today yesterday (https://nxtportal.org/blocks/17516509000674740956) dividents, they are ending up in the unconfirmed transaction pool and you will see a spike as you said.
Whats more important how fast the curve went down afterwards. Also considering that 255 transactions per block is the max, if someone sends 500 dividents out...
Title: Re: NRS v1.7.5
Post by: rriky92 on January 28, 2016, 08:12:47 pm
After installing 1.7.5 from zero with the .dmg file i can't visit localhost:7876 cause i get

Quote
HTTP ERROR: 404

Problem accessing /index.html. Reason:

    Not Found
Powered by Jetty:// 9.3.6.v20151106
Title: Re: NRS v1.7.5
Post by: TheCoinWizard on January 28, 2016, 09:51:09 pm
what do you mean with from zero?
If you mean from nxt client 0.x than...

Updated Bouncy Castle library to version 1.53, Jetty to version 9.3.5, IzPack
installer to 5.0.5, and weupnp to 0.1.4. Make sure to delete the old lib
folder if unpacking over a previous installation.


Otherwise, could you share the content of your log please.
Title: Re: NRS v1.7.5
Post by: DrCharles on January 28, 2016, 09:52:05 pm
I keep getting the message "FINE: didn't accept any blocks, pushing back my previous blocks" and the blockchain is not downloading any further. What can I do to get the rest of the blockchain downloaded?

2016-01-28 16:51:58 FINE: Didn't accept any blocks, pushing back my previous blocks
2016-01-28 16:52:02 FINE: Will process a fork of 274 blocks, mine is 1
2016-01-28 16:52:02 FINE: Rollback from block 1031888723685398168 at height 621002 to 14673195407797974997 at 621001
2016-01-28 16:52:02 FINE: Blacklisting 62.75.159.113 because of: nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed, block 12110544739638067954 {"totalFeeNQT":0,"previousBlockHash":"d5f7b0417ba9a1cb3857ec03aa8cbc443e1b827d7f3dde3722c9b9f9bbe81b73","payloadLength":0,"previousBlock":"14673195407797974997","totalAmountNQT":0,"generationSignature":"a1dc25a6e502da35c44deb3972f6f3f936c9d55794a937e94fb9ec6277d2aef1","generatorPublicKey":"f3831afb0cfbaca8e9fca6523d0b23d14aa2e6f9ac1726f12c30acd4d622bb0a","payloadHash":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","blockSignature":"cd34a89efa2adaac392f46d8bba1745ba522c51b295f116ae3ab12444da0b20d3990792c82e9edfd47af1c0e283117252c0796fa4b26001ec292b52bd43882fc","transactions":[],"version":3,"timestamp":68222030}
nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed, block 12110544739638067954 {"totalFeeNQT":0,"previousBlockHash":"d5f7b0417ba9a1cb3857ec03aa8cbc443e1b827d7f3dde3722c9b9f9bbe81b73","payloadLength":0,"previousBlock":"14673195407797974997","totalAmountNQT":0,"generationSignature":"a1dc25a6e502da35c44deb3972f6f3f936c9d55794a937e94fb9ec6277d2aef1","generatorPublicKey":"f3831afb0cfbaca8e9fca6523d0b23d14aa2e6f9ac1726f12c30acd4d622bb0a","payloadHash":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","blockSignature":"cd34a89efa2adaac392f46d8bba1745ba522c51b295f116ae3ab12444da0b20d3990792c82e9edfd47af1c0e283117252c0796fa4b26001ec292b52bd43882fc","transactions":[],"version":3,"timestamp":68222030}
   at nxt.BlockchainProcessorImpl.validate(BlockchainProcessorImpl.java:1422)
   at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:1327)
   at nxt.BlockchainProcessorImpl.access$1100(BlockchainProcessorImpl.java:64)
   at nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:585)
   at nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:566)
   at nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:267)
   at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:180)
   at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
   at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
2016-01-28 16:52:02 FINE: Didn't accept any blocks, pushing back my previous blocks
Title: Re: NRS v1.7.5
Post by: Riker on January 28, 2016, 09:59:31 pm
I keep getting the message "FINE: didn't accept any blocks, pushing back my previous blocks" and the blockchain is not downloading any further. What can I do to get the rest of the blockchain downloaded?

Use the test page http://localhost:7876/test to invoke the popOff API with block height 621000. This should get you out of the fork in most cases.
Title: Re: NRS v1.7.5
Post by: DrCharles on January 28, 2016, 10:05:06 pm
I keep getting the message "FINE: didn't accept any blocks, pushing back my previous blocks" and the blockchain is not downloading any further. What can I do to get the rest of the blockchain downloaded?

Use the test page http://localhost:7876/test to invoke the popOff API with block height 621000. This should get you out of the fork in most cases.

Perfect.. it looks like the blockchain has started to progress again... you saved the day haha

I was starting to panic when I saw "Blacklisted" popping up a bunch of times.
Title: Re: NRS v1.7.5
Post by: Riker on January 28, 2016, 10:07:58 pm
After installing 1.7.5 from zero with the .dmg file i can't visit localhost:7876 cause i get

Quote
HTTP ERROR: 404

Problem accessing /index.html. Reason:

    Not Found
Powered by Jetty:// 9.3.6.v20151106

I can reproduce this too. Either something new with OS/X El Capitan or just something I messed up. Will try to fix this for 1.7.6.
Title: Re: NRS v1.7.5
Post by: allwelder on January 28, 2016, 11:07:50 pm
Those plots are of unconfirmed transaction numbers, not block times. There is some correlation because when there is a long block, more unconfirmed transactions accumulate. But another reason for a peak would be somebody doing a dividend payment sending hundreds of transactions at once, probably what happened.
What will happen if submit 255 tx at the same time? More unconfirmed tx?
Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 29, 2016, 04:55:36 am
My raspberry just stopped,don't know why,and here is the error message.In the mean time,NRS testnet run normal.After restart,mainnet back to normal again.

Quote
2016-01-29 11:24:31 FINE: Connect: announced address home.kaerner.net now points to 91.7.34.52, replacing peer 91.7.37.186
2016-01-29 11:26:20 FINE: Blacklisting 2.85.10.30 because of: java.net.UnknownHostException: pakisnxt.no-ip.org: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 94.226.14.92 because of: java.net.UnknownHostException: nxt1.testdruif.be: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 92.222.65.159 because of: java.net.UnknownHostException: nxt.scryptmh.eu: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 23.89.5.60 because of: java.net.UnknownHostException: ct.flipflop.mooo.com: unknown error
killed

Maybe JL or Riker interested.
Title: Re: NRS v1.7.5
Post by: allwelder on January 29, 2016, 05:34:30 am
With account control, Let say I set my 'A' account control ,and adding my 'B' account as the only one whitelist to approve tx from 'A'.
How to set Minimum and maximum phasing durations?

e.g,I set maximum phasing durations: 1440 blocks.
This means 'B' account need to approve the transaction of A account within 1440 blocks?
If not approved within 1440 blocks ,the sending NXT will be returned back to A account?

Did I understand correctly?
Thanks.
Title: Re: NRS v1.7.5
Post by: Riker on January 29, 2016, 06:43:55 am
With account control, Let say I set my 'A' account control ,and adding my 'B' account as the only one whitelist to approve tx from 'A'.
How to set Minimum and maximum phasing durations?

e.g,I set maximum phasing durations: 1440 blocks.
This means 'B' account need to approve the transaction of A account within 1440 blocks?
If not approved within 1440 blocks ,the sending NXT will be returned back to A account?

Did I understand correctly?
Thanks.

According to the tooltip in the set mandatory approval modal:
"Restricts the phasing period of the transactions issued by the account. Useful in case the controlled account is compromised. The maximum duration determines for how long an attacker will be able to lock the account funds before the controlling entities are able to rescue them to a new account. The minimum duration, together with the Maximum Pending Fees, determines at what rate an attacker will be able to burn through fees the NXT owned by the controlled account"

For these parameters the value 0 means "do not validate", maxDuration has to be less than 14*1440 i.e. 14 days and minDuration has to be smaller than maxDuration.
The values 1,2,3 are not allowed probably to prevent short range reorgs problems.

Like all phased transactions, if not approved during this block range the transaction is not executed. It will stay in the blockchain forever but won't affect any account balance.

Let's say that an account under your control is compromised and the attacker tries to move the funds to his account. You do not approve this transaction, so this transaction stays an approved and locks the funds until the maxDuration expires. Now the rightful owner of the account can issue another transaction to rescue the funds that you can approve.
Title: Re: NRS v1.7.5
Post by: allwelder on January 29, 2016, 07:31:47 am
Thanks for answering.really a good tool for security and anti-comprised.
Tested,worked well.

But seems set the maxDuration bigger than 10077 is meaningless,because the phased transaction will be rejected if not approved within default max 10077 blocks.
Title: Re: NRS v1.7.5
Post by: blackyblack1 on January 29, 2016, 09:46:01 am
Do we have any way to have a multilanguage support for NRS plugins?
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 29, 2016, 10:51:06 am
My raspberry just stopped,don't know why,and here is the error message.In the mean time,NRS testnet run normal.After restart,mainnet back to normal again.

Quote
2016-01-29 11:24:31 FINE: Connect: announced address home.kaerner.net now points to 91.7.34.52, replacing peer 91.7.37.186
2016-01-29 11:26:20 FINE: Blacklisting 2.85.10.30 because of: java.net.UnknownHostException: pakisnxt.no-ip.org: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 94.226.14.92 because of: java.net.UnknownHostException: nxt1.testdruif.be: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 92.222.65.159 because of: java.net.UnknownHostException: nxt.scryptmh.eu: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 23.89.5.60 because of: java.net.UnknownHostException: ct.flipflop.mooo.com: unknown error
killed

Maybe JL or Riker interested.

Probably the OS got too low on memory and had to kill the java process. Or, you started it without using nohup or screen, and it got killed when you disconnected.
The UnknownHostExceptions indicate some temporary networking or DNS problem.
 
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 29, 2016, 10:53:01 am
What will happen if submit 255 tx at the same time? More unconfirmed tx?
They just wait as unconfirmed and get included in the next blocks, by default in order of highest fee/size ratio.
Title: Re: NRS v1.7.5
Post by: nxtapple on January 29, 2016, 01:34:48 pm
I just downloaded the blockchain (fresh install) but once it finished, it just says "Downloading blockchain...". This disappears for a while but if I log out and in immediately, it happens again for about 30 seconds. Also transactions don't go through, even though a new block has been found.

Any help?  ;D
Title: Re: NRS v1.7.5
Post by: Riker on January 29, 2016, 01:38:18 pm
I just downloaded the blockchain (fresh install) but once it finished, it just says "Downloading blockchain...". This disappears for a while but if I log out and in immediately, it happens again for about 30 seconds. Also transactions don't go through, even though a new block has been found.

Any help?  ;D

We need to see your nxt.log
Title: Re: NRS v1.7.5
Post by: coretechs on January 29, 2016, 06:38:30 pm
Oracle vs OpenJDK - any reason prefer one over the other for running a Nxt node?
Title: Re: NRS v1.7.5
Post by: verymuchso on January 29, 2016, 07:27:57 pm
Oracle vs OpenJDK - any reason prefer one over the other for running a Nxt node?

No difference, but i'd pick oracle.
Built by the same people but the version released under oracle label has had more testing hours and basically has more money spend on it.
Same goes for windows java oracle vs linux java oracle, same engineers but the finishing of the first one just has a lot more resources thrown against it, thats why it performs much better in general.
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 30, 2016, 12:45:52 am
Oracle vs OpenJDK - any reason prefer one over the other for running a Nxt node?
While at that, any experience running Nxt, or in general doing java development on FreeBSD? I am trying it now, and so far it seems to work, using OpenJDK. Still need to make sure I can get running all desktop applications I am used to, or find good replacements. But IntelliJ and SmartGit work.
Title: Re: NRS v1.7.5
Post by: qq2536007339 on January 30, 2016, 02:45:34 am
My raspberry just stopped,don't know why,and here is the error message.In the mean time,NRS testnet run normal.After restart,mainnet back to normal again.

Quote
2016-01-29 11:24:31 FINE: Connect: announced address home.kaerner.net now points to 91.7.34.52, replacing peer 91.7.37.186
2016-01-29 11:26:20 FINE: Blacklisting 2.85.10.30 because of: java.net.UnknownHostException: pakisnxt.no-ip.org: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 94.226.14.92 because of: java.net.UnknownHostException: nxt1.testdruif.be: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 92.222.65.159 because of: java.net.UnknownHostException: nxt.scryptmh.eu: unknown error
2016-01-29 11:26:40 FINE: Blacklisting 23.89.5.60 because of: java.net.UnknownHostException: ct.flipflop.mooo.com: unknown error
killed

Maybe JL or Riker interested.

Probably the OS got too low on memory and had to kill the java process. Or, you started it without using nohup or screen, and it got killed when you disconnected.
The UnknownHostExceptions indicate some temporary networking or DNS problem.

You are right,I didn't started with nohup or screen,I want see NRS what's going on,didn't know it will got killed when disconnected.
Title: Re: NRS v1.7.5
Post by: coretechs on January 30, 2016, 04:41:58 pm
Oracle vs OpenJDK - any reason prefer one over the other for running a Nxt node?

No difference, but i'd pick oracle.
Built by the same people but the version released under oracle label has had more testing hours and basically has more money spend on it.
Same goes for windows java oracle vs linux java oracle, same engineers but the finishing of the first one just has a lot more resources thrown against it, thats why it performs much better in general.


I found an interesting difference between the two while playing around with certs.  OpenJDK appears to include the "unlimited strength" jurisdiction policies by default whereas Oracle Java ships with "strong" which limits the strength of the SSL/TLS ciphers.

For a default installation -
Oracle Java connection: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, 128 bit keys, TLS 1.2
OpenJDK connection: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, 256 bit keys, TLS 1.2

If you are using Oracle Java and you want to enable "unlimited strength" encryption you need to download and install additional policy files that overwrite the defaults:
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

Copy the policy files to $JAVA_HOME/jre/lib/security/ and restart Nxt and your connection should now use stronger encryption w/256 bit keys.
Title: Re: NRS v1.7.5
Post by: verymuchso on January 30, 2016, 05:07:59 pm
I found an interesting difference between the two while playing around with certs.  OpenJDK appears to include the "unlimited strength" jurisdiction policies by default whereas Oracle Java ships with "strong" which limits the strength of the SSL/TLS ciphers.

This has to do with a US law that says >256? bit encryption is considered some sort of a weapon and is bound to export restrictions.
I had no idea this did not apply to OpenJDK.

Good catch, thanks for sharing!
Title: Re: NRS v1.7.5
Post by: coretechs on January 31, 2016, 06:46:58 am
Oracle vs OpenJDK - any reason prefer one over the other for running a Nxt node?

No difference, but i'd pick oracle.
Built by the same people but the version released under oracle label has had more testing hours and basically has more money spend on it.
Same goes for windows java oracle vs linux java oracle, same engineers but the finishing of the first one just has a lot more resources thrown against it, thats why it performs much better in general.


I found an interesting difference between the two while playing around with certs.  OpenJDK appears to include the "unlimited strength" jurisdiction policies by default whereas Oracle Java ships with "strong" which limits the strength of the SSL/TLS ciphers.

For a default installation -
Oracle Java connection: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, 128 bit keys, TLS 1.2
OpenJDK connection: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, 256 bit keys, TLS 1.2

If you are using Oracle Java and you want to enable "unlimited strength" encryption you need to download and install additional policy files that overwrite the defaults:
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

Copy the policy files to $JAVA_HOME/jre/lib/security/ and restart Nxt and your connection should now use stronger encryption w/256 bit keys.

I did a lot of testing on a Raspberry Pi 2 today and found that the Oracle Java seems to perform *significantly* faster than OpenJDK.  Average initialization for the Nxt server is 20-25 seconds for Oracle vs. 110-150 seconds for OpenJDK.  Unless there is something in the configuration that I'm overlooking, I'll probably update my Raspberry Pi install guide shortly to recommend using Oracle Java.

Also, most modern browsers prioritize AES-GCM (https://en.wikipedia.org/wiki/Galois/Counter_Mode) over AES-CBC.  Chrome reports TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA as "strong" but also "obsolete".  The default Sun/Java crypto providers prioritize AES-CBC (https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html) but if you add the following to API.java you can configure jetty to use AES-GCM:

Code: [Select]
sslContextFactory.setIncludeCipherSuites("TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256");

This way you use either an EC or RSA self-signed cert and get the performance of the modern cipher suites.  On a Raspberry Pi every little bit helps, just remember that older browsers and some mobile devices may not support them.
Title: Re: NRS v1.7.5
Post by: Jean-Luc on January 31, 2016, 11:23:47 am
I will make the list of enabled cipher suites for the API SSL a configurable property. However, when using Oracle Java unless the unlimited strength policy files are installed, 256-bit keys will not be available. Even if BouncyCastle is set as default security provider.

This affects only the security of the API SSL connections. For our message encryption and shuffling encryption, we use the BouncyCastle lightweight API directly, with 256-bit AES keys, regardless of what the JDK supports.

Title: Re: NRS v1.7.5
Post by: DrCharles on January 31, 2016, 08:22:26 pm
How can I make a dividend payment to asset holders? When I attempt to send dividend, I get a message that just says "Deadline not specific". Please advise.

Log: 2016-01-31 15:22:19 FINE: Blacklisting 167.114.113.25 version 1.6.2
2016-01-31 15:22:19 FINE: Peer 91.235.72.49 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.7.5","platform":"PC","shareAddress":true}, disconnecting
2016-01-31 15:22:49 FINE: Announced address nxt.bemining.net does not resolve to 158.69.194.254
2016-01-31 15:22:49 FINE: Connect: new announced address for 158.69.194.254 not accepted
2016-01-31 15:23:55 FINE: Will process a fork of 3 blocks, mine is 1
2016-01-31 15:23:55 FINE: Rollback from block 712663975168564399 at height 633448 to 15763699747723305073 at 633447
2016-01-31 15:23:55 FINE: Switched to peer's fork
2016-01-31 15:23:55 FINE: Peer 87.139.122.48 version 1.7.5 returned error: {"error":"Blockchain download in progress"}, request was: {"protocol":1,"requestType":"getCumulativeDifficulty"}, disconnecting
2016-01-31 15:24:58 FINE: Database connection pool current size: 4
Title: Re: NRS v1.7.5
Post by: rriky92 on February 01, 2016, 10:15:20 am
what do you mean with from zero?
If you mean from nxt client 0.x than...

Updated Bouncy Castle library to version 1.53, Jetty to version 9.3.5, IzPack
installer to 5.0.5, and weupnp to 0.1.4. Make sure to delete the old lib
folder if unpacking over a previous installation.


Otherwise, could you share the content of your log please.

I mean that i deleted all the old nxt version, i don't have log file probably this is the cause:
Quote
Initializing Nxt server version 1.7.5
isHeadless=false
Loading nxt-default.properties from classpath
Loading logging-default.properties from classpath
Can't load log handler "java.util.logging.FileHandler"
java.nio.file.NoSuchFileException: logs/nxt.log.lck
java.nio.file.NoSuchFileException: logs/nxt.log.lck

But then my terminal says:
Quote
2016-02-01 11:08:06 INFO: Started API server at 127.0.0.1:7876
2016-02-01 11:08:15 FINE: There are no UPnP gateway devices
2016-02-01 11:08:15 INFO: Started peer networking server at 0.0.0.0:7874
2016-02-01 11:08:15 FINE: Starting 9 background jobs
2016-02-01 11:08:15 FINE: Starting 2 delayed tasks
2016-02-01 11:08:15 FINE: Known peers: 244
2016-02-01 11:08:15 INFO: Initialization took 28 seconds
2016-02-01 11:08:15 INFO: Nxt server 1.7.5 started successfully.
2016-02-01 11:08:15 INFO: Copyright © 2013-2016 The Nxt Core Developers.
2016-02-01 11:08:15 INFO: Distributed under GPLv2, with ABSOLUTELY NO WARRANTY.
2016-02-01 11:08:15 INFO: Client UI is at http://localhost:7876/index.html
2016-02-01 11:08:36 FINE: Database connection pool current size: 3
Title: Re: NRS v1.7.5
Post by: qq2536007339 on February 02, 2016, 02:08:39 am
How can I make a dividend payment to asset holders? When I attempt to send dividend, I get a message that just says "Deadline not specific". Please advise.

You use API to do dividend? If so you should fill deadline with 1440.Or simply use UI to do dividend.
Title: Re: NRS v1.7.5
Post by: MrV777 on February 04, 2016, 08:15:45 pm
Hello,

On line 335 of nrs.server.js, I see that a file is required for uploadTaggedData through the client.  I'm not sure if I'm missing another line of code, but why is this required even when the uploadedData has isText set to true.
Basically, I'm trying to use uploadTaggedData for my Forum plugin, but it gets an error without a file.  I suppose I could look at not using uploadTaggedData, but now I'm wondering why there is this requirement.

Thanks and great work with the 1.7 branch!
Title: Re: NRS v1.7.5
Post by: qq2536007339 on February 06, 2016, 11:10:26 am
Can we increased maximum leasing period again? I think is too short even for 65535 blocks now.

Right now leasing is pointless for those balance less than 1000NXT.Because you need leasing 8 times/year,this cost at least 8 NXT,but you can only earn about 5.5NXT/year even you pay zero cost for forging.Many people criticism POS system is make the rich get richer,but if we can increase leasing period,we can counter that criticism better.And make repeat leasing less frequently.

I found one disadvantage here (https://nxtforum.org/index.php?topic=85.msg200850#msg200850),I'm not sure if this can be fix by set a hard cap.

Maybe there is more disadvantage I'm not aware,hope someone can explain to me,thanks in advance.
Title: Re: NRS v1.7.5
Post by: lurker10 on February 06, 2016, 11:47:49 am
Can we increased maximum leasing period again? I think is too short even for 65535 blocks now.

Right now leasing is pointless for those balance less than 1000NXT.Because you need leasing 8 times/year,this cost at least 8 NXT,but you can only earn about 5.5NXT/year even you pay zero cost for forging.Many people criticism POS system is make the rich get richer,but if we can increase leasing period,we can counter that criticism better.And make repeat leasing less frequently.

I found one disadvantage here (https://nxtforum.org/index.php?topic=85.msg200850#msg200850),I'm not sure if this can be fix by set a hard cap.

Maybe there is more disadvantage I'm not aware,hope someone can explain to me,thanks in advance.

You can't increase the maximum leasing period without a hard fork, can you? My understanding is the next hard fork can happen no sooner than end of 2016 according to the roadmap plans.
Title: Re: NRS v1.7.5
Post by: qq2536007339 on February 06, 2016, 01:04:37 pm
Can we increased maximum leasing period again? I think is too short even for 65535 blocks now.

Right now leasing is pointless for those balance less than 1000NXT.Because you need leasing 8 times/year,this cost at least 8 NXT,but you can only earn about 5.5NXT/year even you pay zero cost for forging.Many people criticism POS system is make the rich get richer,but if we can increase leasing period,we can counter that criticism better.And make repeat leasing less frequently.

I found one disadvantage here (https://nxtforum.org/index.php?topic=85.msg200850#msg200850),I'm not sure if this can be fix by set a hard cap.

Maybe there is more disadvantage I'm not aware,hope someone can explain to me,thanks in advance.

You can't increase the maximum leasing period without a hard fork, can you? My understanding is the next hard fork can happen no sooner than end of 2016 according to the roadmap plans.

Next hard fork is not a problem if dev agree to increase.
Title: Re: NRS v1.7.5
Post by: Brangdon on February 06, 2016, 01:05:20 pm
Right now leasing is pointless for those balance less than 1000NXT.Because you need leasing 8 times/year,this cost at least 8 NXT,but you can only earn about 5.5NXT/year even you pay zero cost for forging.
There will always be a balance below which leasing is not economical. Does it matter whether it is 1000 NXT or 2000 NXT? Both are small amounts in real terms. The difference between them is currently less than $10.
Title: Re: NRS v1.7.5
Post by: qq2536007339 on February 06, 2016, 01:46:59 pm
There will always be a balance below which leasing is not economical. Does it matter whether it is 1000 NXT or 2000 NXT? Both are small amounts in real terms. The difference between them is currently less than $10.

I know,but even difference is small,I think it's always better if minimum balance smaller.And less leasing times is another advantage.
Title: Re: NRS v1.7.5
Post by: altsheets on February 06, 2016, 06:10:01 pm
After an "unable to ... Lucene ... blabla" error, I deleted the nxt_db\nxt folder, and had to manually create a new one.

Then rescanning took about 10 hours (what is a recipe to do that in RAMDISK, next time? Thanks.)

Now:
Code: [Select]
Initializing Nxt server version 1.7.5
[...]
2016-02-06 18:58:19 FINE: Database jdbc url set to jdbc:h2:C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db\nxt;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE;CACHE_SIZE=262144 username sa
[...]
2016-02-06 18:58:27 INFO: Client UI is at http://localhost:7876/index.html

So the client is starting up just fine.

But

Code: [Select]
dir C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db\nxt
the directory is empty.
Title: Re: NRS v1.7.5
Post by: blackyblack1 on February 06, 2016, 06:47:05 pm
Bug report.
Register alias modal. URI input field has NXT account mask set.

How to reproduce:
Click "Register Alias" button, choose "Account" type, choose "URI" type, click URI field.

How to workaround:
Choose "Other" type, delete all text in "Data" input field, choose "URI" type.
Title: Re: NRS v1.7.5
Post by: thezman007 on February 06, 2016, 07:03:32 pm
Can anyone tell me why oh why I need to download the ENTIRE blockchain every time I upgrade. I put off upgrading for this reason... Am I doing it wrong?
Title: Re: NRS v1.7.5
Post by: VanBreuk on February 06, 2016, 07:10:34 pm
Can anyone tell me why oh why I need to download the ENTIRE blockchain every time I upgrade. I put off upgrading for this reason... Am I doing it wrong?

You can save your nxt/nxt_db folder (where blockchain data is) from previous software version, and copy it to the newly unzipped release folder. The new version will do a db rescan and upgrade the blockchain as needed. This can take a bit of time but way less than downloading the entire blockchain from scratch.

Another option, instead of rescanning your previous version blockchain folder, is to download a nearly up-to-date blockchain from a trusted provider like http://peerexplorer.com (find the link in the page bottom). This will get you a current version blockchain updated somewhere in the last 24 hours, and once you add it to your new nxt folder the missing blocks will just take a few minutes to download.
Title: Re: NRS v1.7.5
Post by: thezman007 on February 06, 2016, 07:21:35 pm
Can anyone tell me why oh why I need to download the ENTIRE blockchain every time I upgrade. I put off upgrading for this reason... Am I doing it wrong?

You can save your nxt/nxt_db folder (where blockchain data is) from previous software version, and copy it to the newly unzipped release folder. The new version will do a db rescan and upgrade the blockchain as needed. This can take a bit of time but way less than downloading the entire blockchain from scratch.

Another option, instead of rescanning your previous version blockchain folder, is to download a nearly up-to-date blockchain from a trusted provider like "ican't post links" (find the link in the page bottom). This will get you a current version blockchain updated somewhere in the last 24 hours, and once you add it to your new nxt folder the missing blocks will just take a few minutes to download.

Thank you. I knew there was a better way! I just wasn't sure where to save the blockchain data and place it in the new client files. Is that something that will ever happen automagically?
Title: Re: NRS v1.7.5
Post by: farl4bit on February 11, 2016, 12:13:19 pm
I have some problems with the Mac version https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.5.dmg.

Why is the Nxt installer placed in the application folder? On a Mac, that is not the place to put these files. In the applications folder are applications only. It's not necessary to have it moved as is suggested in the DMG, because in the installation progress people have to choose the destination again. (not userfriendly)

(http://i67.tinypic.com/1zl3pfo.jpg)

When I try to choose a destination folder in the folder applications, nothing happens, for example the Applications folder from the administrator of my Mac, "/Applications/" keeps forcing to be the root for the installation. So I settle with installing it in the Applications folder on my personal account on my Mac, but I prefer to have all apps in the Administrator (main) folder for Applications.

Then after finishing the installation I get a nasty surprise. There isn't a app created, but the old-fashion NRS-folder with files where I need to use terminal. I never do that, because I dislike terminal and just want to click on the app and start playing with Nxt. Wesley and Poofknuckle have always been delivering a stand-alone client. This one is not. The problem is that new people will not know where to start. There is no manual, so I guess the majority will stop there. Can't we have a stand-alone again... please?

(http://i67.tinypic.com/16hnlnb.jpg)

When I try to use the Uninstaller I get a malware alert. Can I trust it? And why did you made a Uninstaller? Can I not just delete the folder? (Mac normally doesn't have uninstallers). This gives me doubts again about the software.

(http://i65.tinypic.com/xxbbn.jpg)

Hope to see a reply from you Riker. Thanks  :)

Title: Re: NRS v1.7.5
Post by: Riker on February 11, 2016, 07:50:14 pm
Regarding the Mac installer. The current installer is a compromise between the tools Java provides and the user experience Mac users expect.

Please consider that the current installer has the following important advantages:
1. Packaged automatically from the development environment and is therefore fully reproducible by anyone which has a Mac directly from the source code
2. Digitally signed using the "NXT Stitchting" digital signature which allows it to be downloaded to any Mac without receiving scary installation warnings or having to add specific security exceptions
3. Bundles a Java distribution, therefore it saves users the joy of installing Oracle Java on their Mac

Currently we use the IzPack tool to generate a cross platform installer which is almost the same on Windows, Linux and Mac. But since this is a cross platform tool, the installed NXT package is incompatible with the layout of a Mac application and therefore has to rely on the same terminal commands used by the Linux distribution.
The installer package itself is packaged using the javapackager tool which converts it to a standard Mac DMG file.
This creates the strange effect that the installer itself is an application (NXT-installer) but the actual installed package is not.

Can we do better ? Perhaps
Is it difficult ? Very

Regarding the desktop wallet. I recently experimented with a Javafx tool which wraps a browser component using a Java container and can therefore open the wallet automatically like the Wesley installer. It almost works but has some limitations which makes it difficult to use. Still haven't gave up on this.

Regarding the rest of the problems,
Uninstaller - I'll look into the uninstaller issue but there is no reason not to just delete the NXT folder so there is really no need to use it.
Applications folder - Do you really have to install the nxt package itself to the /Applications folder ? Can't you just choose another package in the installer dialog ?
Double click on run.command starts an unusable wallet, this is a known issue that I intend to fix.
Title: Re: NRS v1.7.5
Post by: Nexxie on February 12, 2016, 06:10:38 pm
I have some problems with the Mac version https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.5.dmg.

Why is the Nxt installer placed in the application folder? On a Mac, that is not the place to put these files. In the applications folder are applications only. It's not necessary to have it moved as is suggested in the DMG, because in the installation progress people have to choose the destination again. (not userfriendly)

(http://i67.tinypic.com/1zl3pfo.jpg)

When I try to choose a destination folder in the folder applications, nothing happens, for example the Applications folder from the administrator of my Mac, "/Applications/" keeps forcing to be the root for the installation. So I settle with installing it in the Applications folder on my personal account on my Mac, but I prefer to have all apps in the Administrator (main) folder for Applications.

Then after finishing the installation I get a nasty surprise. There isn't a app created, but the old-fashion NRS-folder with files where I need to use terminal. I never do that, because I dislike terminal and just want to click on the app and start playing with Nxt. Wesley and Poofknuckle have always been delivering a stand-alone client. This one is not. The problem is that new people will not know where to start. There is no manual, so I guess the majority will stop there. Can't we have a stand-alone again... please?

(http://i67.tinypic.com/16hnlnb.jpg)

When I try to use the Uninstaller I get a malware alert. Can I trust it? And why did you made a Uninstaller? Can I not just delete the folder? (Mac normally doesn't have uninstallers). This gives me doubts again about the software.

(http://i65.tinypic.com/xxbbn.jpg)

Hope to see a reply from you Riker. Thanks  :)

Nice to see that I am not the only one with the problem ..
How does one start the client after installing the nxt installer ?

thanks
Title: Re: NRS v1.7.5
Post by: romanix on February 12, 2016, 07:15:37 pm

NRS 1.7.5 is again a nice release!
Congratulation! I hope developers keep on the good work. The NRS GUI is so nice and clean.
The client doesn't use too much computer resources and everything* works just fine.
(expect that MGW asset 10524562908394749924 corrupted the GUI menu on the left side)

What I'm wondering is whether it's possible to send NXT or messages to aliases. I couldn't figure out how to do it.
Also, I can't add existing aliases to contacts. Or can I ?
Title: Re: NRS v1.7.5
Post by: Nexxie on February 13, 2016, 06:25:57 am
I have some problems with the Mac version https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-installer-1.7.5.dmg.

Why is the Nxt installer placed in the application folder? On a Mac, that is not the place to put these files. In the applications folder are applications only. It's not necessary to have it moved as is suggested in the DMG, because in the installation progress people have to choose the destination again. (not userfriendly)

(http://i67.tinypic.com/1zl3pfo.jpg)

When I try to choose a destination folder in the folder applications, nothing happens, for example the Applications folder from the administrator of my Mac, "/Applications/" keeps forcing to be the root for the installation. So I settle with installing it in the Applications folder on my personal account on my Mac, but I prefer to have all apps in the Administrator (main) folder for Applications.

Then after finishing the installation I get a nasty surprise. There isn't a app created, but the old-fashion NRS-folder with files where I need to use terminal. I never do that, because I dislike terminal and just want to click on the app and start playing with Nxt. Wesley and Poofknuckle have always been delivering a stand-alone client. This one is not. The problem is that new people will not know where to start. There is no manual, so I guess the majority will stop there. Can't we have a stand-alone again... please?

(http://i67.tinypic.com/16hnlnb.jpg)

When I try to use the Uninstaller I get a malware alert. Can I trust it? And why did you made a Uninstaller? Can I not just delete the folder? (Mac normally doesn't have uninstallers). This gives me doubts again about the software.

(http://i65.tinypic.com/xxbbn.jpg)

Hope to see a reply from you Riker. Thanks  :)

Nice to see that I am not the only one with the problem ..
How does one start the client after installing the nxt installer ?

thanks

This is the server log:
2016-02-13 07:23:37 INFO: nxt.includeExpiredPrunable = "true"
2016-02-13 07:23:37 INFO: nxt.correctInvalidFees = "false"
2016-02-13 07:23:37 INFO: nxt.statementLogThreshold = "10000"
2016-02-13 07:23:37 INFO: nxt.transactionLogThreshold = "15000"
2016-02-13 07:23:37 INFO: nxt.transactionLogInterval = "15"
2016-02-13 07:23:37 INFO: nxt.dbCacheKB = "0"
2016-02-13 07:23:37 INFO: nxt.dbUrl = "jdbc:h2:/Users/marcsegers/Library/Application Support/Nxt Wallet/nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE"
2016-02-13 07:23:37 INFO: nxt.dbType = "h2"
2016-02-13 07:23:37 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-02-13 07:23:37 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-02-13 07:23:37 INFO: nxt.dbUsername = "sa"
2016-02-13 07:23:37 INFO: nxt.dbPassword = "{not logged}"
2016-02-13 07:23:37 INFO: nxt.maxDbConnections = "30"
2016-02-13 07:23:37 INFO: nxt.dbLoginTimeout = "70"
2016-02-13 07:23:37 INFO: nxt.dbDefaultLockTimeout = "60"
2016-02-13 07:23:37 FINE: Database jdbc url set to jdbc:h2:/Users/marcsegers/Library/Application Support/Nxt Wallet/nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE;MV_STORE=FALSE;CACHE_SIZE=262144 username sa
2016-02-13 07:23:37 INFO: nxt.useStrongSecureRandom = "false"
2016-02-13 07:23:44 FINE: Database connection pool current size: 1
2016-02-13 07:23:44 INFO: Database update may take a while if needed, current db version 477...
2016-02-13 07:23:44 INFO: nxt.enableTransactionRebroadcasting = "true"
2016-02-13 07:23:44 INFO: nxt.testUnconfirmedTransactions not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.maxUnconfirmedTransactions = "2000"
2016-02-13 07:23:44 INFO: nxt.trimDerivedTables = "true"
2016-02-13 07:23:44 INFO: nxt.numberOfForkConfirmations = "2"
2016-02-13 07:23:44 INFO: nxt.trimFrequency = "1000"
2016-02-13 07:23:44 INFO: nxt.disableGetMoreBlocksThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disableProcessTransactionsThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disableRemoveUnconfirmedTransactionsThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disableProcessWaitingTransactionsThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disableRebroadcastTransactionsThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.enablePublicKeyCache = "true"
2016-02-13 07:23:44 INFO: nxt.ledgerTrimKeep = "30000"
2016-02-13 07:23:44 INFO: nxt.ledgerAccounts = "*"
2016-02-13 07:23:44 INFO: Account ledger is tracking all accounts
2016-02-13 07:23:44 INFO: nxt.ledgerLogUnconfirmed = "2"
2016-02-13 07:23:44 INFO: nxt.processPolls = "true"
2016-02-13 07:23:44 INFO: nxt.deleteFinishedShufflings = "false"
2016-02-13 07:23:44 INFO: nxt.hideErrorDetails = "false"
2016-02-13 07:23:44 INFO: nxt.myPlatform = "PC"
2016-02-13 07:23:44 INFO: nxt.myAddress not defined
2016-02-13 07:23:44 INFO: nxt.peerServerPort = "7874"
2016-02-13 07:23:44 INFO: nxt.shareMyAddress = "true"
2016-02-13 07:23:44 INFO: nxt.enablePeerUPnP = "true"
2016-02-13 07:23:44 INFO: nxt.myHallmark not defined
2016-02-13 07:23:44 INFO: nxt.adminPassword not defined
2016-02-13 07:23:44 INFO: nxt.maxAPIRecords = "100"
2016-02-13 07:23:44 INFO: nxt.enableAPIUPnP = "false"
2016-02-13 07:23:44 INFO: nxt.disabledAPIs not defined
2016-02-13 07:23:44 INFO: nxt.disabledAPITags not defined
2016-02-13 07:23:44 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-02-13 07:23:44 INFO: nxt.enableAPIServer = "true"
2016-02-13 07:23:44 INFO: nxt.apiServerPort = "7876"
2016-02-13 07:23:44 INFO: nxt.apiServerSSLPort = "7876"
2016-02-13 07:23:44 INFO: nxt.apiServerHost = "127.0.0.1"
2016-02-13 07:23:44 INFO: nxt.disableAdminPassword = "false"
2016-02-13 07:23:44 INFO: nxt.apiSSL = "false"
2016-02-13 07:23:44 INFO: nxt.apiServerIdleTimeout = "30000"
2016-02-13 07:23:44 INFO: API server using HTTP port 7876
2016-02-13 07:23:44 INFO: nxt.apiResourceBase = "html/ui"
2016-02-13 07:23:44 INFO: nxt.apiWelcomeFile = "index.html"
2016-02-13 07:23:44 INFO: nxt.javadocResourceBase = "html/doc"
2016-02-13 07:23:44 INFO: nxt.maxUploadFileSize not defined or not numeric, using default value 0
2016-02-13 07:23:44 INFO: nxt.enableAPIServerGZIPFilter = "false"
2016-02-13 07:23:44 INFO: nxt.apiServerCORS = "false"
2016-02-13 07:23:44 INFO: nxt.apiFrameOptionsSameOrigin = "true"
2016-02-13 07:23:44 FINE: My peer info:
{"application":"NRS","services":"0","version":"1.7.5","platform":"PC","shareAddress":true}
2016-02-13 07:23:44 INFO: nxt.defaultPeers = "bug.airdns.org; 93.208.212.137; nxt6.y.cz; 104.193.41.253; 37.139.5.199; 109.230.224.89; 70.106.182.230; 77.144.105.130; 78.62.219.252; 68.168.161.160; 78.46.233.109; 120.25.65.184; nxt.cryonet.de; 111.192.141.164; 98.245.11.138; 100.34.247.56; 85.10.201.15; 05.zapto.org; 158.69.33.172; 78.47.58.62; 144.76.3.50; 192.99.77.148; 90.153.107.93; 76.79.201.54; 5.9.149.197; 81.2.103.237; 92.222.65.40; nxt4.y.cz; 178.62.225.240; 85.25.198.120; 185.99.132.54; 89.212.19.49; nxt01.now.im; nrs.scripterron.org; 175.156.85.245; 62.227.10.194; 73.40.166.72; 217.23.6.2; 73.40.166.127; 174.140.167.239; 52.79.46.24; 162.243.242.8; gunka.szn.dk; 128.199.46.72; 101.100.175.48; 76.176.202.107; 69.163.40.132; 192.0.226.19; 100.13.33.13; 94.227.33.223; 90.75.247.40; raspi2nxtnode.ddns.net; nxt-001.nodes.be; 83.83.161.46; 91.121.150.75; nxt3.y.cz; 80.153.101.190; 95.215.47.221; 86.206.97.98; 78.47.115.250; 52.29.122.21; nxt.sx; nxt.cybermailing.com; 5.230.145.165; 70.31.212.252; 188.243.4.139; 128.199.189.226; nxt.scriba.io; 174.17.156.59; 80.150.243.96; 51.254.99.240; pakisnxt.no-ip.org; enricoip.no-ip.biz; 50.27.137.177; 80.150.243.99; 211.149.213.86; 176.97.2.179; 198.46.193.111; 80.150.243.12; 176.9.138.21; 80.150.243.13; f376.ddns.net; 61.120.160.90; 52.28.97.208; 5.9.180.173; 77.123.252.71; 93.211.251.105; 79.159.11.14; 96.255.76.163; langust.ddns.net; 73.50.115.206; 66.215.60.93; 69.137.154.114; 103.250.83.112; 46.101.112.58; 71.170.34.26; 176.97.2.141; nxt1.testdruif.be; home.kaerner.net; nxt.bened.de; 78.46.160.9; 162.243.122.251; 178.15.99.67; 78.46.49.59:4509; 93.219.103.107; 78.63.207.76; 198.211.127.34; 5.9.155.145; nxt.ydns.eu; 87.138.143.21; 77.152.74.54; 198.199.95.15; 46.223.83.130; 103.250.83.127; 91.210.188.6; 87.139.122.48; nxt1.y.cz; 113.106.85.172; 37.97.136.254; 87.139.122.157; 94.102.50.75; 70.189.162.138; 79.167.162.77; ct.flipflop.mooo.com; 51.255.149.237; 174.91.212.242; petko.ddns.net; 181.47.183.188; 93.75.9.10; 176.94.115.161; 91.235.72.49; 71.60.182.55; nxtcoin.no-ip.org; 91.239.69.78; 2.218.35.177; 46.4.74.71; 162.243.145.83; 94.102.50.68; 14.200.253.61; nxtpeers.com; 192.3.196.10; 80.98.81.73; nxt2.testdruif.be; 77.88.208.12; 84.252.21.155; 158.69.194.254; 23.94.134.161; 96.236.141.73; 142.4.218.174; 72.182.27.227; 178.33.203.157; nxt.noip.me; 176.31.167.127; sluni.szn.dk; 198.27.81.25; 216.119.150.238; 71.218.89.236; 190.10.9.166; 166.48.75.119; megaman.thican.net; 88.163.78.131; 132.230.76.160; 54.213.222.141; humanoide.thican.net; 106.187.102.227; 96.236.143.175; 217.26.24.27; 184.191.182.165; 52.0.72.67; 104.130.7.74; 62.85.20.37; 82.165.138.42;"
2016-02-13 07:23:44 INFO: nxt.wellKnownPeers not defined
2016-02-13 07:23:44 INFO: nxt.knownBlacklistedPeers not defined
2016-02-13 07:23:44 INFO: nxt.maxNumberOfInboundConnections = "250"
2016-02-13 07:23:44 INFO: nxt.maxNumberOfOutboundConnections = "50"
2016-02-13 07:23:44 INFO: nxt.maxNumberOfConnectedPublicPeers = "20"
2016-02-13 07:23:44 INFO: nxt.maxNumberOfKnownPeers = "2000"
2016-02-13 07:23:44 INFO: nxt.minNumberOfKnownPeers = "1000"
2016-02-13 07:23:44 INFO: nxt.connectTimeout = "10000"
2016-02-13 07:23:44 INFO: nxt.readTimeout = "20000"
2016-02-13 07:23:44 INFO: nxt.enableHallmarkProtection = "true"
2016-02-13 07:23:44 INFO: nxt.pushThreshold = "0"
2016-02-13 07:23:44 INFO: nxt.pullThreshold = "0"
2016-02-13 07:23:44 INFO: nxt.useWebSockets = "true"
2016-02-13 07:23:44 INFO: nxt.webSocketIdleTimeout = "900000"
2016-02-13 07:23:44 INFO: nxt.enablePeerServerGZIPFilter = "true"
2016-02-13 07:23:44 INFO: nxt.blacklistingPeriod = "600000"
2016-02-13 07:23:44 INFO: nxt.communicationLoggingMask = "0"
2016-02-13 07:23:44 INFO: nxt.sendToPeersLimit = "10"
2016-02-13 07:23:44 INFO: nxt.usePeersDb = "true"
2016-02-13 07:23:44 INFO: nxt.savePeers = "true"
2016-02-13 07:23:44 INFO: nxt.getMorePeers = "true"
2016-02-13 07:23:44 INFO: nxt.cjdnsOnly = "false"
2016-02-13 07:23:44 INFO: nxt.ignorePeerAnnouncedAddress = "false"
2016-02-13 07:23:44 INFO: nxt.disablePeerConnectingThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disablePeerUnBlacklistingThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disableGetMorePeersThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.peerServerHost = "0.0.0.0"
2016-02-13 07:23:44 INFO: nxt.peerServerIdleTimeout = "30000"
2016-02-13 07:23:44 INFO: nxt.enablePeerServerDoSFilter = "true"
2016-02-13 07:23:44 INFO: nxt.peerServerDoSFilter.maxRequestsPerSec = "30"
2016-02-13 07:23:44 INFO: nxt.peerServerDoSFilter.delayMs = "1000"
2016-02-13 07:23:44 INFO: nxt.peerServerDoSFilter.maxRequestMs = "300000"
2016-02-13 07:23:44 INFO: nxt.maxNumberOfForgers = "100"
2016-02-13 07:23:44 INFO: nxt.enableFakeForging not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.disableGenerateBlocksThread not defined, assuming false
2016-02-13 07:23:44 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-02-13 07:23:44 INFO: nxt.enableUIServer = "false"
2016-02-13 07:23:44 INFO: User interface server not enabled
2016-02-13 07:23:44 INFO: nxt.debugTraceQuote = """
2016-02-13 07:23:44 INFO: nxt.debugTraceSeparator = "   "
2016-02-13 07:23:44 INFO: nxt.debugLogUnconfirmed = "false"
2016-02-13 07:23:44 INFO: nxt.debugTraceAccounts not defined
2016-02-13 07:23:44 INFO: nxt.debugTraceLog = "nxt-trace.csv"
2016-02-13 07:23:44 FINE: Running 2 tasks...
2016-02-13 07:23:44 FINE: Loading known peers from the database...
2016-02-13 07:23:44 FINE: Database connection pool current size: 2
2016-02-13 07:23:44 INFO: Genesis block already in database
2016-02-13 07:23:44 FINE: Rollback from block 4842631404627106472 at height 637791 to 4842631404627106472 at 637791
2016-02-13 07:23:49 FINE: Average database transaction time is 5,188 seconds
2016-02-13 07:23:49 INFO: Last block height: 637791
2016-02-13 07:23:49 INFO: nxt.forceScan = "false"
2016-02-13 07:23:49 FINE: Running 2 final tasks...
2016-02-13 07:23:49 INFO: nxt.apiServerEnforcePOST = "true"
2016-02-13 07:23:49 INFO: Looking for UPnP gateway device...
2016-02-13 07:23:49 INFO: nxt.upnpGatewayTimeout not defined or not numeric, using default value 7000
2016-02-13 07:23:50 INFO: nxt.upnpDiscoverTimeout not defined or not numeric, using default value 3000
2016-02-13 07:23:50 INFO: Started API server at 127.0.0.1:7876
2016-02-13 07:23:57 FINE: UPnP gateway device found on 192.168.0.163
2016-02-13 07:23:57 FINE: There is no connected UPnP gateway device
2016-02-13 07:23:57 INFO: Started peer networking server at 0.0.0.0:7874
2016-02-13 07:23:57 FINE: Starting 9 background jobs
2016-02-13 07:23:57 FINE: Starting 2 delayed tasks
2016-02-13 07:23:57 INFO: Initialization took 20 seconds
2016-02-13 07:23:57 INFO: Nxt server 1.7.5 started successfully.
2016-02-13 07:23:57 INFO: Copyright © 2013-2016 The Nxt Core Developers.
2016-02-13 07:23:57 INFO: Distributed under GPLv2, with ABSOLUTELY NO WARRANTY.
2016-02-13 07:23:57 INFO: Client UI is at http://localhost:7876/index.html
2016-02-13 07:23:57 FINE: Known peers: 239
2016-02-13 07:23:57 FINE: Database connection pool current size: 3
2016-02-13 07:23:57 FINE: Peer 91.235.72.49 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.7.5","platform":"PC","shareAddress":true}, disconnecting

What am I doing wrong?????
Title: Re: NRS v1.7.5
Post by: Riker on February 13, 2016, 07:58:07 am
@Nexxie the log looks fine, are you getting 404 error when accessing http://localhost:7876/index.html ?
If so, what you need to do, is open a terminal window, cd to your NXT folder, if you used the installation defaults:
cd /Applications/NXT
Then invoke run.command from the terminal:
./run.command
Title: Re: NRS v1.7.5
Post by: Nexxie on February 13, 2016, 01:52:11 pm
@Nexxie the log looks fine, are you getting 404 error when accessing http://localhost:7876/index.html ?
If so, what you need to do, is open a terminal window, cd to your NXT folder, if you used the installation defaults:
cd /Applications/NXT
Then invoke run.command from the terminal:
./run.command

Thanks Riker

I managed to put in the command lines, I guess.
It seems it is now downloading the blockchain and it will remain doing that for the next 224 minutes...
After that, then what?
This is way to complicated for the average Mac user...

Thanks
Title: Re: NRS v1.7.5
Post by: Nexxie on February 13, 2016, 03:17:58 pm
@Nexxie the log looks fine, are you getting 404 error when accessing http://localhost:7876/index.html ?
If so, what you need to do, is open a terminal window, cd to your NXT folder, if you used the installation defaults:
cd /Applications/NXT
Then invoke run.command from the terminal:
./run.command

Yes I get error 404. What does that mean?
Title: Re: NRS v1.7.5
Post by: Riker on February 13, 2016, 03:31:50 pm
@Nexxie the log looks fine, are you getting 404 error when accessing http://localhost:7876/index.html ?
If so, what you need to do, is open a terminal window, cd to your NXT folder, if you used the installation defaults:
cd /Applications/NXT
Then invoke run.command from the terminal:
./run.command

Yes I get error 404. What does that mean?

It's a bug ... to workaround it create or update the nxt.properties file in the conf folder and add the following setting:
nxt.apiResourceBase=./html/ui
Title: Re: NRS v1.7.5
Post by: Nexxie on February 13, 2016, 03:41:40 pm
@Nexxie the log looks fine, are you getting 404 error when accessing http://localhost:7876/index.html ?
If so, what you need to do, is open a terminal window, cd to your NXT folder, if you used the installation defaults:
cd /Applications/NXT
Then invoke run.command from the terminal:
./run.command

Yes I get error 404. What does that mean?

It's a bug ... to workaround it create or update the nxt.properties file in the conf folder and add the following setting:
nxt.apiResourceBase=./html/ui

I found the file but how do I update it? I can't even open it...

How long does it take for the blockchain to download? It keeps staying around 200 minutes, the log says...

thanks
Title: Re: NRS v1.7.5
Post by: Nexxie on February 14, 2016, 06:43:11 am
@Nexxie the log looks fine, are you getting 404 error when accessing http://localhost:7876/index.html ?
If so, what you need to do, is open a terminal window, cd to your NXT folder, if you used the installation defaults:
cd /Applications/NXT
Then invoke run.command from the terminal:
./run.command

Yes I get error 404. What does that mean?

It's a bug ... to workaround it create or update the nxt.properties file in the conf folder and add the following setting:
nxt.apiResourceBase=./html/ui

I found the file but how do I update it? I can't even open it...

How long does it take for the blockchain to download? It keeps staying around 200 minutes, the log says...

thanks

And there we go again... After the terminal indicating it is downloading the blockchain by 719 blocks a time, again a whole afternoon, it started saying about unblacklisting for several times and stopped downloading the blockchain.
Again a lot of time waisted and still no client running..  >:(
Title: Re: NRS v1.7.5
Post by: altsheets on February 15, 2016, 10:53:33 am
on the bottom of the page http://www.peerexplorer.com you can download
a snapshot of the whole blockchain. Faster than the "719 blocks a time" way.

Then if you don't know where to put it, you can e.g. search your whole
computer for file & folder named the same, (perhaps make a backup)
and overwrite that with the contents of the archive.

Then, when you start NXT, it only needs to get a few hundred more blocks and you are synced.

(Actually, idea: That bootstrap download could be included as an opt-in into the installer)
Title: Re: NRS v1.7.5
Post by: farl4bit on February 17, 2016, 06:50:13 pm
Regarding the Mac installer. The current installer is a compromise between the tools Java provides and the user experience Mac users expect.

Please consider that the current installer has the following important advantages:
1. Packaged automatically from the development environment and is therefore fully reproducible by anyone which has a Mac directly from the source code
2. Digitally signed using the "NXT Stitchting" digital signature which allows it to be downloaded to any Mac without receiving scary installation warnings or having to add specific security exceptions
3. Bundles a Java distribution, therefore it saves users the joy of installing Oracle Java on their Mac

Currently we use the IzPack tool to generate a cross platform installer which is almost the same on Windows, Linux and Mac. But since this is a cross platform tool, the installed NXT package is incompatible with the layout of a Mac application and therefore has to rely on the same terminal commands used by the Linux distribution.
The installer package itself is packaged using the javapackager tool which converts it to a standard Mac DMG file.
This creates the strange effect that the installer itself is an application (NXT-installer) but the actual installed package is not.

Can we do better ? Perhaps
Is it difficult ? Very

Regarding the desktop wallet. I recently experimented with a Javafx tool which wraps a browser component using a Java container and can therefore open the wallet automatically like the Wesley installer. It almost works but has some limitations which makes it difficult to use. Still haven't gave up on this.

Regarding the rest of the problems,
Uninstaller - I'll look into the uninstaller issue but there is no reason not to just delete the NXT folder so there is really no need to use it.
Applications folder - Do you really have to install the nxt package itself to the /Applications folder ? Can't you just choose another package in the installer dialog ?
Double click on run.command starts an unusable wallet, this is a known issue that I intend to fix.

Thanks for the explanation Riker. You do great work, but I am just disappointed that I haven't got the Mac Wallet as I used it for 2 years (started by Wesley). That was just a one-click-app, nothing more. That was my main reason for Nxt. Easy-to-use. Hope someone will create this again.

I feel like a were send back 2 years in time. Is it safe the forge in the incognito-window of Chrome?
Title: Re: NRS v1.7.5
Post by: Riker on February 17, 2016, 07:48:47 pm
Thanks for the explanation Riker. You do great work, but I am just disappointed that I haven't got the Mac Wallet as I used it for 2 years (started by Wesley). That was just a one-click-app, nothing more. That was my main reason for Nxt. Easy-to-use. Hope someone will create this again.

I feel like a were send back 2 years in time. Is it safe the forge in the incognito-window of Chrome?

I'm working on a desktop wallet which is launched directly from the run command. This would eliminate the manual step of opening a browser to load the wallet and will probably open up the door for additional usability improvements.
Regarding the current Mac installation procedure, probably won't change soon. According to bitbucket only 4% of the package downloads are for nxt-installer-1.7.5.dmg so we need to prioritize.
Title: Re: NRS v1.7.5
Post by: SamIbandii on February 23, 2016, 07:03:16 pm
Hooooray a desktop wallet!!
That 's great news, thanks Riker.  :D
Title: Re: NRS v1.7.5
Post by: Marc De Mesel on February 23, 2016, 07:09:50 pm
Desktop wallet would be great indeed Riker.
Title: Re: NRS v1.7.5
Post by: wesley on February 23, 2016, 07:23:47 pm
Oh good, desktop wallet :-) I was planning to return to build one, but seems I don't need to now :-)
Title: Re: NRS v1.7.5
Post by: farl4bit on February 23, 2016, 10:08:56 pm
Oh good, desktop wallet :-) I was planning to return to build one, but seems I don't need to now :-)

You are always welcome to return. Your Nxt Mac Wallet was one of the reasons Nxt is the #1 crypto out there!  :-*
Title: Re: NRS v1.7.5
Post by: Marc De Mesel on February 23, 2016, 10:56:09 pm
Oh good, desktop wallet :-) I was planning to return to build one, but seems I don't need to now :-)

That would be awesome Wesley! :)

Title: Re: NRS v1.7.5
Post by: CryptKeeper on February 24, 2016, 09:56:27 am
I've just noticed that the "compact.bat" isn't working right out of the box with the windows installer.
It fails because it can't find the path to java.exe, if you haven't installed a separate java runtime. The windows installer version brings it own java in a folder "nxt/jre" so you don't need to install the java runtime.

I think you need a wrapper around the compact call like in run.bat. I see the same problem with "mint.bat".

Nothing critical though.  ;)
Title: Re: NRS v1.7.5
Post by: CryptKeeper on February 24, 2016, 04:05:21 pm
The shutdown procedure in the windows installer version is error-prone.
If you shutdown by the systray option, the database is still busy while the systray icon is long gone:

Code: [Select]
2016-02-24 16:55:11 INFO: Shutdown requested by System Tray
2016-02-24 16:55:11 INFO: Shutting down...
2016-02-24 16:55:12 INFO: Stopping background jobs...
2016-02-24 16:55:12 INFO: shutting down scheduledThreadPool
2016-02-24 16:55:12 INFO: ...Done
2016-02-24 16:55:12 FINE: Mapping deleted for port 7874
2016-02-24 16:55:12 INFO: shutting down sendingService
2016-02-24 16:55:12 INFO: shutting down peersService
2016-02-24 16:55:29 INFO: Database shutdown completed
2016-02-24 16:55:29 INFO: Nxt server 1.7.5 stopped.

There is a confirmation dialog for the shutdown. I've confirmed it at 16:55:13. Please note that the database shutdown is logged at 16:55:29. That's 16 seconds later (windows was quite busy).

Could the database become corrupted if I shutdown windows while the NRS is still closing?
Title: Re: NRS v1.7.5
Post by: P2PGuy on February 25, 2016, 09:55:16 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.5

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.5.zip



This version (and the last 3 versions) do not work on my version Mac OSX Mavericks. The app starts up, the blockchain updates after a few hours but it then hangs without opening the wallet. 6 or 7 hours later it crashes?

Tried everything, Terminal commands, Memory leak checks, re-downloading the blockchain, updated the Java plugin.
Title: Re: NRS v1.7.5
Post by: Twarden on February 25, 2016, 05:22:21 pm
I unzipped the new version and updated the nxt-default.properties file an saved it as nxt.properties.  When I attempt to start the server, I receive this cryptic error message:

Code: [Select]
root@xagate:/home/manager/nxt# sh run.sh
Initializing Nxt server version 1.7.5
isHeadless=true
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.RuntimeException: Using an nxt-default.properties file from a version other than 1.7.5 is not supported!!!
        at nxt.Nxt.<clinit>(Nxt.java:72)
Title: Re: NRS v1.7.5
Post by: MrV777 on February 25, 2016, 05:33:36 pm
I unzipped the new version and updated the nxt-default.properties file an saved it as nxt.properties.  When I attempt to start the server, I receive this cryptic error message:

Code: [Select]
root@xagate:/home/manager/nxt# sh run.sh
Initializing Nxt server version 1.7.5
isHeadless=true
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.RuntimeException: Using an nxt-default.properties file from a version other than 1.7.5 is not supported!!!
        at nxt.Nxt.<clinit>(Nxt.java:72)

It seems to be saying that you removed/edited nxt-default.properties which you shouldn't do
Title: Re: NRS v1.7.5
Post by: EvilDave on February 25, 2016, 06:29:06 pm
You should simply leave the nxt-default.properties as it is, then create a nxt.properties file in the same folder and add your custom settings to that.

Quickest and easiest way to do this under Windows is to open nxt-default.properties, delete everything except your custom settings, then 'Save As...' to save the resulting file under the new name; nxt.properties
Title: Re: NRS v1.7.5
Post by: Riker on February 25, 2016, 09:25:08 pm
Oh good, desktop wallet :-) I was planning to return to build one, but seems I don't need to now :-)

I'm working on a desktop wallet based on JavaFX WebView which is a Java wrapper around webkit rendering engine.
The desktop wallet can reuse most of the existing wallet JavaScript/Html/CSS code, run in a separate frame and communicate directly with the server code using JavaScript to Java liveconnect.
It looks very much like the existing browser wallet and pretty much the same on Windows, Linux and Mac.

Alas, there are quite a few limitations that I'm trying to address. The biggest being that indexedDB is not supported. I'm trying to re-implement some of the indexedDB functionality using local storage and this is very time consuming.

The good thing is that the desktop wallet opens up various improvement opportunities like implementing a "Bitcoin like" multi-account wallet and getting immediate updates from the server about new blocks and transactions instead of polling.

I estimate that this wallet can be released on mainnet sometime in April.
Title: Re: NRS v1.7.5
Post by: Riker on February 25, 2016, 09:26:13 pm
I've just noticed that the "compact.bat" isn't working right out of the box with the windows installer.
It fails because it can't find the path to java.exe, if you haven't installed a separate java runtime. The windows installer version brings it own java in a folder "nxt/jre" so you don't need to install the java runtime.

I think you need a wrapper around the compact call like in run.bat. I see the same problem with "mint.bat".

Nothing critical though.  ;)

Thanks for reporting, I'll try to fix that for the next release.
Title: Re: NRS v1.7.5
Post by: Riker on February 25, 2016, 09:34:23 pm
The shutdown procedure in the windows installer version is error-prone.
If you shutdown by the systray option, the database is still busy while the systray icon is long gone:

Code: [Select]
2016-02-24 16:55:11 INFO: Shutdown requested by System Tray
2016-02-24 16:55:11 INFO: Shutting down...
2016-02-24 16:55:12 INFO: Stopping background jobs...
2016-02-24 16:55:12 INFO: shutting down scheduledThreadPool
2016-02-24 16:55:12 INFO: ...Done
2016-02-24 16:55:12 FINE: Mapping deleted for port 7874
2016-02-24 16:55:12 INFO: shutting down sendingService
2016-02-24 16:55:12 INFO: shutting down peersService
2016-02-24 16:55:29 INFO: Database shutdown completed
2016-02-24 16:55:29 INFO: Nxt server 1.7.5 stopped.

There is a confirmation dialog for the shutdown. I've confirmed it at 16:55:13. Please note that the database shutdown is logged at 16:55:29. That's 16 seconds later (windows was quite busy).

Could the database become corrupted if I shutdown windows while the NRS is still closing?

Correct, currently the shutdown system tray option simply calls System.exit() which invokes the server shutdown hook.
The side effect is that the system tray icon disappears immediately but the shutdown hook closes the database and this takes time.
This is not simple to fix.

If you perform an orderly shutdown of Windows the shutdown hook should run to completion and close the database correctly regardless of the system tray icon.
If you hit the power button, then yes you can corrupt the database.
Title: Re: NRS v1.7.5
Post by: Riker on February 25, 2016, 09:35:25 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.5

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.7.5.zip



This version (and the last 3 versions) do not work on my version Mac OSX Mavericks. The app starts up, the blockchain updates after a few hours but it then hangs without opening the wallet. 6 or 7 hours later it crashes?

Tried everything, Terminal commands, Memory leak checks, re-downloading the blockchain, updated the Java plugin.

Can you find your nxt.log and post it somewhere I can see ?
Title: Re: NRS v1.7.5
Post by: nestingdoll on February 27, 2016, 07:11:41 am
thank you
Title: Re: NRS v1.7.5
Post by: Cybnate on February 28, 2016, 04:55:57 am
Upgrade issue here. Tried to unzip the client into my existing folders after having stopped the previous NXT client 1.5.x.
After a brief conversion process it stopped and threw an exception. Tried to start it 2 more times to no avail. Deleted the database in nxt_db folder hoping that would solve the issue but it doesn't.
Probably I'm overlooking another file which also needs to be deleted or some specific config.

Please help.

Below the relevant part of the log:

Quote
Initializing Nxt server version 1.7.5

2016-02-28 17:32:39 FINE: os.arch = amd64
2016-02-28 17:32:39 FINE: sun.arch.data.model = 64
2016-02-28 17:32:39 FINE: os.name = Windows 7
2016-02-28 17:32:39 FINE: file.encoding = Cp1252
2016-02-28 17:32:39 FINE: nxt.runtime.mode = desktop
2016-02-28 17:32:39 FINE: availableProcessors = 2
2016-02-28 17:32:39 FINE: maxMemory = 954728448
2016-02-28 17:32:39 FINE: processId = 1700
2016-02-28 17:32:39 INFO: nxt.isTestnet = "false"
2016-02-28 17:32:39 INFO: nxt.isOffline = "false"
2016-02-28 17:32:39 INFO: nxt.maxRollback = "1441"
2016-02-28 17:32:39 INFO: nxt.forgingDelay = "20"
2016-02-28 17:32:39 INFO: nxt.forgingSpeedup = "3"
2016-02-28 17:32:39 INFO: nxt.maxPrunableLifetime = "7776000"
2016-02-28 17:32:39 INFO: nxt.includeExpiredPrunable = "true"
2016-02-28 17:32:39 INFO: nxt.correctInvalidFees = "false"
2016-02-28 17:32:40 INFO: nxt.statementLogThreshold = "10000"
2016-02-28 17:32:42 INFO: nxt.transactionLogThreshold = "15000"
2016-02-28 17:32:46 INFO: nxt.transactionLogInterval = "15"
2016-02-28 17:32:46 INFO: nxt.useStrongSecureRandom = "false"
2016-02-28 17:32:46 INFO: nxt.dbCacheKB = "0"
2016-02-28 17:32:46 INFO: nxt.dbUrl = "jdbc:h2:nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE
;MVCC=TRUE"
2016-02-28 17:32:46 INFO: nxt.dbType = "h2"
2016-02-28 17:32:46 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-02-28 17:32:46 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_ST
ORE=FALSE"
2016-02-28 17:32:46 INFO: nxt.dbUsername = "sa"
2016-02-28 17:32:46 INFO: nxt.dbPassword = "{not logged}"
2016-02-28 17:32:46 INFO: nxt.maxDbConnections = "30"
2016-02-28 17:32:46 INFO: nxt.dbLoginTimeout = "70"
2016-02-28 17:32:46 INFO: nxt.dbDefaultLockTimeout = "60"
2016-02-28 17:32:46 FINE: Database jdbc url set to jdbc:h2:nxt_db/nxt;DB_CLOSE_O
N_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE;CACHE_SIZE=262144 username sa
2016-02-28 17:32:51 FINE: Database connection pool current size: 1
2016-02-28 17:32:51 INFO: Database update may take a while if needed, current db
 version 414...
2016-02-28 17:32:51 FINE: Database connection pool current size: 2
2016-02-28 17:32:51 INFO: Lucene search index deleted
Fatal error: java.lang.NoSuchMethodError: org.apache.lucene.store.FSDirectory.op
en(Ljava/nio/file/Path;)Lorg/apache/lucene/store/FSDirectory;
java.lang.NoSuchMethodError: org.apache.lucene.store.FSDirectory.open(Ljava/nio/
file/Path;)Lorg/apache/lucene/store/FSDirectory;
        at nxt.db.FullTextTrigger.getIndexAccess(FullTextTrigger.java:857)
        at nxt.db.FullTextTrigger.removeIndexFiles(FullTextTrigger.java:935)
        at nxt.db.FullTextTrigger.init(FullTextTrigger.java:203)
        at nxt.NxtDbVersion.update(NxtDbVersion.java:983)
        at nxt.db.DbVersion.init(DbVersion.java:55)
        at nxt.db.BasicDb.init(BasicDb.java:140)
        at nxt.Db.init(Db.java:39)
        at nxt.Nxt$Init.<clinit>(Nxt.java:334)
        at nxt.Nxt.init(Nxt.java:306)
        at nxt.Nxt.main(Nxt.java:293)
Title: Re: NRS v1.7.5
Post by: martismartis on February 28, 2016, 06:07:59 am
Upgrade issue here. Tried to unzip the client into my existing folders after having stopped the previous NXT client 1.5.x.
After a brief conversion process it stopped and threw an exception. Tried to start it 2 more times to no avail. Deleted the database in nxt_db folder hoping that would solve the issue but it doesn't.
Probably I'm overlooking another file which also needs to be deleted or some specific config.

Please help.

Below the relevant part of the log:

Quote
Initializing Nxt server version 1.7.5

2016-02-28 17:32:39 FINE: os.arch = amd64
2016-02-28 17:32:39 FINE: sun.arch.data.model = 64
2016-02-28 17:32:39 FINE: os.name = Windows 7
2016-02-28 17:32:39 FINE: file.encoding = Cp1252
2016-02-28 17:32:39 FINE: nxt.runtime.mode = desktop
2016-02-28 17:32:39 FINE: availableProcessors = 2
2016-02-28 17:32:39 FINE: maxMemory = 954728448
2016-02-28 17:32:39 FINE: processId = 1700
2016-02-28 17:32:39 INFO: nxt.isTestnet = "false"
2016-02-28 17:32:39 INFO: nxt.isOffline = "false"
2016-02-28 17:32:39 INFO: nxt.maxRollback = "1441"
2016-02-28 17:32:39 INFO: nxt.forgingDelay = "20"
2016-02-28 17:32:39 INFO: nxt.forgingSpeedup = "3"
2016-02-28 17:32:39 INFO: nxt.maxPrunableLifetime = "7776000"
2016-02-28 17:32:39 INFO: nxt.includeExpiredPrunable = "true"
2016-02-28 17:32:39 INFO: nxt.correctInvalidFees = "false"
2016-02-28 17:32:40 INFO: nxt.statementLogThreshold = "10000"
2016-02-28 17:32:42 INFO: nxt.transactionLogThreshold = "15000"
2016-02-28 17:32:46 INFO: nxt.transactionLogInterval = "15"
2016-02-28 17:32:46 INFO: nxt.useStrongSecureRandom = "false"
2016-02-28 17:32:46 INFO: nxt.dbCacheKB = "0"
2016-02-28 17:32:46 INFO: nxt.dbUrl = "jdbc:h2:nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE
;MVCC=TRUE"
2016-02-28 17:32:46 INFO: nxt.dbType = "h2"
2016-02-28 17:32:46 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-02-28 17:32:46 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_ST
ORE=FALSE"
2016-02-28 17:32:46 INFO: nxt.dbUsername = "sa"
2016-02-28 17:32:46 INFO: nxt.dbPassword = "{not logged}"
2016-02-28 17:32:46 INFO: nxt.maxDbConnections = "30"
2016-02-28 17:32:46 INFO: nxt.dbLoginTimeout = "70"
2016-02-28 17:32:46 INFO: nxt.dbDefaultLockTimeout = "60"
2016-02-28 17:32:46 FINE: Database jdbc url set to jdbc:h2:nxt_db/nxt;DB_CLOSE_O
N_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE;CACHE_SIZE=262144 username sa
2016-02-28 17:32:51 FINE: Database connection pool current size: 1
2016-02-28 17:32:51 INFO: Database update may take a while if needed, current db
 version 414...
2016-02-28 17:32:51 FINE: Database connection pool current size: 2
2016-02-28 17:32:51 INFO: Lucene search index deleted
Fatal error: java.lang.NoSuchMethodError: org.apache.lucene.store.FSDirectory.op
en(Ljava/nio/file/Path;)Lorg/apache/lucene/store/FSDirectory;
java.lang.NoSuchMethodError: org.apache.lucene.store.FSDirectory.open(Ljava/nio/
file/Path;)Lorg/apache/lucene/store/FSDirectory;
        at nxt.db.FullTextTrigger.getIndexAccess(FullTextTrigger.java:857)
        at nxt.db.FullTextTrigger.removeIndexFiles(FullTextTrigger.java:935)
        at nxt.db.FullTextTrigger.init(FullTextTrigger.java:203)
        at nxt.NxtDbVersion.update(NxtDbVersion.java:983)
        at nxt.db.DbVersion.init(DbVersion.java:55)
        at nxt.db.BasicDb.init(BasicDb.java:140)
        at nxt.Db.init(Db.java:39)
        at nxt.Nxt$Init.<clinit>(Nxt.java:334)
        at nxt.Nxt.init(Nxt.java:306)
        at nxt.Nxt.main(Nxt.java:293)

You had to delete "lib" folder also.
Title: Re: NRS v1.7.5
Post by: Cybnate on February 28, 2016, 07:19:21 am
You said 'you had' with other words too late I suppose? I tried clearing the lib folder and copying the new libs into it. I didn't get the specific exception any longer, but the client still doesn't start properly and exits after a second, can't capture the output and there is nothing in a log file. Is getting too hard.

Will do a clean install from here. Thanks for your suggestion anyway, will keep it in mind the next time.
Title: Re: NRS v1.7.5
Post by: Jushe on February 28, 2016, 02:03:41 pm
Thanks for the explanation Riker. You do great work, but I am just disappointed that I haven't got the Mac Wallet as I used it for 2 years (started by Wesley). That was just a one-click-app, nothing more. That was my main reason for Nxt. Easy-to-use. Hope someone will create this again.

I feel like a were send back 2 years in time. Is it safe the forge in the incognito-window of Chrome?

I'm working on a desktop wallet which is launched directly from the run command. This would eliminate the manual step of opening a browser to load the wallet and will probably open up the door for additional usability improvements.
Regarding the current Mac installation procedure, probably won't change soon. According to bitbucket only 4% of the package downloads are for nxt-installer-1.7.5.dmg so we need to prioritize.

You are a hero, I've been waiting for a desktop wallet to return! One click app like Wesleys is something I really liked about nxt.
Title: Re: NRS v1.7.5
Post by: BTCDDev on March 04, 2016, 08:38:53 pm
Why can't I generate a token???

I am on nxt 1.7.5, logged into my account. My blockchain has not finished downloading.

String:
Code: [Select]
27 BTC to 1GkKbFVub2Hpr9JkcwmuoWtk9jKXjwyUHM => ALJTDQUWDQWRHRXPZD9HWRKKWVDYJZRQFBNHEUPLVFYXURSSDRGCDIMEJNZUZ9GWWHOOQXXQGJT9TL9NF
Generates:
Code: [Select]
hi2cct1qmbfdf801d8r7hafdodmjd7miha313qnt2dridj06903tc4si3g68bb04efc5apu4p2npdmilab7cgvqutd1uc9nmn4kvekmhmvng41vnv1iema80l7vuf85ikt50t33j97f4akid8a3v5uu1tgu70jlo

When I validate the token on http://62.194.6.113:7876/ it says:

The token is NOT VALID. It appears to belong to account NXT-N95T-92SH-8QSF-9DPZW. It was generated on 3/4/2016 15:37:41.

I am definitely logged in to my correct account!

Is there another place I can verify a token?

EDIT: i created the token through supernet lite wallet, it worked.
Title: Re: NRS v1.7.5
Post by: coretechs on March 04, 2016, 10:03:01 pm
Hmm, it doesn't come up as valid in my token tool either.  Perhaps there was a problem parsing the string (maybe the "=>") when it was generated?

https://nxtportal.org/tools/nxt_auth_token.html

(you can save the page and run it offline if you like, everything runs in javascript in the browser)
Title: Pay Divident feature is not working please assist.
Post by: bgcaffe on March 09, 2016, 07:21:02 pm
Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.
Title: Re: Pay Divident feature is not working please assist.
Post by: kseistrup on March 09, 2016, 07:37:53 pm
Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635
I can see the March transaction in the “Account Ledger” (but not on the dahboard under “Recent Transactions”). I can't seem to find the February transaction anywhere, but it seems that the account ledger only goes ~1 month back and there is no way to choose ealier transactions than the ones you can see.
Title: Re: NRS v1.7.5
Post by: lopalcar on March 09, 2016, 11:33:18 pm
@kseistrup: In order to see older ledger entries, I guess you need to modify nxt.properties file and change nxt.ledgerTrimKeep=30000 to 0 in order to keep all blocks.

@bgcaffe: People can see the dividends in the account ledger and their balance is increassed also. If you like to track your account balance and maybe suggest to your shareholders, there's an useful app in the play store called "nxt wallet watcher" which notify you from any balance change in your account.

And... in case this isn't good enough for you and want to send dividends in individual transactions, you have this nice plugin: https://nxtforum.org/nxt-plugins/(plugin)-dividend-payout-plugin-(via-normal-transactions)-for-nrs Forgers will love you if you pay them this way :P
Title: Re: NRS v1.7.5
Post by: Jose on March 09, 2016, 11:34:48 pm
I'm not sure if my issue concerns NRS 1.7.5 or it's just a problem related to my old Raspbery Pi ::), but... Has anybody experienced that NRS stacks everytime it reaches a certain block number (686000, 687000, 688000...)?

It never happened to me with previous NRS versions and the same Raspi, and I've kept it running smoothly for some months.



The CPU goes from 30% to 100% usage at these blocks (usually it's at about 30% when running NRS) and then the blockchain isn't updated anymore... ???
Title: Re: NRS v1.7.5
Post by: kseistrup on March 10, 2016, 08:16:01 am
@kseistrup: In order to see older ledger entries, I guess you need to modify nxt.properties file and change nxt.ledgerTrimKeep=30000 to 0 in order to keep all blocks.
Thanks, mate!
Title: Re: NRS v1.7.5
Post by: Riker on March 10, 2016, 08:34:44 am
I'm not sure if my issue concerns NRS 1.7.5 or it's just a problem related to my old Raspbery Pi ::), but... Has anybody experienced that NRS stacks everytime it reaches a certain block number (686000, 687000, 688000...)?

It never happened to me with previous NRS versions and the same Raspi, and I've kept it running smoothly for some months.



The CPU goes from 30% to 100% usage at these blocks (usually it's at about 30% when running NRS) and then the blockchain isn't updated anymore... ???

It's the trimming of the derived tables which takes place every 1000 blocks by default (this is controlled by the nxt.trimFrequency setting).
This is a heavy database operation which may "chock" your PI if it was already close to being maxed out.

To start with, not sure why you are seeing constant 30% CPU usage. On my 1GB VPS, I rarely see CPU usage of more than 3% from NXT.
Perhaps the PI is already on the verge of running out of memory thus making heavy usage of the garbage collector ?

I assume your PI has 512 Ram. Do you set any specific memory setting for the Java process ?
Next time you start it add the garbage collection flags to the Java command line:
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:gc.log

Then when the problem occurs review the gc.log and nxt.log or post it here.
Title: Re: NRS v1.7.5
Post by: Jose on March 10, 2016, 05:05:52 pm
Hi Riker. Thanks for answering :)

The Raspi model isn't the last one, nor the previous one. It has a 700mhz simple ARM processor and 512MB ram (shared with the GPU). 7GB of disk space are left.
I'm using Oracle java 8.
I limit the maximum amount of ram that the java process can use to 256MB using the following command in the run.sh file:
Quote
java -Xmx256m -cp classes:lib/*:conf nxt.Nxt     -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:gc.log
I've added the -verbose... string following your advice, but I haven't been able to locate the gc.log file ::)

Again the system was running ok until it reached the block 689000, and then no more blocks seem to be updated. NRS isn't halted, nor the Raspi isn't hanged, because I can access throught SSH and stop NRS or run other commands. This is what the nxt.log says (the block 689000 happened today at 16:37:34 local time):
Quote
2016-03-10 16:13:24 FINE: SQL statement required 10,036 seconds at height 688975:
UPDATE sell_offer SET latest = FALSE  WHERE id = ?  AND latest = TRUE LIMIT 1
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:330)
  nxt.db.EntityDbTable.insert(EntityDbTable.java:422)
  nxt.CurrencySellOffer.addOffer(CurrencySellOffer.java:102)
  nxt.CurrencyExchangeOffer.publishOffer(CurrencyExchangeOffer.java:81)
  nxt.MonetarySystem$5.applyAttachment(MonetarySystem.java:536)
  nxt.TransactionType.apply(TransactionType.java:240)
  nxt.Attachment$AbstractAttachment.apply(Attachment.java:64)
  nxt.TransactionImpl.apply(TransactionImpl.java:1056)
  nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:1535)
  nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:1349)
  nxt.BlockchainProcessorImpl.access$1100(BlockchainProcessorImpl.java:64)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:552)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:267)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:180)
2016-03-10 16:13:37 FINE: Database transaction required 107,105 seconds at height 688975
  nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:1357)
  nxt.BlockchainProcessorImpl.access$1100(BlockchainProcessorImpl.java:64)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:552)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:267)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:180)
2016-03-10 16:24:11 FINE: Average database transaction time is 0,951 seconds
2016-03-10 16:34:41 FINE: SQL statement required 10,707 seconds at height 688998:
SELECT * FROM trade WHERE asset_id = ? ORDER BY height DESC, db_id DESC LIMIT 1
  nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:319)
  nxt.Trade.getLastTrades(Trade.java:95)
  nxt.http.GetLastTrades.processRequest(GetLastTrades.java:39)
  nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:92)
  nxt.http.APIServlet.process(APIServlet.java:477)
  nxt.http.APIServlet.doGet(APIServlet.java:406)
2016-03-10 16:38:39 FINE: SQL statement required 41,753 seconds at height 689000:
SELECT id, MAX(height) AS max_height FROM account WHERE height < ? GROUP BY id HAVING COUNT(DISTINCT height) > 1
  nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:319)
  nxt.db.VersionedEntityDbTable.trim(VersionedEntityDbTable.java:138)
  nxt.db.EntityDbTable.trim(EntityDbTable.java:443)
  nxt.BlockchainProcessorImpl.doTrimDerivedTables(BlockchainProcessorImpl.java:1064)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1047)
  nxt.BlockchainProcessorImpl.lambda$null$27(BlockchainProcessorImpl.java:979)
  nxt.BlockchainProcessorImpl$$Lambda$112/23719618.run(Unknown Source)
2016-03-10 16:39:15 FINE: SQL statement required 36,417 seconds at height 689000:
DELETE FROM account WHERE id = ?  AND height < ? AND height >= 0
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:330)
  nxt.db.VersionedEntityDbTable.trim(VersionedEntityDbTable.java:145)
  nxt.db.EntityDbTable.trim(EntityDbTable.java:443)
  nxt.BlockchainProcessorImpl.doTrimDerivedTables(BlockchainProcessorImpl.java:1064)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1047)
  nxt.BlockchainProcessorImpl.lambda$null$27(BlockchainProcessorImpl.java:979)
  nxt.BlockchainProcessorImpl$$Lambda$112/23719618.run(Unknown Source)
2016-03-10 16:39:15 FINE: SQL statement required 32,789 seconds at height 689000:
SELECT account_id, SUM (additions) AS additions FROM account_guaranteed_balance, TABLE (id BIGINT=?) T WHERE account_id = T.id AND height > ?  GROUP BY account_id ORDER BY account_id
  nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:319)
  nxt.Account.getLessorsGuaranteedBalanceNQT(Account.java:1241)
  nxt.Account.getEffectiveBalanceNXT(Account.java:1209)
  nxt.Account.getEffectiveBalanceNXT(Account.java:1185)
  nxt.http.JSONData.accountBalance(JSONData.java:104)
  nxt.http.GetAccount.processRequest(GetAccount.java:46)
  nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:92)
  nxt.http.APIServlet.process(APIServlet.java:477)
  nxt.http.APIServlet.doGet(APIServlet.java:406)
2016-03-10 16:39:49 FINE: SQL statement required 33,821 seconds at height 689000:
DELETE FROM account WHERE id = ?  AND height < ? AND height >= 0
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:330)
  nxt.db.VersionedEntityDbTable.trim(VersionedEntityDbTable.java:145)
  nxt.db.EntityDbTable.trim(EntityDbTable.java:443)
  nxt.BlockchainProcessorImpl.doTrimDerivedTables(BlockchainProcessorImpl.java:1064)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1047)
  nxt.BlockchainProcessorImpl.lambda$null$27(BlockchainProcessorImpl.java:979)
  nxt.BlockchainProcessorImpl$$Lambda$112/23719618.run(Unknown Source)
...

... and it keeps going on and on with the same block until I manually stop the NRS service (Ctrl+c in the command line), and restart it (sh run.sh). Then after restarting, it takes about a minute to finish downloading the blockchain and no problem again for the following 1000 blocks.

Title: Re: NRS v1.7.5
Post by: Riker on March 10, 2016, 06:34:34 pm
I limit the maximum amount of ram that the java process can use to 256MB using the following command in the run.sh file:
Quote
java -Xmx256m -cp classes:lib/*:conf nxt.Nxt     -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:gc.log

Here is the correct command line, the command line params has to be placed before the class name nxt.Nxt, I also recommend to increase memory to 320MB:
Code: [Select]
java -Xmx320m -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:gc.log -cp classes:lib/*:conf nxt.Nxt
Title: Re: NRS v1.7.5
Post by: mr001 on March 10, 2016, 10:12:43 pm
After installing 1.7.5 from zero with the .dmg file i can't visit localhost:7876 cause i get

Quote
HTTP ERROR: 404

Problem accessing /index.html. Reason:

    Not Found
Powered by Jetty:// 9.3.6.v20151106
I have the same problem on Yasomite , but yesterday it was running.
Title: Re: Pay Divident feature is not working please assist.
Post by: AQQA on March 11, 2016, 12:20:59 am
Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.

I can confirm, I haven't seen my bgcaffe dividend for Feb or March yet. The last dividend I've received was on 2 Jan 2016.
Title: Re: Pay Divident feature is not working please assist.
Post by: martismartis on March 11, 2016, 06:04:10 am
Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.

I can confirm, I haven't seen my bgcaffe dividend for Feb or March yet. The last dividend I've received was on 2 Jan 2016.

Didi you check account ledger under Dashboard in left menu?
Title: Re: Pay Divident feature is not working please assist.
Post by: AQQA on March 11, 2016, 03:36:38 pm
Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.

I can confirm, I haven't seen my bgcaffe dividend for Feb or March yet. The last dividend I've received was on 2 Jan 2016.

Didi you check account ledger under Dashboard in left menu?

Thanks, but yes, did check. Just not seeing it; no dividend from BGCAFFE after the 2nd.
Title: Re: NRS v1.7.5
Post by: Jose on March 12, 2016, 07:44:21 am
... I also recommend to increase memory to 320MB...

Well, it seems that increasing the memory allocated to Java up to 320MB worked!  8)
Now my Raspi with NRS 1.7.5 works as it used to with the previous versions!
Thank you very much! :)
Title: Re: Pay Divident feature is not working please assist.
Post by: bgcaffe on March 12, 2016, 04:37:15 pm
It seems that all the confusion is related to new dividend payment feature not showing up in the normal transaction log. You need to check your account ledger to see the transaction.

This is causing quite a bit of confusion for our users, is there a way it can be improved?

Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.

I can confirm, I haven't seen my bgcaffe dividend for Feb or March yet. The last dividend I've received was on 2 Jan 2016.
Title: Re: Pay Divident feature is not working please assist.
Post by: Sebastien256 on March 12, 2016, 04:46:24 pm
It seems that all the confusion is related to new dividend payment feature not showing up in the normal transaction log. You need to check your account ledger to see the transaction.

This is causing quite a bit of confusion for our users, is there a way it can be improved?

Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.

I can confirm, I haven't seen my bgcaffe dividend for Feb or March yet. The last dividend I've received was on 2 Jan 2016.

You can use the dividend plugin from testdruif, it will show in the dashboard.
Title: Re: Pay Divident feature is not working please assist.
Post by: bgcaffe on March 12, 2016, 04:47:46 pm
Thanks will give it a go.

It seems that all the confusion is related to new dividend payment feature not showing up in the normal transaction log. You need to check your account ledger to see the transaction.

This is causing quite a bit of confusion for our users, is there a way it can be improved?

Hi,

Can someone please assist us the last two months we have been paying dividends using the pay dividend feature within the NXT 1.7.5 client. However people have not been receiving the dividend and the NXT is being subtracted from our account. What is going on?

Here is the March transaction: 551230313289286389
and Feb is: 11102242001579620635

Before this we were using the plugin from the Supernet client and all went well. Its really difficult to see what is going on with the new client as its just a single transaction and no detail of who received the payment.

I can confirm, I haven't seen my bgcaffe dividend for Feb or March yet. The last dividend I've received was on 2 Jan 2016.

You can use the dividend plugin from testdruif, it will show in the dashboard.
Title: Re: NRS v1.7.5
Post by: Sebastien256 on March 12, 2016, 04:50:47 pm
here is the link to the plugin
https://nxtforum.org/nxt-plugins/(plugin)-dividend-payout-plugin-(via-normal-transactions)-for-nrs/msg205989/#msg205989
Title: Re: NRS v1.7.5
Post by: qq2536007339 on March 14, 2016, 11:51:43 am
I set
Code: [Select]
nxt.ledgerTrimKeep=0,and redownloading the blockchain.

Use http://127.0.0.1:7876/nxt?requestType=getAccountLedger&account=myaccount to check records,but I found out sometimes some transactions are missing for some accounts.

Is this because those accounts are too early when they create?
Title: Re: NRS v1.7.5
Post by: websioux on March 15, 2016, 07:29:37 pm
My Nxt server stopped this night, I can not restart it, looks like something in the DB

Quote
2016-03-15 19:03:01 INFO: nxt.enableStackTraces = "true"
2016-03-15 19:03:01 INFO: nxt.enableLogTraceback = "false"
2016-03-15 19:03:01 INFO: logging enabled
2016-03-15 19:03:01 INFO: socksProxyHost not defined
2016-03-15 19:03:01 INFO: socksProxyPort not defined
2016-03-15 19:03:01 FINE: java.version = 1.8.0_72-internal
2016-03-15 19:03:01 FINE: java.vm.version = 25.72-b15
2016-03-15 19:03:01 FINE: java.vm.name = OpenJDK 64-Bit Server VM
2016-03-15 19:03:01 FINE: java.vendor = Oracle Corporation
2016-03-15 19:03:01 FINE: java.vm.vendor = Oracle Corporation
2016-03-15 19:03:01 FINE: java.home = /usr/lib/jvm/java-8-openjdk-amd64/jre
2016-03-15 19:03:01 FINE: java.library.path = /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
2016-03-15 19:03:01 FINE: java.class.path = classes:lib/bcprov-jdk15on-154.jar:lib/h2-1.4.191.jar:lib/lucene-queries-5.3.1.jar:lib/javax.servlet-api-3.1.0.jar:lib/tika-parsers-1.11.jar:lib/websocket-servlet-9.3.6.v20151106.jar:lib/slf4j-jdk14-1.7.13.jar:lib/slf4j-api-1.7.13.jar:lib/jetty-server-9.3.6.v20151106.jar:lib/lucene-core-5.3.1.jar:lib/websocket-client-9.3.6.v20151106.jar:lib/javase-3.2.1.jar:lib/websocket-common-9.3.6.v20151106.jar:lib/jetty-http-9.3.6.v20151106.jar:lib/jetty-security-9.3.6.v20151106.jar:lib/jetty-io-9.3.6.v20151106.jar:lib/jetty-servlets-9.3.6.v20151106.jar:lib/core-3.2.1.jar:lib/jetty-servlet-9.3.6.v20151106.jar:lib/jetty-util-9.3.6.v20151106.jar:lib/lucene-analyzers-common-5.3.1.jar:lib/weupnp-0.1.4.jar:lib/jetty-continuation-9.3.6.v20151106.jar:lib/h2-1.3.176.jar:lib/websocket-api-9.3.6.v20151106.jar:lib/tika-core-1.11.jar:lib/websocket-server-9.3.6.v20151106.jar:lib/json-simple-1.1.1.jar:lib/lucene-queryparser-5.3.1.jar:conf
2016-03-15 19:03:01 FINE: os.arch = amd64
2016-03-15 19:03:01 FINE: sun.arch.data.model = 64
2016-03-15 19:03:01 FINE: os.name = Linux
2016-03-15 19:03:01 FINE: file.encoding = UTF-8
2016-03-15 19:03:01 FINE: nxt.runtime.mode = null
2016-03-15 19:03:01 FINE: availableProcessors = 16
2016-03-15 19:03:01 FINE: maxMemory = 4294967296
2016-03-15 19:03:01 FINE: processId = 6540
2016-03-15 19:03:01 INFO: nxt.isTestnet = "false"
2016-03-15 19:03:01 INFO: nxt.isOffline = "false"
2016-03-15 19:03:01 INFO: nxt.maxRollback = "800"
2016-03-15 19:03:01 INFO: nxt.forgingDelay = "20"
2016-03-15 19:03:01 INFO: nxt.forgingSpeedup = "3"
2016-03-15 19:03:01 INFO: nxt.maxPrunableLifetime = "-1"
2016-03-15 19:03:01 INFO: nxt.includeExpiredPrunable = "true"
2016-03-15 19:03:01 INFO: nxt.correctInvalidFees = "false"
2016-03-15 19:03:01 INFO: nxt.statementLogThreshold = "10000"
2016-03-15 19:03:01 INFO: nxt.transactionLogThreshold = "15000"
2016-03-15 19:03:01 INFO: nxt.transactionLogInterval = "15"
2016-03-15 19:03:01 INFO: nxt.dbCacheKB = "0"
2016-03-15 19:03:01 INFO: nxt.dbUrl not defined
2016-03-15 19:03:01 INFO: nxt.dbType = "h2"
2016-03-15 19:03:01 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-03-15 19:03:01 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-03-15 19:03:01 INFO: nxt.dbUsername = "sa"
2016-03-15 19:03:01 INFO: nxt.dbPassword = "{not logged}"
2016-03-15 19:03:01 INFO: nxt.maxDbConnections = "30"
2016-03-15 19:03:01 INFO: nxt.dbLoginTimeout = "70"
2016-03-15 19:03:01 INFO: nxt.dbDefaultLockTimeout = "60"
2016-03-15 19:03:01 FINE: Database jdbc url set to jdbc:h2:./nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE;CACHE_SIZE=262144 username sa
2016-03-15 19:03:01 INFO: nxt.useStrongSecureRandom = "false"
2016-03-15 19:03:02 SEVERE: org.h2.jdbc.JdbcSQLException: Allgemeiner Fehler: "java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962"
General error: "java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962" [50000-191]
java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: Allgemeiner Fehler: "java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962"
General error: "java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962" [50000-191]
   at nxt.db.BasicDb.init(BasicDb.java:138)
   at nxt.Db.init(Db.java:39)
   at nxt.Nxt$Init.<clinit>(Nxt.java:334)
   at nxt.Nxt.init(Nxt.java:306)
   at nxt.Nxt.main(Nxt.java:293)
Caused by: org.h2.jdbc.JdbcSQLException: Allgemeiner Fehler: "java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962"
General error: "java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962" [50000-191]
   at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
   at org.h2.message.DbException.get(DbException.java:168)
   at org.h2.message.DbException.convert(DbException.java:295)
   at org.h2.engine.Database.openDatabase(Database.java:301)
   at org.h2.engine.Database.<init>(Database.java:264)
   at org.h2.engine.Engine.openSession(Engine.java:65)
   at org.h2.engine.Engine.openSession(Engine.java:175)
   at org.h2.engine.Engine.createSessionAndValidate(Engine.java:153)
   at org.h2.engine.Engine.createSession(Engine.java:136)
   at org.h2.engine.Engine.createSession(Engine.java:28)
   at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:349)
   at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:107)
   at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:91)
   at org.h2.Driver.connect(Driver.java:72)
   at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:190)
   at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:353)
   at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:385)
   at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:227)
   at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:199)
   at nxt.db.BasicDb.init(BasicDb.java:134)
   ... 4 more
Caused by: java.lang.RuntimeException: page[1733662] data leaf table:121 T121 entries:8 parent:1769905 keys:[706193, 706194, 706195, 706196, 706197, 706198, 706199, 706200] offsets:[1809, 1570, 1331, 1086, 845, 606, 367, 137] parent 1769905 expected 1757962
   at org.h2.message.DbException.throwInternalError(DbException.java:242)
   at org.h2.index.PageDataIndex.getPage(PageDataIndex.java:245)
   at org.h2.index.PageDataNode.getLastKey(PageDataNode.java:214)
   at org.h2.index.PageDataNode.getLastKey(PageDataNode.java:214)
   at org.h2.index.PageDataNode.getLastKey(PageDataNode.java:214)
   at org.h2.index.PageDataIndex.<init>(PageDataIndex.java:86)
   at org.h2.table.RegularTable.<init>(RegularTable.java:83)
   at org.h2.store.PageStore.addMeta(PageStore.java:1696)
   at org.h2.store.PageStore.readMetaData(PageStore.java:1627)
   at org.h2.store.PageStore.recover(PageStore.java:1405)
   at org.h2.store.PageStore.openExisting(PageStore.java:367)
   at org.h2.store.PageStore.open(PageStore.java:288)
   at org.h2.engine.Database.getPageStore(Database.java:2474)
   at org.h2.engine.Database.open(Database.java:692)
   at org.h2.engine.Database.openDatabase(Database.java:270)
   ... 20 more
2016-03-15 19:03:02 INFO: Shutting down...
...
...
I guess that I can delete the blockchain and restart but perhaps it is usefull that I do nothing if some core dev wants to ask me to run some query in order to learn something out of it.
Title: Re: NRS v1.7.5
Post by: Jean-Luc on March 16, 2016, 10:17:33 am
It must be an internal H2 problem indeed. I can't make use of it, not worth keeping the corrupted db. For such cases, it is good to regularly backup and keep around a recent good copy of the nxt_db folder.
Title: Re: NRS v1.7.5
Post by: websioux on March 16, 2016, 02:27:35 pm
it is good to regularly backup and keep around a recent good copy of the nxt_db folder.
I'll program that, but if it is quite usefull it should become a setting...
Title: Re: NRS v1.7.5
Post by: ccat70541 on March 19, 2016, 04:10:11 am
Like the back button, and a button to switch accounts, so now it's easy. ;D ;D ;D ;D ;D ;D ;D ;D
Title: Re: NRS v1.7.5
Post by: Mara Edmund on March 22, 2016, 04:37:12 am
Thanks ;D
Title: Re: NRS v1.7.5
Post by: altsheets on March 22, 2016, 08:28:22 pm
it is good to regularly backup and keep around a recent good copy of the nxt_db folder.
I'll program that, but if it is quite usefull it should become a setting...

Good suggestions, both of them.
Title: Re: NRS v1.7.5
Post by: websioux on March 22, 2016, 08:53:22 pm
I've finally set up a loosy crontab :

0 1 10 * * cp -R /home/websioux/nxt/nxt_db /home/websioux/nxt_db_back

I don't know if it risks too loose consistency if I do not stop the server while I'm copying.

But my local node crashed too.. yesterday.. strange.. so I downloaded my VPS backup made from the above and... it worked !
So if your know how to set up a crontab (crontab -e  ;)), this simple copy paste can save you time.

Title: Re: NRS v1.7.5
Post by: Jean-Luc on March 22, 2016, 09:34:31 pm
The "backup" sql command http://www.h2database.com/html/grammar.html#backup is supposed to be transactionally safe, however I remember trying it once and intentionally doing a rescan or pop-off at the same time to put the db under heavy load, and it failed. But under normal use, may work.

Another trick would be to use rsync instead of cp, and do it twice, first while the server is running, then stop it, do a second rsync, and start it again. This should reduce the downtime, as the second rsync will have very few changes to copy.
Title: Re: NRS v1.7.5
Post by: martismartis on March 24, 2016, 03:12:28 pm
Have very strange behavior with NRS 1.7.5 on Ubuntu 15.10:
Everything was working fine, installed some ubuntu updates, restarted and started NRS again. Then I'm stuck for long time at:

2016-03-24 16:59:50 FINE: Database jdbc url set to jdbc:h2:./nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE;CACHE_SIZE=60416 username sa
2016-03-24 16:59:52 INFO: nxt.useStrongSecureRandom = "false"

PC do not show any activity during this and after hitting ctrl+c, everything starts moving on until Server 1.7.5 stopped.

nxt.log:

Code: [Select]
Initializing Nxt server version 1.7.5
isHeadless=false
Loading nxt-default.properties from classpath
Loading logging-default.properties from classpath
2016-03-24 16:59:49 INFO: nxt.enableStackTraces = "true"
2016-03-24 16:59:49 INFO: nxt.enableLogTraceback = "false"
2016-03-24 16:59:49 INFO: logging enabled
2016-03-24 16:59:49 INFO: socksProxyHost not defined
2016-03-24 16:59:49 INFO: socksProxyPort not defined
2016-03-24 16:59:49 FINE: java.version = 1.8.0_74
2016-03-24 16:59:49 FINE: java.vm.version = 25.74-b02
2016-03-24 16:59:49 FINE: java.vm.name = Java HotSpot(TM) Client VM
2016-03-24 16:59:49 FINE: java.vendor = Oracle Corporation
2016-03-24 16:59:49 FINE: java.vm.vendor = Oracle Corporation
2016-03-24 16:59:49 FINE: java.home = /usr/lib/jvm/java-8-oracle/jre
2016-03-24 16:59:49 FINE: java.library.path = /usr/java/packages/lib/i386:/lib:/usr/lib
2016-03-24 16:59:49 FINE: java.class.path = classes:lib/bcprov-jdk15on-154.jar:lib/core-3.2.1.jar:lib/h2-1.4.191.jar:lib/javase-3.2.1.jar:lib/javax.servlet-api-3.1.0.jar:lib/jetty-continuation-9.3.6.v20151106.jar:lib/jetty-http-9.3.6.v20151106.jar:lib/jetty-io-9.3.6.v20151106.jar:lib/jetty-security-9.3.6.v20151106.jar:lib/jetty-server-9.3.6.v20151106.jar:lib/jetty-servlet-9.3.6.v20151106.jar:lib/jetty-servlets-9.3.6.v20151106.jar:lib/jetty-util-9.3.6.v20151106.jar:lib/json-simple-1.1.1.jar:lib/lucene-analyzers-common-5.3.1.jar:lib/lucene-core-5.3.1.jar:lib/lucene-queries-5.3.1.jar:lib/lucene-queryparser-5.3.1.jar:lib/slf4j-api-1.7.13.jar:lib/slf4j-jdk14-1.7.13.jar:lib/tika-core-1.11.jar:lib/tika-parsers-1.11.jar:lib/websocket-api-9.3.6.v20151106.jar:lib/websocket-client-9.3.6.v20151106.jar:lib/websocket-common-9.3.6.v20151106.jar:lib/websocket-server-9.3.6.v20151106.jar:lib/websocket-servlet-9.3.6.v20151106.jar:lib/weupnp-0.1.4.jar:conf
2016-03-24 16:59:49 FINE: os.arch = i386
2016-03-24 16:59:49 FINE: sun.arch.data.model = 32
2016-03-24 16:59:49 FINE: os.name = Linux
2016-03-24 16:59:49 FINE: file.encoding = UTF-8
2016-03-24 16:59:49 FINE: nxt.runtime.mode = null
2016-03-24 16:59:49 FINE: availableProcessors = 1
2016-03-24 16:59:49 FINE: maxMemory = 259522560
2016-03-24 16:59:49 FINE: processId = 2409
2016-03-24 16:59:50 INFO: nxt.isTestnet = "false"
2016-03-24 16:59:50 INFO: nxt.isOffline = "false"
2016-03-24 16:59:50 INFO: nxt.maxRollback = "800"
2016-03-24 16:59:50 INFO: nxt.forgingDelay = "20"
2016-03-24 16:59:50 INFO: nxt.forgingSpeedup = "3"
2016-03-24 16:59:50 INFO: nxt.maxPrunableLifetime = "7776000"
2016-03-24 16:59:50 INFO: nxt.includeExpiredPrunable = "true"
2016-03-24 16:59:50 INFO: nxt.correctInvalidFees = "false"
2016-03-24 16:59:50 INFO: nxt.statementLogThreshold = "10000"
2016-03-24 16:59:50 INFO: nxt.transactionLogThreshold = "15000"
2016-03-24 16:59:50 INFO: nxt.transactionLogInterval = "15"
2016-03-24 16:59:50 INFO: nxt.dbCacheKB = "0"
2016-03-24 16:59:50 INFO: nxt.dbUrl not defined
2016-03-24 16:59:50 INFO: nxt.dbType = "h2"
2016-03-24 16:59:50 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-03-24 16:59:50 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-03-24 16:59:50 INFO: nxt.dbUsername = "sa"
2016-03-24 16:59:50 INFO: nxt.dbPassword = "{not logged}"
2016-03-24 16:59:50 INFO: nxt.maxDbConnections = "30"
2016-03-24 16:59:50 INFO: nxt.dbLoginTimeout = "70"
2016-03-24 16:59:50 INFO: nxt.dbDefaultLockTimeout = "60"
2016-03-24 16:59:50 FINE: Database jdbc url set to jdbc:h2:./nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE;CACHE_SIZE=60416 username sa
2016-03-24 16:59:52 INFO: nxt.useStrongSecureRandom = "false"
 ^C2016-03-24 17:08:45 INFO: Shutting down...
2016-03-24 17:08:45 INFO: nxt.adminPassword not defined
2016-03-24 17:08:45 INFO: nxt.maxAPIRecords = "100"
2016-03-24 17:08:45 INFO: nxt.enableAPIUPnP = "false"
2016-03-24 17:08:45 INFO: nxt.disabledAPIs not defined
2016-03-24 17:08:45 INFO: nxt.disabledAPITags not defined
2016-03-24 17:08:45 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-03-24 17:08:45 INFO: nxt.enableAPIServer = "true"
2016-03-24 17:08:45 INFO: nxt.apiServerPort = "7876"
2016-03-24 17:08:45 INFO: nxt.apiServerSSLPort = "7876"
2016-03-24 17:08:45 INFO: nxt.apiServerHost = "127.0.0.1"
2016-03-24 17:08:45 INFO: nxt.disableAdminPassword = "false"
2016-03-24 17:08:46 INFO: nxt.apiSSL = "false"
2016-03-24 17:08:46 INFO: nxt.apiServerIdleTimeout = "30000"
2016-03-24 17:08:46 INFO: API server using HTTP port 7876
2016-03-24 17:08:47 INFO: nxt.apiResourceBase = "html/ui"
2016-03-24 17:08:47 INFO: nxt.apiWelcomeFile = "index.html"
2016-03-24 17:08:47 INFO: nxt.javadocResourceBase = "html/doc"
2016-03-24 17:08:47 INFO: nxt.maxUploadFileSize not defined or not numeric, using default value 0
2016-03-24 17:08:47 INFO: nxt.enableAPIServerGZIPFilter = "false"
2016-03-24 17:08:48 INFO: nxt.apiServerCORS = "false"
2016-03-24 17:08:48 INFO: nxt.apiFrameOptionsSameOrigin = "true"
2016-03-24 17:08:48 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-03-24 17:08:48 INFO: nxt.enableUIServer = "false"
2016-03-24 17:08:48 INFO: User interface server not enabled
2016-03-24 17:08:48 INFO: nxt.hideErrorDetails = "false"
2016-03-24 17:08:48 INFO: nxt.myPlatform = "PC"
2016-03-24 17:08:48 INFO: nxt.myAddress not defined
2016-03-24 17:08:48 INFO: nxt.peerServerPort = "7874"
2016-03-24 17:08:48 INFO: nxt.shareMyAddress = "true"
2016-03-24 17:08:48 INFO: nxt.enablePeerUPnP = "true"
2016-03-24 17:08:48 INFO: nxt.myHallmark not defined
2016-03-24 17:08:48 FINE: My peer info:
{"application":"NRS","services":"0","version":"1.7.5","platform":"PC","shareAddress":true}
2016-03-24 17:08:48 INFO: nxt.defaultPeers = "bug.airdns.org; 93.208.212.137; nxt6.y.cz; 104.193.41.253; 37.139.5.199; 109.230.224.89; 70.106.182.230; 77.144.105.130; 78.62.219.252; 68.168.161.160; 78.46.233.109; 120.25.65.184; nxt.cryonet.de; 111.192.141.164; 98.245.11.138; 100.34.247.56; 85.10.201.15; 05.zapto.org; 158.69.33.172; 78.47.58.62; 144.76.3.50; 192.99.77.148; 90.153.107.93; 76.79.201.54; 5.9.149.197; 81.2.103.237; 92.222.65.40; nxt4.y.cz; 178.62.225.240; 85.25.198.120; 185.99.132.54; 89.212.19.49; nxt01.now.im; nrs.scripterron.org; 175.156.85.245; 62.227.10.194; 73.40.166.72; 217.23.6.2; 73.40.166.127; 174.140.167.239; 52.79.46.24; 162.243.242.8; gunka.szn.dk; 128.199.46.72; 101.100.175.48; 76.176.202.107; 69.163.40.132; 192.0.226.19; 100.13.33.13; 94.227.33.223; 90.75.247.40; raspi2nxtnode.ddns.net; nxt-001.nodes.be; 83.83.161.46; 91.121.150.75; nxt3.y.cz; 80.153.101.190; 95.215.47.221; 86.206.97.98; 78.47.115.250; 52.29.122.21; nxt.sx; nxt.cybermailing.com; 5.230.145.165; 70.31.212.252; 188.243.4.139; 128.199.189.226; nxt.scriba.io; 174.17.156.59; 80.150.243.96; 51.254.99.240; pakisnxt.no-ip.org; enricoip.no-ip.biz; 50.27.137.177; 80.150.243.99; 211.149.213.86; 176.97.2.179; 198.46.193.111; 80.150.243.12; 176.9.138.21; 80.150.243.13; f376.ddns.net; 61.120.160.90; 52.28.97.208; 5.9.180.173; 77.123.252.71; 93.211.251.105; 79.159.11.14; 96.255.76.163; langust.ddns.net; 73.50.115.206; 66.215.60.93; 69.137.154.114; 103.250.83.112; 46.101.112.58; 71.170.34.26; 176.97.2.141; nxt1.testdruif.be; home.kaerner.net; nxt.bened.de; 78.46.160.9; 162.243.122.251; 178.15.99.67; 78.46.49.59:4509; 93.219.103.107; 78.63.207.76; 198.211.127.34; 5.9.155.145; nxt.ydns.eu; 87.138.143.21; 77.152.74.54; 198.199.95.15; 46.223.83.130; 103.250.83.127; 91.210.188.6; 87.139.122.48; nxt1.y.cz; 113.106.85.172; 37.97.136.254; 87.139.122.157; 94.102.50.75; 70.189.162.138; 79.167.162.77; ct.flipflop.mooo.com; 51.255.149.237; 174.91.212.242; petko.ddns.net; 181.47.183.188; 93.75.9.10; 176.94.115.161; 91.235.72.49; 71.60.182.55; nxtcoin.no-ip.org; 91.239.69.78; 2.218.35.177; 46.4.74.71; 162.243.145.83; 94.102.50.68; 14.200.253.61; nxtpeers.com; 192.3.196.10; 80.98.81.73; nxt2.testdruif.be; 77.88.208.12; 84.252.21.155; 158.69.194.254; 23.94.134.161; 96.236.141.73; 142.4.218.174; 72.182.27.227; 178.33.203.157; nxt.noip.me; 176.31.167.127; sluni.szn.dk; 198.27.81.25; 216.119.150.238; 71.218.89.236; 190.10.9.166; 166.48.75.119; megaman.thican.net; 88.163.78.131; 132.230.76.160; 54.213.222.141; humanoide.thican.net; 106.187.102.227; 96.236.143.175; 217.26.24.27; 184.191.182.165; 52.0.72.67; 104.130.7.74; 62.85.20.37; 82.165.138.42;"
2016-03-24 17:08:48 INFO: nxt.wellKnownPeers not defined
2016-03-24 17:08:48 INFO: nxt.knownBlacklistedPeers not defined
2016-03-24 17:08:48 INFO: nxt.maxNumberOfInboundConnections = "250"
2016-03-24 17:08:48 INFO: nxt.maxNumberOfOutboundConnections = "50"
2016-03-24 17:08:48 INFO: nxt.maxNumberOfConnectedPublicPeers = "20"
2016-03-24 17:08:48 INFO: nxt.maxNumberOfKnownPeers = "2000"
2016-03-24 17:08:48 INFO: nxt.minNumberOfKnownPeers = "1000"
2016-03-24 17:08:48 INFO: nxt.connectTimeout = "10000"
2016-03-24 17:08:48 INFO: nxt.readTimeout = "20000"
2016-03-24 17:08:48 INFO: nxt.enableHallmarkProtection = "true"
2016-03-24 17:08:48 INFO: nxt.pushThreshold = "0"
2016-03-24 17:08:48 INFO: nxt.pullThreshold = "0"
2016-03-24 17:08:48 INFO: nxt.useWebSockets = "true"
2016-03-24 17:08:48 INFO: nxt.webSocketIdleTimeout = "900000"
2016-03-24 17:08:48 INFO: nxt.enablePeerServerGZIPFilter = "true"
2016-03-24 17:08:48 INFO: nxt.blacklistingPeriod = "600000"
2016-03-24 17:08:48 INFO: nxt.communicationLoggingMask = "0"
2016-03-24 17:08:48 INFO: nxt.sendToPeersLimit = "10"
2016-03-24 17:08:48 INFO: nxt.usePeersDb = "true"
2016-03-24 17:08:48 INFO: nxt.savePeers = "true"
2016-03-24 17:08:48 INFO: nxt.getMorePeers = "true"
2016-03-24 17:08:48 INFO: nxt.cjdnsOnly = "false"
2016-03-24 17:08:48 INFO: nxt.ignorePeerAnnouncedAddress = "false"
2016-03-24 17:08:50 INFO: nxt.trimDerivedTables = "true"
2016-03-24 17:08:50 INFO: nxt.numberOfForkConfirmations = "2"
2016-03-24 17:08:50 INFO: nxt.trimFrequency = "1000"
2016-03-24 17:08:50 INFO: nxt.disableGetMoreBlocksThread not defined, assuming false
2016-03-24 17:08:50 INFO: nxt.enablePublicKeyCache = "true"
2016-03-24 17:08:50 INFO: nxt.disablePeerConnectingThread not defined, assuming false
2016-03-24 17:08:50 INFO: nxt.disablePeerUnBlacklistingThread not defined, assuming false
2016-03-24 17:08:50 INFO: nxt.disableGetMorePeersThread not defined, assuming false
2016-03-24 17:08:50 INFO: nxt.peerServerHost = "0.0.0.0"
2016-03-24 17:08:50 INFO: nxt.peerServerIdleTimeout = "30000"
2016-03-24 17:08:51 INFO: nxt.enablePeerServerDoSFilter = "true"
2016-03-24 17:08:51 INFO: nxt.peerServerDoSFilter.maxRequestsPerSec = "30"
2016-03-24 17:08:51 INFO: nxt.peerServerDoSFilter.delayMs = "1000"
2016-03-24 17:08:51 INFO: nxt.peerServerDoSFilter.maxRequestMs = "300000"
2016-03-24 17:08:51 INFO: shutting down sendingService
2016-03-24 17:08:51 INFO: shutting down peersService
2016-03-24 17:08:51 INFO: Nxt server 1.7.5 stopped.




Title: Re: NRS v1.7.5
Post by: Jean-Luc on March 24, 2016, 04:05:22 pm
Just after the secureRandom log message is the time when the H2 db initializes. Sometimes it takes its time to do some internal processing or cleanup on startup. Or it could have just deadlocked, if neither CPU nor disk activity was present.
Title: Re: NRS v1.7.5
Post by: martismartis on March 24, 2016, 04:26:13 pm
Just after the secureRandom log message is the time when the H2 db initializes. Sometimes it takes its time to do some internal processing or cleanup on startup. Or it could have just deadlocked, if neither CPU nor disk activity was present.

Well, after some long time it continued to load, but with a lot Input/output errors and nxt.h2.db became 5.2GB. Seems I need to download blockchain from the start.
Title: Re: NRS v1.7.5
Post by: Riker on March 24, 2016, 04:32:41 pm
@martismartis in case this happens again, take a thread dump either using the
Code: [Select]
jstack <pid> utility or using the
Code: [Select]
kill -3 <pid> command.
Post here the resulting thread dump so we can get an idea which thread is blocked.
Title: Re: NRS v1.7.5
Post by: void on March 28, 2016, 05:59:29 pm
Can I join to bitbucket to create Polish translation for NXT?
Title: Re: NRS v1.7.5
Post by: NxtSwe on March 28, 2016, 06:39:36 pm
Would it be possible for those with a stake on testnet to get back to forging?
Last block was generated 8 hours ago on 1.7.5 chain (I see two 1.8.0e nodes, maybe we forked the net?).

Thanx!
Title: Re: NRS v1.7.5
Post by: EvilDave on March 28, 2016, 07:30:23 pm
Just spun up my testNxt node and put one million testNXT to work.
Looks like I'm getting all the blocks.... :D
Title: Re: NRS v1.7.5
Post by: NxtSwe on March 28, 2016, 07:50:33 pm
Just spun up my testNxt node and put one million testNXT to work.
Looks like I'm getting all the blocks.... :D

Dank je!
Title: Re: NRS v1.7.5
Post by: Riker on March 28, 2016, 08:15:57 pm
Can I join to bitbucket to create Polish translation for NXT?

Please create an account on crowdin.com and PM me your username. I'll get you in contact with the admin.
Title: Re: NRS v1.7.5
Post by: allwelder on March 28, 2016, 10:36:59 pm
Can I join to bitbucket to create Polish translation for NXT?

Please create an account on crowdin.com and PM me your username. I'll get you in contact with the admin.
@void
You can also find detailed info here:
https://nxtforum.org/core-development-discussion/(client-translation)-nrs-1-7-4-ui-translation-with-bounty/ (https://nxtforum.org/core-development-discussion/(client-translation)-nrs-1-7-4-ui-translation-with-bounty/)
Title: Re: NRS v1.7.5
Post by: ScripterRon on March 29, 2016, 02:34:19 pm
Would it be possible for those with a stake on testnet to get back to forging?
Last block was generated 8 hours ago on 1.7.5 chain (I see two 1.8.0e nodes, maybe we forked the net?).

Thanx!
There shouldn't be a fork.  My node is 1.8.0e but I'm seeing blocks generated by several different users.  The block at height 650364 is 11552682360036847110.  Does this match what you see?
Title: Re: NRS v1.7.5
Post by: abctc on March 29, 2016, 02:37:33 pm
The block at height 650364 is 11552682360036847110. 
- I can confirm this.
Title: Re: NRS v1.7.5
Post by: Tosch110 on March 31, 2016, 01:50:55 pm
I am reporting this because it told me to:

Code: [Select]
Initializing Nxt server version 1.7.5

[...]

Exception in thread "qtp936653983-62325" java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at org.eclipse.jetty.util.thread.QueuedThreadPool.startThreads(QueuedThreadPool.java:462)
at org.eclipse.jetty.util.thread.QueuedThreadPool.access$200(QueuedThreadPool.java:47)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:639)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "qtp1816725203-62345" java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at org.eclipse.jetty.util.thread.QueuedThreadPool.startThreads(QueuedThreadPool.java:462)
at org.eclipse.jetty.util.thread.QueuedThreadPool.access$200(QueuedThreadPool.java:47)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:639)
at java.lang.Thread.run(Thread.java:745)
2016-03-29 22:58:36 FINE: Peer 31.128.67.247 version 1.7.5 returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"announcedAddress":"NxtPeers.com","application":"NRS","requestType":"getInfo","services":"0","version":"1.7.5","platform":"Awesome","shareAddress":true}, disconnecting
2016-03-29 23:07:16 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368)
at nxt.util.QueuedThreadPool.execute(QueuedThreadPool.java:112)
at nxt.util.QueuedThreadPool.submit(QueuedThreadPool.java:131)
at nxt.peer.Peers$2.lambda$run$113(Peers.java:524)
at nxt.peer.Peers$2$$Lambda$69/1051166413.accept(Unknown Source)
at java.util.concurrent.ConcurrentHashMap$ValuesView.forEach(ConcurrentHashMap.java:4707)
at nxt.peer.Peers$2.run(Peers.java:520)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Title: Re: NRS v1.7.5
Post by: HCLivess on April 06, 2016, 04:37:24 pm
My client is rolling back since yesterday, updating to 1.8 now
elective-stereophonic
elective-stereophonic
assembly
assembly