Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on December 07, 2015, 07:05:30 pm

Title: NRS v1.7.2e
Post by: Jean-Luc on December 07, 2015, 07:05:30 pm
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.7.2e

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

sha256:

86e7cd23939765a3525d1f3e6c61a52e6427177f66e8abf94db7b7d4dceaf1f3  nxt-client-1.7.2e.zip

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

sha256:

660bd0130d5c7d092431dc85b00eb98482c63203e48e3a86d84bf927eedce0f2  nxt-client-1.7.2e.jar

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

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


This is an experimental release for testing only. Source code is not provided.


Change log:

This is an experimental bugfix release. It is a mandatory update for testnet
nodes.

Accounts under phasing only control are not allowed to create or join
shufflings, or start shufflers.

Shuffling UI improvements. The My Shufflers page has been merged with
My Shufflings.

Added includeParticipantState parameter to getShufflers, to allow retrieving
shuffling participant state too with the same request.

The deleteAccountProperty API has been fixed to accept both recipient and
setter parameters, to be able to delete properties set to the account by
another account.

For consistency with setAccountProperty and deleteAccountProperty, the
getAccountProperties API account parameter has been renamed to recipient.
The account owner is also identified as recipient in the JSON fields of
the properties returned.

Added getAvailableToBuy and getAvailableToSell Monetary System APIs, to allow
calculating the rate required in order to completely fill an exchange request,
or the maximum available currency units or NXT amount considering the current
market offers.

Added Account Properties UI.

Account Control UI improvements and bugfixes.

This release will do a blockchain rescan on testnet only, deleting blocks
after height 484310.


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

iQIcBAEBCgAGBQJWZc/AAAoJENqvaxkWiP4Z3+AQAOgp4W3LaztnVM72l3QhGYa6
NCdlVNPYQxJI1EKaYLSQhTwpzWBvY2SZ+P7Z67a0W0Er5svqg0AZ0oGM7Tbp4m7U
bz0gM0sWwxffn5ccLe1AdSniw2pGJLfLQhrtlJmDzCJsUSMuDhdzZ3J4cxb9ehIH
3bDXhVLtOLOoSJiIAJ0dHfzKxvBWjF7UJUNABu27Ljj/pgeyv4t3Q2P0JcHQedIX
O/E737tDdTx7aDMypqceTGJhRDRbSlIQ3z/TpacATVOdVF+WHhbUSiquiRF8rvXa
7hidBYxm/yMGm4U3DojDLQTlilixwEo+1/zknpj3fA2tfbObJMnCsRbE2icmGH2B
Dx74RZUxtKG4ohroysyS70kinYOWYMx3PAjIWrCmR1GLur3CrynxQACmgwbNxCOk
HnOtnaYDY8A0PnzBgQBeqq/uvn8nAFYe70N+4fggc7bJBz9QxpRlQ+WC0ahQCLob
eruJc2UqeIaZ0PgM9aJsP4LaVyyrl3MU+vLNNPuJQ0rOAuACYqpg0Kf1K4Edmkot
won/OYykl4KvSCjHBtxVlXsvL7THRo2Um1IXw3vcLUWu+XnOm5BntOhWOtHUN+AY
AtIVlLWC3zC4mZk928+KKBz19PCqG6chjmWhrCgOu0LLRqm/AgmJpnKphvPlKcgE
3D29f/yMEKuHki1Jp3H2
=73e9
-----END PGP SIGNATURE-----
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 07, 2015, 07:08:32 pm
Note that this release will delete the blocks from the last few days on testnet and cause a fork there. There will be errors in the log and blacklisting of 1.7.1e and older peers, until they also move to 1.7.2e.
Title: Re: NRS v1.7.2e
Post by: qq2536007339 on December 08, 2015, 01:21:29 am
Thanks,updated.Too bad I lost a payment after height 484310.
Title: Re: NRS v1.7.2e
Post by: abctc on December 08, 2015, 09:57:46 am
Can not update my successfull 1.7.1e testNET VPS to 1.7.2e:

Code: [Select]
....
2015-12-08 00:43:14 FINE: Poll 5819406515142809241 has been finished
2015-12-08 00:43:17 FINE: Poll 2354938103242688579 has been finished
2015-12-08 00:43:20 INFO: processed block 450000
2015-12-08 00:43:23 INFO: Checksum passed at block 450000
2015-12-08 00:43:34 INFO: processed block 455000
2015-12-08 00:43:46 INFO: processed block 460000
2015-12-08 00:43:58 INFO: processed block 465000
2015-12-08 00:44:03 FINE: Transaction 10653334928549547241 has been rejected
2015-12-08 00:44:03 FINE: Transaction 1610338497170730905 has been released
2015-12-08 00:44:11 INFO: processed block 470000
2015-12-08 00:44:22 FINE: Transaction 152360589446582252 has been released
2015-12-08 00:44:22 FINE: Transaction 9470148039833812593 has been released
2015-12-08 00:44:22 INFO: processed block 475000
2015-12-08 00:44:33 INFO: processed block 480000
2015-12-08 00:44:41 FINE: Transaction 6740668935534210079 has been rejected
2015-12-08 00:44:41 FINE: Transaction 13044877526374043292 has been released
2015-12-08 00:44:41 FINE: Early finish of transaction 13044877526374043292 at height 483142
2015-12-08 00:44:41 FINE: Transaction 1078542203852326466 has been released
2015-12-08 00:44:41 FINE: Early finish of transaction 1078542203852326466 at height 483155
2015-12-08 00:44:41 FINE: Shuffling 6846283040177340533 entered stage PROCESSING, assignee 5873880488492319831, remaining
2015-12-08 00:44:41 FINE: Participant 5873880488492319831 did not submit processing
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483166
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483165
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483164
2015-12-08 00:44:41 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483167
2015-12-08 00:44:41 FINE: Shuffling 6846283040177340533 entered stage CANCELLED, assignee 5873880488492319831, remaining
2015-12-08 00:44:41 FINE: Shuffling 6846283040177340533 was cancelled, blaming account 5873880488492319831
2015-12-08 00:44:41 FINE: Transaction 6130108325828118580 has been rejected
2015-12-08 00:44:42 FINE: Transaction 8431880759533023599 has been released
2015-12-08 00:44:42 FINE: Early finish of transaction 8431880759533023599 at height 483252
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 entered stage PROCESSING, assignee 5873880488492319831, remainin
2015-12-08 00:44:42 FINE: Shuffling participant 5873880488492319831 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 17158652599359757654 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 5183642564593472619 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 12745647715474645062 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 16992224448242675179 changed state to PROCESSED
2015-12-08 00:44:42 FINE: Shuffling participant 16992224448242675179 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 entered stage VERIFICATION, assignee 0, remaining blocks 15
2015-12-08 00:44:42 FINE: Shuffling participant 17158652599359757654 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling participant 5873880488492319831 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling participant 12745647715474645062 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling participant 5183642564593472619 changed state to VERIFIED
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 entered stage DONE, assignee 0, remaining blocks 0
2015-12-08 00:44:42 FINE: Shuffling 17626955119804441745 was distributed
2015-12-08 00:44:43 FINE: Registration never completed for shuffling 12715834022325590208
2015-12-08 00:44:43 FINE: Shuffling 12715834022325590208 entered stage CANCELLED, assignee 0, remaining blocks 0
2015-12-08 00:44:43 FINE: Shuffling 12715834022325590208 was cancelled, blaming account 0
2015-12-08 00:44:44 FINE: Shuffling 18010187208323581708 entered stage PROCESSING, assignee 6033326673854333936, remainin
2015-12-08 00:44:44 FINE: Participant 6033326673854333936 did not submit processing
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483648
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483647
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483646
2015-12-08 00:44:44 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 483649
2015-12-08 00:44:44 FINE: Shuffling 18010187208323581708 entered stage CANCELLED, assignee 6033326673854333936, remaining
2015-12-08 00:44:44 FINE: Shuffling 18010187208323581708 was cancelled, blaming account 6033326673854333936
2015-12-08 00:44:48 INFO: Checksum passed at block 484000
2015-12-08 00:44:48 FINE: Registration never completed for shuffling 2116146789204042375
2015-12-08 00:44:48 FINE: Shuffling 2116146789204042375 entered stage CANCELLED, assignee 0, remaining blocks 0
2015-12-08 00:44:48 FINE: Shuffling 2116146789204042375 was cancelled, blaming account 0
2015-12-08 00:44:49 FINE: Transaction 17632403758298131653 has been released
2015-12-08 00:44:49 FINE: Transaction 10282165754252393729 has been released
2015-12-08 00:44:49 FINE: Shuffling 17066004119398550389 entered stage PROCESSING, assignee 9107471420880698254, remainin
2015-12-08 00:44:49 FINE: Participant 9107471420880698254 did not submit processing
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484126
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484125
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484124
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484127
2015-12-08 00:44:49 FINE: Shuffling 17066004119398550389 entered stage CANCELLED, assignee 9107471420880698254, remaining
2015-12-08 00:44:49 FINE: Shuffling 17066004119398550389 was cancelled, blaming account 9107471420880698254
2015-12-08 00:44:49 FINE: Shuffling 11883961883981516616 entered stage PROCESSING, assignee 9107471420880698254, remainin
2015-12-08 00:44:49 FINE: Participant 9107471420880698254 did not submit processing
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484211
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484210
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484209
2015-12-08 00:44:49 FINE: Shuffling penalty 1.750000 NXT awarded to forger at height 484212
2015-12-08 00:44:49 FINE: Shuffling 11883961883981516616 entered stage CANCELLED, assignee 9107471420880698254, remaining
2015-12-08 00:44:49 FINE: Shuffling 11883961883981516616 was cancelled, blaming account 9107471420880698254
2015-12-08 00:44:50 FINE: Transaction 14071447012335411688 has been released
2015-12-08 00:44:50 FINE: Early finish of transaction 14071447012335411688 at height 484290
2015-12-08 00:44:50 FINE: nxt.de: Invalid max fees 10.000000 NXT, block 17473766081329873540 {"totalFeeNQT":100000000,"pr
nxt.de: Invalid max fees 10.000000 NXT, block 17473766081329873540 {"totalFeeNQT":100000000,"previousBlockHash":"b5cd960c
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.a(Unknown Source)
<------>at nxt.df.r(Unknown Source)
<------>at nxt.df$$Lambda$9/587153993.run(Unknown Source)
<------>at nxt.util.v$2.run(Unknown Source)
2015-12-08 00:44:50 FINE: Applying block 17473766081329873540 at height 484310 failed, deleting from database
2015-12-08 00:44:56 FINE: Rollback from block 11946872595449040309 at height 484309 to 11946872595449040309 at 484309
2015-12-08 00:44:56 FINE: Creating search index on account_info (name,description)
2015-12-08 00:44:56 INFO: Lucene search index created for table PUBLIC.ACCOUNT_INFO
2015-12-08 00:44:56 FINE: Creating search index on asset (name,description)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.ASSET
2015-12-08 00:44:57 FINE: Creating search index on goods (name,description,tags)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.GOODS
2015-12-08 00:44:57 FINE: Creating search index on poll (name,description)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.POLL
2015-12-08 00:44:57 FINE: Creating search index on currency (code,name,description)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.CURRENCY
2015-12-08 00:44:57 FINE: Creating search index on tagged_data (name,description,tags)
2015-12-08 00:44:57 INFO: Lucene search index created for table PUBLIC.TAGGED_DATA
2015-12-08 00:45:03 INFO: ...done at height 484309
2015-12-08 00:45:03 INFO: SUCCESSFULLY PERFORMED FULL RESCAN WITH VALIDATION
2015-12-08 00:45:03 FINE: Database transaction required 1465.187 seconds at height 484309
  nxt.df.a(Unknown Source)
  nxt.df.a(Unknown Source)
  nxt.df.r(Unknown Source)
  nxt.df$$Lambda$9/587153993.run(Unknown Source)
  nxt.util.v$2.run(Unknown Source)
2015-12-08 00:45:03 FINE: Running 2 final tasks...
2015-12-08 00:45:03 INFO: Looking for UPnP gateway device...
2015-12-08 00:45:03 INFO: nxt.upnpGatewayTimeout not defined or not numeric, using default value 7000
2015-12-08 00:45:03 INFO: nxt.upnpDiscoverTimeout not defined or not numeric, using default value 3000
2015-12-08 00:45:03 FINE: There are no UPnP gateway devices
2015-12-08 00:45:03 INFO: Started peer networking server at 0.0.0.0:6874
2015-12-08 00:45:03 INFO: Started API server at 0.0.0.0:6876, 0.0.0.0:6877
2015-12-08 00:45:03 FINE: Starting 9 background jobs
2015-12-08 00:45:03 FINE: Starting 2 delayed tasks
2015-12-08 00:45:04 FINE: Known peers: 7
2015-12-08 00:45:04 INFO: Initialization took 1470 seconds
2015-12-08 00:45:04 INFO: Nxt server 1.7.2e started successfully.
2015-12-08 00:45:04 INFO: Copyright ? 2013-2015 The Nxt Core Developers.
2015-12-08 00:45:04 INFO: THIS IS AN EXPERIMENTAL RELEASE!
2015-12-08 00:45:04 INFO: Client UI is at https://localhost:6877/index.html
2015-12-08 00:45:04 INFO: RUNNING ON TESTNET - DO NOT USE REAL ACCOUNTS!
2015-12-08 00:45:07 FINE: Average database transaction time is 0.070 seconds
2015-12-08 00:45:07 FINE: Poll 1947826240325430239 has been finished
2015-12-08 00:45:08 FINE: Transaction 13932930154345407092 has been released
2015-12-08 00:45:08 FINE: Transaction 18220658706250640101 has been released
2015-12-08 00:45:10 INFO: Blockchain download in progress
2015-12-08 00:45:10 FINE: Got 1 confirmations
2015-12-08 00:45:10 INFO: Downloaded 655 blocks in 5 s, 113 per s, 0 min left
2015-12-08 00:45:12 INFO: Finished blockchain download
2015-12-08 00:45:12 FINE: Connected to archive peer 178.150.207.53
2015-12-08 00:45:12 FINE: Need to restore 2 pruned data
2015-12-08 00:45:12 FINE: Done retrieving prunable transactions from 178.150.207.53
2015-12-08 00:45:12 FINE: Remaining 2 pruned transactions
2015-12-08 00:46:31 FINE: GetInfo: peer 119.81.29.172 changed announced address from null to 119.81.29.172
2015-12-08 00:46:31 FINE: Blacklisting 119.81.29.172 version 1.5.12
2015-12-08 00:46:46 FINE: GetInfo: peer 40.115.9.93 changed announced address from null to nxtclient1.cloudapp.net
2015-12-08 00:46:46 FINE: Blacklisting 40.115.9.93 version 1.5.15
2015-12-08 00:48:17 FINE: GetInfo: peer 5.146.64.45 changed announced address from null to raspnxt.hopto.org
2015-12-08 00:48:17 FINE: Blacklisting 5.146.64.45 version 1.6.2
2015-12-08 00:49:25 FINE: GetInfo: peer 37.139.6.166 changed announced address from null to 37.139.6.166
2015-12-08 00:49:25 FINE: Blacklisting 37.139.6.166 version 1.5.12
2015-12-08 00:53:09 FINE: Blacklisting 54.165.215.68 version 1.6.2
2015-12-08 00:55:01 FINE: GetInfo: peer 5.196.72.29 changed announced address from null to 5.196.72.29
2015-12-08 00:55:01 FINE: Blacklisting 5.196.72.29 version 1.5.12
2015-12-08 00:57:12 FINE: Database connection pool current size: 3
2015-12-08 00:57:12 FINE: Database connection pool current size: 4
2015-12-08 00:57:19 FINE: Database connection pool current size: 5
2015-12-08 00:57:19 FINE: Database connection pool current size: 6
2015-12-08 00:57:34 FINE: Database connection pool current size: 7
2015-12-08 00:57:34 FINE: Database connection pool current size: 8
2015-12-08 01:01:11 FINE: Average database transaction time is 0.005 seconds
2015-12-08 01:17:28 FINE: Average database transaction time is 0.006 seconds
2015-12-08 01:20:26 INFO: received block 485000
2015-12-08 01:32:34 FINE: Average database transaction time is 0.358 seconds
2015-12-08 01:34:19 INFO: Shutting down...
2015-12-08 01:34:19 INFO: Stopping background jobs...
2015-12-08 01:34:19 INFO: shutting down scheduledThreadPool
2015-12-08 01:34:19 INFO: ...Done
2015-12-08 01:34:19 INFO: shutting down sendingService
2015-12-08 01:34:19 INFO: shutting down peersService
2015-12-08 01:34:21 INFO: Database shutdown completed
2015-12-08 01:34:21 INFO: Nxt server 1.7.2e stopped.
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 08, 2015, 11:17:26 am
Why, this looks normal to me. It has deleted blocks after 484310, then downloaded the new blocks forged since yesterday, and passed block 485000.
Title: Re: NRS v1.7.2e
Post by: abctc on December 08, 2015, 11:26:22 am
Why
- I'm wondering too.

this looks normal to me. It has deleted blocks after 484310, then downloaded the new blocks forged since yesterday, and passed block 485000.
- yes, and then all of a sudden:
Quote
2015-12-08 01:20:26 INFO: received block 485000
2015-12-08 01:32:34 FINE: Average database transaction time is 0.358 seconds
2015-12-08 01:34:19 INFO: Shutting down...
2015-12-08 01:34:19 INFO: Stopping background jobs...
2015-12-08 01:34:19 INFO: shutting down scheduledThreadPool
2015-12-08 01:34:19 INFO: ...Done
2015-12-08 01:34:19 INFO: shutting down sendingService
2015-12-08 01:34:19 INFO: shutting down peersService
2015-12-08 01:34:21 INFO: Database shutdown completed
2015-12-08 01:34:21 INFO: Nxt server 1.7.2e stopped.
- why...
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 08, 2015, 11:30:51 am
Unless it ran out of memory, because of the rescan, but shutting down without any error message is still unusual.
Title: Re: NRS v1.7.2e
Post by: phideas on December 08, 2015, 01:03:39 pm
Small UI quirk: When approval request disappear from the list, the counter badge stay still there on left menu item.
Title: Re: NRS v1.7.2e
Post by: phideas on December 08, 2015, 03:11:42 pm
Still not happy with AC. It is not fool proof enough IMO. Imagine the most common usecase will be probably voting by accounts.
Now if user forget to type in the account id and will send an empty whitelist he is locked out with no way of recovery. (am i right here?)
Maybe checking for existing accounts and pubkeys in whitelist (as it is done already elswhere) could be a nice improvements towards more safety.
Is it possible to implement?

EDIT: Here is NXT-APNQ-LRZS-6JJK-2B85Q locked out becuse of empty whitelist. Is it possible to remove AC in this case?
Title: Re: NRS v1.7.2e
Post by: Riker on December 08, 2015, 03:22:37 pm
Why
- I'm wondering too.

this looks normal to me. It has deleted blocks after 484310, then downloaded the new blocks forged since yesterday, and passed block 485000.
- yes, and then all of a sudden:
Quote
2015-12-08 01:20:26 INFO: received block 485000
2015-12-08 01:32:34 FINE: Average database transaction time is 0.358 seconds
2015-12-08 01:34:19 INFO: Shutting down...
2015-12-08 01:34:19 INFO: Stopping background jobs...
2015-12-08 01:34:19 INFO: shutting down scheduledThreadPool
2015-12-08 01:34:19 INFO: ...Done
2015-12-08 01:34:19 INFO: shutting down sendingService
2015-12-08 01:34:19 INFO: shutting down peersService
2015-12-08 01:34:21 INFO: Database shutdown completed
2015-12-08 01:34:21 INFO: Nxt server 1.7.2e stopped.
- why...

Perhaps you were running on a Linux VPS without specifying the nohup command ?
This would (under certain conditions) trigger the Java shutdown hook whenever you logout or when your terminal session times out.
Title: Re: NRS v1.7.2e
Post by: Riker on December 08, 2015, 03:29:01 pm
Is anyone else getting heavy CPU loading? It maxes out a core in Firefox and I traced it to Lastpass add-on. Then I installed Chromium and it seemed better. Today I'm shuffling on testnet in Chromium and it's giving spurious CPU loads of roughly 50%, one core at a time. I'm not using any plugins in Chromium and have a pretty decent processor (4200M) and SSD so it should not be anywhere near 50%. Maybe there's something wrong with my Java installation? When I close Chromium and leave NRS running the CPU goes back to a trickle, so I think it's UI related.

Edit: It seems to have stopped doing it now. Aaaaargh! I don't know why this is happening!

P.S.: Possible rogue process that gets called by the UI when initiating a shuffle? It did stop as soon as I closed Chromium after starting a shuffle and now that I have opened Chromium again just to view my shuffle it is playing nice.

The first thing to test would be who is consuming the CPU the wallet running in the browser or the server.
What happens if you connect using the same browser to a remote node (PM me if you need a VPS node to connect to), do you still see the CPU spikes ?
If you do, then this is a client side issue. If you don't this is a server side issue.
The methods to diagnose server CPU spikes are different than the methods to diagnose client side CPU spikes so this should be the first thing to figure out.
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 08, 2015, 03:37:25 pm
Still not happy with AC. It is not fool proof enough IMO. Imagine the most common usecase will be probably voting by accounts.
Now if user forget to type in the account id and will send an empty whitelist he is locked out with no way of recovery. (am i right here?)
Maybe checking for existing accounts and pubkeys in whitelist (as it is done already elswhere) could be a nice improvements towards more safety.
Is it possible to implement?

EDIT: Here is NXT-APNQ-LRZS-6JJK-2B85Q locked out becuse of empty whitelist. Is it possible to remove AC in this case?
Empty whitelist means any account can approve the transaction. While not very useful, this is allowed. You should be able to create an account control transaction removing the control, and then approve it using either this, or any other account.
Phasing using by-account with empty whitelist however is executed at finish height only, early release of such transactions is not supported. Meaning you will have to wait until finish height for the change to take effect, after the approval.
Title: Re: NRS v1.7.2e
Post by: CryptKeeper on December 08, 2015, 04:19:32 pm
GUI refresh issue:

after approving still showing "Dashboard/Approval Requests (1)".
Title: Re: NRS v1.7.2e
Post by: phideas on December 08, 2015, 05:47:21 pm
Still not happy with AC. It is not fool proof enough IMO. Imagine the most common usecase will be probably voting by accounts.
Now if user forget to type in the account id and will send an empty whitelist he is locked out with no way of recovery. (am i right here?)
Maybe checking for existing accounts and pubkeys in whitelist (as it is done already elswhere) could be a nice improvements towards more safety.
Is it possible to implement?

EDIT: Here is NXT-APNQ-LRZS-6JJK-2B85Q locked out becuse of empty whitelist. Is it possible to remove AC in this case?
Empty whitelist means any account can approve the transaction. While not very useful, this is allowed. You should be able to create an account control transaction removing the control, and then approve it using either this, or any other account.
Phasing using by-account with empty whitelist however is executed at finish height only, early release of such transactions is not supported. Meaning you will have to wait until finish height for the change to take effect, after the approval.

Thanks for clarification!
Didn't know it is possible to approve empty whitelisted AC. However there is no GUI support for this right?
I think because it is so easy for new user to get into trouble, there should be an easy way to fix it.
I'd like to propose this. What if such empty white list Approval Requests appeared in the GUI but only for the creator account.
It couldn't harm and the user would be able to fix his broken AC easy-peasy with one click.
Title: Re: NRS v1.7.2e
Post by: abctc on December 08, 2015, 07:13:25 pm
Perhaps you were running on a Linux VPS without specifying the nohup command ?
This would (under certain conditions) trigger the Java shutdown hook whenever you logout or when your terminal session times out.
- yes, probably it is the cause. Thank you.
Title: Re: NRS v1.7.2e
Post by: petko on December 08, 2015, 09:55:10 pm

Thanks for clarification!
Didn't know it is possible to approve empty whitelisted AC. However there is no GUI support for this right?
I think because it is so easy for new user to get into trouble, there should be an easy way to fix it.
I'd like to propose this. What if such empty white list Approval Requests appeared in the GUI but only for the creator account.
It couldn't harm and the user would be able to fix his broken AC easy-peasy with one click.

There is UI support, there isn't a notification in Dashboard. You can approve the transaction from the transaction info dialog, Actions tab:

(http://i68.tinypic.com/2d9r6uo.png)

Title: Re: NRS v1.7.2e
Post by: petko on December 08, 2015, 09:59:51 pm
GUI refresh issue:

after approving still showing "Dashboard/Approval Requests (1)".

I think it's on purpose. The approval request will disappear after the finish height (if not, that's a bug).
Title: Re: NRS v1.7.2e
Post by: phideas on December 08, 2015, 10:50:31 pm

Thanks for clarification!
Didn't know it is possible to approve empty whitelisted AC. However there is no GUI support for this right?
I think because it is so easy for new user to get into trouble, there should be an easy way to fix it.
I'd like to propose this. What if such empty white list Approval Requests appeared in the GUI but only for the creator account.
It couldn't harm and the user would be able to fix his broken AC easy-peasy with one click.

There is UI support, there isn't a notification in Dashboard. You can approve the transaction from the transaction info dialog, Actions tab:

(http://i68.tinypic.com/2d9r6uo.png)

Just wow and thanks! Didn't know about that option so I did a curl API request instead ;D
Oh boy NXT is so ...complex.
Title: Re: NRS v1.7.2e
Post by: phideas on December 08, 2015, 10:54:41 pm
Small UI quirk: Error message in shuffling is in NQT instead of NXT
"Incorrect amount. value 500000000 not in range [700000000-9223372036854775807]"
Title: Re: NRS v1.7.2e
Post by: qq2536007339 on December 09, 2015, 06:24:00 am
Should the receiver of properties have a change to refuse a setter? In case a setter set a aggressive properties name or value? The receiver have to pay 1 NXT to delete? Seems not fair.
Title: Re: NRS v1.7.2e
Post by: petko on December 09, 2015, 09:38:34 am
Just wow and thanks! Didn't know about that option so I did a curl API request instead ;D
Oh boy NXT is so ...complex.

There is simpler way than curl - open http://localhost:6876/test in browser

The complex UI is a problem. I myself found this button by searching the code! There is nothing guiding the user that they can approve from the transaction actions. (It seems intuitive once you know it, but apparently not enough. That's why users are better in UX than developers).

On top of that, there is Approval Requests in Dashboard which only shows transactions that have your account as whitelisted (it cannot be otherwise, else this list will be full of spam). But this is not clearly explained, so the user thinks this is the only place to approve transaction.

I can add some info text in Approval Requests explaining what this list contains and where to find the "general" button for transaction approval. This is what comes to my mind as a solution, but I'm not UX designer and will accept other suggestions.

I don't like your initial suggestion to add to Dashboard/Approval Requests the outgoing transactions that can be approved by the sender. Because this is not solving the general problem with the visibility of Transaction Info/Actions (and there are many other cases when the user will want to approve a transaction without whitelisted accounts, which is not issued by himself).
Title: Re: NRS v1.7.2e
Post by: Klokan on December 09, 2015, 11:57:54 am
Short question about NRS nodes and hallmark, not related just to 1.7.2e, but to all versions : If I have a node with a direct real/public IP/iface on it, everything works well. But if I'd like to run hallmarked node behind a firewall ... if I set up nxt.peerServerHost and nxt.apiServerHost to internal IP (or 0.0.0.0.0), node is running. But then, if I create hallmark due to public DNS name or public/real IP of that node, and I start it again, all other nodes start to cry "Invalid announced address" and my node is running, but not connect to any other nodes. If I disable nxt.MyAddress item, node is running well then, and it is connected, but at the same time it is not visible on peerexplorer.com, so in that case is my node probably not fully hallmarked & serve to whole NXT network properly.
So, what's the solution? Create hallmark according to internal IP of that machine? Or ... ? Thanks!
Title: Re: NRS v1.7.2e
Post by: abctc on December 09, 2015, 12:45:14 pm
.. if I create hallmark due to public DNS name or public/real IP of that node, and I start it again, all other nodes start to cry ...
- maybe this will help:
Added generate hallmark dialog to facilitate hallmarking your node. The host
field is pre-populated with the external node address as detected by UPnP.
Note that when using dynamic IP address you should set up and use a dynamic
DNS hostname
instead of the numeric IP for the hallmark. And when using a
non-default port, the host field should be filled as host:port.
Title: Re: NRS v1.7.2e
Post by: Klokan on December 09, 2015, 02:26:40 pm
.. if I create hallmark due to public DNS name or public/real IP of that node, and I start it again, all other nodes start to cry ...
- maybe this will help:
Added generate hallmark dialog to facilitate hallmarking your node. The host
field is pre-populated with the external node address as detected by UPnP.
Note that when using dynamic IP address you should set up and use a dynamic
DNS hostname
instead of the numeric IP for the hallmark. And when using a
non-default port, the host field should be filled as host:port.

Thanks. But I'm afraid, this is not the case. I haven't dynamic IP, on the main firewall I have still the same, static IP address - I'm doing portforwarding into internal Linux NRS node (with internal IP, e.g. 192.168.2.2), both forwarded ports (7874/tcp, 7876/tcp) are standard and it works well. But doesn't matter, if I create hallmark with that external (static) IP, or with DNS name, that represents this external IP - other nodes start to cry immediately about "Invalid announced address" in both cases...
Title: Re: NRS v1.7.2e
Post by: phideas on December 09, 2015, 05:51:01 pm
Just wow and thanks! Didn't know about that option so I did a curl API request instead ;D
Oh boy NXT is so ...complex.

There is simpler way than curl - open http://localhost:6876/test in browser

The complex UI is a problem. I myself found this button by searching the code! There is nothing guiding the user that they can approve from the transaction actions. (It seems intuitive once you know it, but apparently not enough. That's why users are better in UX than developers).

On top of that, there is Approval Requests in Dashboard which only shows transactions that have your account as whitelisted (it cannot be otherwise, else this list will be full of spam). But this is not clearly explained, so the user thinks this is the only place to approve transaction.

I can add some info text in Approval Requests explaining what this list contains and where to find the "general" button for transaction approval. This is what comes to my mind as a solution, but I'm not UX designer and will accept other suggestions.

I don't like your initial suggestion to add to Dashboard/Approval Requests the outgoing transactions that can be approved by the sender. Because this is not solving the general problem with the visibility of Transaction Info/Actions (and there are many other cases when the user will want to approve a transaction without whitelisted accounts, which is not issued by himself).

Thanks for a detailed answer. I don't think I have any more complaints. The GUI option to recover from this mistake is there.

I think what would be useful for new users is simple guidelines (tutorials) for most common usecases.
E.g.
- How to create multisig NXT account? Then guiding through AC and showing how to set up optimal values.
- How to issue an Asset
- How to create own currency
- How to use nxtvault
- How to do cold storage for NXT
...
EDIT:
I was playing with idea to create a dedicated website for smth. like this targeting newbies.
But no hurry. I know Tenessee cooking the new web and maybe something similar, don't want to duplicate effort.
Title: Re: NRS v1.7.2e
Post by: qq2536007339 on December 11, 2015, 01:08:48 am
Maybe Shuffling warning message should add something like "Shuffling process will cost 12NXT,make sure you keep enough balance during the time".
Title: Re: NRS v1.7.2e
Post by: Klokan on December 11, 2015, 11:42:20 am
.. if I create hallmark due to public DNS name or public/real IP of that node, and I start it again, all other nodes start to cry ...
- maybe this will help:
Added generate hallmark dialog to facilitate hallmarking your node. The host
field is pre-populated with the external node address as detected by UPnP.
Note that when using dynamic IP address you should set up and use a dynamic
DNS hostname
instead of the numeric IP for the hallmark. And when using a
non-default port, the host field should be filled as host:port.

Thanks. But I'm afraid, this is not the case. I haven't dynamic IP, on the main firewall I have still the same, static IP address - I'm doing portforwarding into internal Linux NRS node (with internal IP, e.g. 192.168.2.2), both forwarded ports (7874/tcp, 7876/tcp) are standard and it works well. But doesn't matter, if I create hallmark with that external (static) IP, or with DNS name, that represents this external IP - other nodes start to cry immediately about "Invalid announced address" in both cases...

Any idea ? Thanks...
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 11, 2015, 12:13:53 pm
Do you have nxt.myAddress set? It should match the hallmark, and for a static IP both can use the just the IP.
Title: Re: NRS v1.7.2e
Post by: Klokan on December 11, 2015, 01:12:55 pm
Do you have nxt.myAddress set? It should match the hallmark, and for a static IP both can use the just the IP.

Of course. I checked it with : hallmark due to (public) IP address and nxt.myAddress with that IP address (with and without 7874 port), hallmark due to DNS name (according to that public IP), with nxt.MyAdress= that DNS name (also with and without 7874 port). In every cases other nodes said "Invalid announced address...". If I disabled nxt.MyAddress, that node works and it was connected to other nodes, but it wasn't visible on peerexplorer.com, so it wasn't correctly hallmarked in that case, probably...
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 11, 2015, 03:24:19 pm
Not sure what could be wrong really. You can compare with my setup, I have a hallmarked node running behind VPN so external IP 178.162.198.109 is very different from internal (10.0....), yet peer explorer finds it:

http://www.peerexplorer.com/info?node=178.162.198.109

Relevant properties I have set:

Code: [Select]
nxt.peerServerHost=10.x.x.x
nxt.myAddress=bug.airdns.org
nxt.myHallmark=7be10dbe33c9be7fcf73f9d64a384f2208d71681ec655f8e786933942f9762470e006275672e616972646e732e6f726701000000547b3301d654b626acaee8e920ff3625ce9099b96b655623e2e1bc28fa9af39c402eac05045e00e3cd6ec710e513a86009d435193bbf2e5b9b0ddc208cc3e418025a8efcce
Title: Re: NRS v1.7.2e
Post by: Klokan on December 11, 2015, 04:36:35 pm
Not sure what could be wrong really. You can compare with my setup, I have a hallmarked node running behind VPN so external IP 178.162.198.109 is very different from internal (10.0....), yet peer explorer finds it:

http://www.peerexplorer.com/info?node=178.162.198.109

Relevant properties I have set:

Code: [Select]
nxt.peerServerHost=10.x.x.x
nxt.myAddress=bug.airdns.org
nxt.myHallmark=7be10dbe33c9be7fcf73f9d64a384f2208d71681ec655f8e786933942f9762470e006275672e616972646e732e6f726701000000547b3301d654b626acaee8e920ff3625ce9099b96b655623e2e1bc28fa9af39c402eac05045e00e3cd6ec710e513a86009d435193bbf2e5b9b0ddc208cc3e418025a8efcce

My config looks really very similar :

Code: [Select]
nxt.shareMyAddress=true
nxt.peerServerPort=7874
nxt.peerServerHost=192.168.2.2
nxt.myAddress=nxt6.y.cz
nxt.myPlatform=LinuxCZ
nxt.myHallmark=6c00bc391d90b8a64155c773e13c6cbe5b6b7bb98ea9cbd4390849ea07eeb80a09006e7874362e792e637a64000000a77b3301e3f3da0ffdf8cc4127a7d5a1f5388d54df62ea1a1d2657e145fe3d181e8e303c0c8757465d84f91422115cb5432d6723a1293afdd1dded15d3d1c93da548f78877

Here is output from "hallmark decryption" in NRS admin menu :

Code: [Select]
{ "date": "2015-12-07", "valid": true, "port": 7874, "accountRS": "NXT-8CBP-XQAH-J47K-GNQPB", "host": "nxt6.y.cz", "weight": 100, "requestProcessingTime": 1, "account": "16489601202467842357" }

But all the nodes start to cry immediately after start of my node :

Code: [Select]
2015-12-11 17:33:24 FINE: Peer 23.239.27.64 version null returned error: {"error":"Invalid announced address"}, request was: {"hallmark":"6c00bc391d90b8a64155c773e13c6cbe5b6b7bb98ea9cbd4390849ea07eeb80a09006e7874362e792e637a64000000a77b3301e3f3da0ffdf8cc4127a7d5a1f5388d54df62ea1a1d2657e145fe3d181e8e303c0c8757465d84f91422115cb5432d6723a1293afdd1dded15d3d1c93da548f78877","protocol":1,"announcedAddress":"nxt6.y.cz","application":"NRS","requestType":"getInfo","services":"1","version":"1.6.2","platform":"LinuxCZ","shareAddress":true}, disconnecting


So, what's wrong ? Portforwarding/NAT is working well, you can reach nxt6.y.cz node on both 7874 & 7876/tcp ports without any troubles...
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 11, 2015, 05:08:54 pm
I found this in my log:

2015-12-11 16:49:40 FINE: Hallmark host nxt6.y.cz doesn't match 31.30.6.130
2015-12-11 16:49:40 FINE: Announced address nxt6.y.cz does not resolve to 31.30.6.130
2015-12-11 16:49:40 FINE: GetInfo: ignoring invalid announced address for 31.30.6.130

Where is the 31.30.6.130 coming from? The address nxt6.y.cz resolves to 31.30.6.134, and this is the same as in your hallmark. Could it be that your http requests are being sent out from a different IP? The address GetInfo sees as peer address is coming from ServletRequest.getRemoteAddr().
Title: Re: NRS v1.7.2e
Post by: Klokan on December 11, 2015, 05:24:51 pm
I found this in my log:

2015-12-11 16:49:40 FINE: Hallmark host nxt6.y.cz doesn't match 31.30.6.130
2015-12-11 16:49:40 FINE: Announced address nxt6.y.cz does not resolve to 31.30.6.130
2015-12-11 16:49:40 FINE: GetInfo: ignoring invalid announced address for 31.30.6.130

Where is the 31.30.6.130 coming from? The address nxt6.y.cz resolves to 31.30.6.134, and this is the same as in your hallmark. Could it be that your http requests are being sent out from a different IP? The address GetInfo sees as peer address is coming from ServletRequest.getRemoteAddr().

Ha, this is probably the point! Another real IP (31.30.6.130) is main IP of firewall, but I suppose that portforwarding (and "SNATting / masquerading" in the opposite track) is enough for 7874 & 7876 ports? So, my question is -- which all ports I'd included to the appropriate firewall rules(ets) ?

Thanks for your help in any case, Jean-Luc...
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 11, 2015, 06:27:49 pm
We have this restriction, that the announced address is considered invalid when it doesn't match the address from which the http request originates. I understand you can have a configuration where you listen on one network interface, and send outgoing requests out of another, but in such case we can't verify that those two addresses really belong to the same node, and allowing it would open the door to possible sybil attacks on the network.
Title: Re: NRS v1.7.2e
Post by: MrCluster87 on December 12, 2015, 10:05:15 am
Hey I got this nxt log:

2015-12-12 10:40:06 FINE: os.arch = amd64
2015-12-12 10:40:06 FINE: sun.arch.data.model = 64
2015-12-12 10:40:06 FINE: os.name = Linux
2015-12-12 10:40:06 FINE: file.encoding = UTF-8
2015-12-12 10:40:06 FINE: nxt.runtime.mode = null
2015-12-12 10:40:06 FINE: availableProcessors = 4
2015-12-12 10:40:06 FINE: maxMemory = 893386752
2015-12-12 10:40:06 FINE: processId = 3024
2015-12-12 10:40:06 INFO: nxt.isTestnet = "false"
2015-12-12 10:40:06 INFO: nxt.isOffline = "false"
2015-12-12 10:40:06 INFO: nxt.maxRollback = "800"
2015-12-12 10:40:06 INFO: nxt.forgingDelay = "20"
2015-12-12 10:40:06 INFO: nxt.forgingSpeedup = "3"
2015-12-12 10:40:06 INFO: nxt.maxPrunableLifetime = "7776000"
2015-12-12 10:40:06 INFO: nxt.includeExpiredPrunable = "true"
2015-12-12 10:40:06 INFO: nxt.correctInvalidFees = "false"
2015-12-12 10:40:06 INFO: nxt.statementLogThreshold = "10000"
2015-12-12 10:40:06 INFO: nxt.transactionLogThreshold = "15000"
2015-12-12 10:40:06 INFO: nxt.transactionLogInterval = "15"
2015-12-12 10:40:06 INFO: nxt.dbCacheKB = "0"
2015-12-12 10:40:06 INFO: nxt.dbUrl not defined
2015-12-12 10:40:06 INFO: nxt.dbType = "h2"
2015-12-12 10:40:06 INFO: nxt.dbDir = "nxt_db/nxt"
2015-12-12 10:40:06 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE"
2015-12-12 10:40:06 INFO: nxt.dbUsername = "sa"
2015-12-12 10:40:06 INFO: nxt.dbPassword = "{not logged}"
2015-12-12 10:40:06 INFO: nxt.maxDbConnections = "30"
2015-12-12 10:40:06 INFO: nxt.dbLoginTimeout = "70"
2015-12-12 10:40:06 INFO: nxt.dbDefaultLockTimeout = "60"
2015-12-12 10:40:06 FINE: Database jdbc url set to jdbc:h2:nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;CACHE_SIZE=262144 username sa
2015-12-12 10:40:06 INFO: nxt.useStrongSecureRandom = "false"
2015-12-12 10:43:58 SEVERE: org.h2.jdbc.JdbcSQLException: General error: "java.lang.ArrayIndexOutOfBoundsException: 54" [50000-176]
java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: General error: "java.lang.ArrayIndexOutOfBoundsException: 54" [50000-176]
   at nxt.db.a.a(Unknown Source)
   at nxt.eb.a(Unknown Source)
   at nxt.fa.<clinit>(Unknown Source)
   at nxt.Nxt.e(Unknown Source)
   at nxt.Nxt.main(Unknown Source)
Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.ArrayIndexOutOfBoundsException: 54" [50000-176]
   at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
   at org.h2.message.DbException.get(DbException.java:167)
   at org.h2.message.DbException.convert(DbException.java:294)
   at org.h2.engine.Database.openDatabase(Database.java:291)
   at org.h2.engine.Database.<init>(Database.java:254)
   at org.h2.engine.Engine.openSession(Engine.java:57)
   at org.h2.engine.Engine.openSession(Engine.java:164)
   at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)
   at org.h2.engine.Engine.createSession(Engine.java:125)
   at org.h2.engine.Engine.createSession(Engine.java:27)
   at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:331)
   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:74)
   at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:191)
   at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:354)
   at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:386)
   at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:228)
   at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:200)
   ... 5 more
Caused by: java.lang.ArrayIndexOutOfBoundsException: 54
   at org.h2.index.PageDataLeaf.getRowAt(PageDataLeaf.java:333)
   at org.h2.index.PageDataLeaf.getRowWithKey(PageDataLeaf.java:456)
   at org.h2.index.PageDataNode.getRowWithKey(PageDataNode.java:281)
   at org.h2.index.PageDataIndex.getRowWithKey(PageDataIndex.java:427)
   at org.h2.store.PageStore.redoDelete(PageStore.java:1549)
   at org.h2.store.PageLog.recover(PageLog.java:347)
   at org.h2.store.PageStore.recover(PageStore.java:1407)
   at org.h2.store.PageStore.openExisting(PageStore.java:368)
   at org.h2.store.PageStore.open(PageStore.java:289)
   at org.h2.engine.Database.getPageStore(Database.java:2366)
   at org.h2.engine.Database.open(Database.java:657)
   at org.h2.engine.Database.openDatabase(Database.java:260)
   ... 20 more
2015-12-12 10:43:58 INFO: Shutting down...
2015-12-12 10:43:58 INFO: nxt.adminPassword not defined
2015-12-12 10:43:58 INFO: nxt.maxAPIRecords = "100"
2015-12-12 10:43:58 INFO: nxt.enableAPIUPnP = "false"
2015-12-12 10:43:58 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2015-12-12 10:43:58 INFO: nxt.enableAPIServer = "true"
2015-12-12 10:43:58 INFO: nxt.apiServerPort = "7876"
2015-12-12 10:43:58 INFO: nxt.apiServerSSLPort = "7876"
2015-12-12 10:43:58 INFO: nxt.apiServerHost = "127.0.0.1"
2015-12-12 10:43:58 INFO: nxt.disableAdminPassword = "false"
2015-12-12 10:43:58 INFO: nxt.apiSSL = "false"
2015-12-12 10:43:58 INFO: nxt.apiServerIdleTimeout = "30000"
2015-12-12 10:43:58 INFO: API server using HTTP port 7876
2015-12-12 10:43:58 INFO: nxt.apiResourceBase = "html/ui"
2015-12-12 10:43:58 INFO: nxt.apiWelcomeFile = "index.html"
2015-12-12 10:43:58 INFO: nxt.javadocResourceBase = "html/doc"
2015-12-12 10:43:58 INFO: nxt.maxUploadFileSize not defined or not numeric, using default value 0
2015-12-12 10:43:58 INFO: nxt.enableAPIServerGZIPFilter = "false"
2015-12-12 10:43:58 INFO: nxt.apiServerCORS = "false"
2015-12-12 10:43:58 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2015-12-12 10:43:58 INFO: nxt.enableUIServer = "false"
2015-12-12 10:43:58 INFO: User interface server not enabled
2015-12-12 10:43:58 INFO: nxt.hideErrorDetails = "false"
2015-12-12 10:43:58 INFO: nxt.myPlatform = "PC"
2015-12-12 10:43:58 INFO: nxt.myAddress not defined
2015-12-12 10:43:58 INFO: nxt.peerServerPort = "7874"
2015-12-12 10:43:58 INFO: nxt.shareMyAddress = "true"
2015-12-12 10:43:58 INFO: nxt.enablePeerUPnP = "true"
2015-12-12 10:43:58 INFO: nxt.myHallmark not defined
2015-12-12 10:43:58 FINE: My peer info:
{"application":"NRS","services":"0","version":"1.7.2e","platform":"PC","shareAddress":true}
2015-12-12 10:43:58 INFO: nxt.defaultPeers = "98.207.117.83; 128.199.65.112; 162.243.242.8; 115.28.222.148; 202.96.138.235; 93.75.9.10; 128.8.128.117; nxtjinn.ddns.net; 91.239.69.78; 62.75.145.171; raspi2nxtnode.ddns.net; 176.97.2.141; 78.61.48.176; 158.69.194.254; 142.4.218.174; 78.63.207.76; nxt.miasik.tk; nxt.noip.me; 93.190.139.136; 90.154.170.235; 7876.us; 202.96.138.245; 132.230.76.160; 73.187.84.57; 70.31.212.252; 72.185.23.235; 178.62.185.131; 188.226.135.201; 99.249.104.230; bug.airdns.org; 167.114.113.197; 173.224.126.254; coinserver.ddns.net; 167.114.113.194; 104.193.41.253; 37.139.5.199; 98.219.161.231; 70.106.182.230; 92.11.133.156; 23.239.27.64; nxt.cryonet.de; 85.10.201.15; raspnxt.hopto.org; 158.69.33.172; 78.47.58.62; 188.35.156.10; 73.217.192.86; 144.76.3.50; 192.99.77.148; 107.170.193.198; 81.2.103.237; 78.69.188.169; nxtx.ru; 92.222.65.40; 85.25.198.120; 185.99.132.54; 89.212.19.49; nxt01.now.im; nrs.scripterron.org; 192.241.196.179; 46.28.206.40; 167.114.113.250; 217.23.6.2; 71.8.87.15; 84.242.91.139; node-001.hohertz.com; 75.177.109.103; 69.163.40.132; 178.63.60.131; beor.homeip.net; 94.227.33.223; 173.73.166.80; 167.114.113.249; 71.174.53.51; 109.87.255.75; 167.114.113.246; 75.137.188.158; 80.153.101.190; 68.61.91.124; 95.215.47.221; 78.47.115.250; 73.40.226.143; nxt.servebeer.com:18911; 159.203.101.247; nxt.sx; nxt.cybermailing.com; 176.183.209.73; 91.202.253.240; 192.3.158.120; 46.28.111.249; 80.150.243.95; 80.150.243.96; 80.150.243.97; 80.150.243.98; pakisnxt.no-ip.org; 80.150.243.99; 194.135.85.170; 80.150.243.12; 176.9.138.21; 80.150.243.13; 52.28.97.208; 114.144.20.175; 77.123.252.71; 167.114.96.222; 167.114.96.223; 103.22.181.235; 85.10.196.54; 73.50.115.206; 46.108.156.144; 46.236.161.66; 24.165.52.89; 71.170.34.26; nxt1.testdruif.be; bitcoinnode.ddns.net; silvanoip.dhcp.biz; 27.121.134.84; 162.243.122.251; 192.99.151.160; strat2.hd.free.fr; 62.194.6.113; node-dua.miasik.tk; 160.97.62.237; 220.215.167.4; 198.199.95.15; 31.187.71.186; 82.154.10.253; 178.63.60.81; 87.139.122.48; 91.44.217.37; nxt1.y.cz; 82.244.150.47; 191.238.101.73; 50.157.173.168; 52.24.76.122; 87.139.122.157; brangdon.duckdns.org; 94.102.50.75; ct.flipflop.mooo.com; 24.214.96.98; 77.58.253.73; 83.35.239.24; blackdog1.no-ip.biz; 212.232.49.28; 95.85.31.45; 176.94.115.161; 167.114.113.25; 82.150.180.133; 167.114.113.27; nxtcoin.no-ip.org; 82.247.98.128; 46.4.74.71; 162.243.145.83; nxt2.testdruif.be; 178.24.154.11; 167.114.113.201; 96.41.28.161; 24.23.120.252; 77.88.208.12; 103.250.80.247; 192.241.239.118; 210.6.41.187; 189.183.11.32; 96.236.141.73; 72.182.27.227; 178.33.203.157; 176.31.167.127; sluni.szn.dk; 216.119.150.238; 190.10.9.166; megaman.thican.net; 74.15.230.40; 88.163.78.131; 185.53.170.40; 54.213.222.141; 217.217.182.65; humanoide.thican.net; 106.187.102.227; 52.0.72.67; 37.59.14.7; 62.85.20.37; 91.158.16.70; 192.99.68.108;"
2015-12-12 10:43:58 INFO: nxt.wellKnownPeers not defined
2015-12-12 10:43:58 INFO: nxt.knownBlacklistedPeers not defined
2015-12-12 10:43:58 INFO: nxt.maxNumberOfInboundConnections = "250"
2015-12-12 10:43:58 INFO: nxt.maxNumberOfOutboundConnections = "50"
2015-12-12 10:43:58 INFO: nxt.maxNumberOfConnectedPublicPeers = "20"
2015-12-12 10:43:58 INFO: nxt.maxNumberOfKnownPeers = "2000"
2015-12-12 10:43:58 INFO: nxt.minNumberOfKnownPeers = "1000"
2015-12-12 10:43:58 INFO: nxt.connectTimeout = "10000"
2015-12-12 10:43:58 INFO: nxt.readTimeout = "20000"
2015-12-12 10:43:58 INFO: nxt.enableHallmarkProtection = "true"
2015-12-12 10:43:58 INFO: nxt.pushThreshold = "0"
2015-12-12 10:43:58 INFO: nxt.pullThreshold = "0"
2015-12-12 10:43:58 INFO: nxt.useWebSockets = "true"
2015-12-12 10:43:58 INFO: nxt.webSocketIdleTimeout = "900000"
2015-12-12 10:43:58 INFO: nxt.enablePeerServerGZIPFilter = "true"
2015-12-12 10:43:58 INFO: nxt.blacklistingPeriod = "600000"
2015-12-12 10:43:58 INFO: nxt.communicationLoggingMask = "0"
2015-12-12 10:43:58 INFO: nxt.sendToPeersLimit = "10"
2015-12-12 10:43:58 INFO: nxt.usePeersDb = "true"
2015-12-12 10:43:58 INFO: nxt.savePeers = "true"
2015-12-12 10:43:58 INFO: nxt.getMorePeers = "true"
2015-12-12 10:43:58 INFO: nxt.cjdnsOnly = "false"
2015-12-12 10:43:58 INFO: nxt.ignorePeerAnnouncedAddress = "false"
2015-12-12 10:43:59 INFO: nxt.trimDerivedTables = "true"
2015-12-12 10:43:59 INFO: nxt.numberOfForkConfirmations = "2"
2015-12-12 10:43:59 INFO: nxt.trimFrequency = "1000"
2015-12-12 10:43:59 INFO: nxt.disableGetMoreBlocksThread not defined, assuming false
2015-12-12 10:43:59 INFO: nxt.disablePeerConnectingThread not defined, assuming false
2015-12-12 10:43:59 INFO: nxt.disablePeerUnBlacklistingThread not defined, assuming false
2015-12-12 10:43:59 INFO: nxt.disableGetMorePeersThread not defined, assuming false
2015-12-12 10:43:59 INFO: nxt.peerServerHost = "0.0.0.0"
2015-12-12 10:43:59 INFO: nxt.peerServerIdleTimeout = "30000"
2015-12-12 10:43:59 INFO: nxt.enablePeerServerDoSFilter = "true"
2015-12-12 10:43:59 INFO: nxt.peerServerDoSFilter.maxRequestsPerSec = "30"
2015-12-12 10:43:59 INFO: nxt.peerServerDoSFilter.delayMs = "1000"
2015-12-12 10:43:59 INFO: nxt.peerServerDoSFilter.maxRequestMs = "300000"
2015-12-12 10:43:59 INFO: shutting down sendingService
2015-12-12 10:43:59 INFO: shutting down peersService
2015-12-12 10:43:59 INFO: Nxt server 1.7.2e stopped.


What should I do?
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 12, 2015, 11:00:56 am
Corrupted database. Could be due to an H2 bug, or killing the process without waiting for clean shutdown, or who knows what else. Delete nxt_db and restore from backup, or download from scratch if you don't have a recent backup.
Title: Re: NRS v1.7.2e
Post by: Brangdon on December 13, 2015, 03:34:25 pm
It looks like all the Wiki links in the Nxt http API pages are broken, because the Wiki has moved from https://wiki.nxtcrypto.org/wiki/The_Nxt_API to http://nxtwiki.org/wiki/Nxt_API. It's broken in LiveNet too. See https://nxtforum.org/general-discussion/%28tnnse%29-nxt-wiki-a-new-start!/.
Title: Re: NRS v1.7.2e
Post by: Riker on December 14, 2015, 07:16:24 am
It looks like all the Wiki links in the Nxt http API pages are broken, because the Wiki has moved from https://wiki.nxtcrypto.org/wiki/The_Nxt_API to http://nxtwiki.org/wiki/Nxt_API. It's broken in LiveNet too. See https://nxtforum.org/general-discussion/%28tnnse%29-nxt-wiki-a-new-start!/.

We already fixed this for 1.7.3
Title: Re: NRS v1.7.2e
Post by: starik69 on December 14, 2015, 08:33:18 pm
Can not download testnet blockchain  :'(
Tryed several times from scratch always stuck at this messages in logs:
Code: [Select]
2015-12-14 21:23:57 FINE: Blacklisting 178.162.198.109 because of: nxt.de: Transaction should not have recipient when setting account's own property, recipient is: 16703651475152238025, transaction 11319168567596147115 {"senderPublicKey":"7c5243c756047b755f14909756064da66263fd3a25741ac471bc7669c3443b0a","signature":"29c768064c021951e8dd4ba225f73662d13acce5cf65096a1eb87e771e2b6d088f684d552537f56c37feab0ced1f61594c55dd0ceba52513acff9dd9f142e875","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"6967523821133338355","attachment":{"property":"test Property","value":"2","version.AccountProperty":1},"subtype":10,"amountNQT":0,"recipient":"16703651475152238025","ecBlockHeight":484815,"deadline":1440,"timestamp":64251004}
nxt.de: Transaction should not have recipient when setting account's own property, recipient is: 16703651475152238025, transaction 11319168567596147115 {"senderPublicKey":"7c5243c756047b755f14909756064da66263fd3a25741ac471bc7669c3443b0a","signature":"29c768064c021951e8dd4ba225f73662d13acce5cf65096a1eb87e771e2b6d088f684d552537f56c37feab0ced1f61594c55dd0ceba52513acff9dd9f142e875","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"6967523821133338355","attachment":{"property":"test Property","value":"2","version.AccountProperty":1},"subtype":10,"amountNQT":0,"recipient":"16703651475152238025","ecBlockHeight":484815,"deadline":1440,"timestamp":64251004}
at nxt.df.a(Unknown Source)
at nxt.df.b(Unknown Source)
at nxt.df.a(Unknown Source)
at nxt.df$1.a(Unknown Source)
at nxt.df$1.a(Unknown Source)
at nxt.df$1.run(Unknown Source)
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)
2015-12-14 21:23:57 FINE: Will process a fork of 718 blocks
2015-12-14 21:23:57 FINE: Rollback from block 6038453976342745305 at height 484824 to 6038453976342745305 at 484824
2015-12-14 21:23:57 FINE: Didn't accept any blocks, pushing back my previous blocks
2015-12-14 21:24:00 FINE: Blacklisting 174.140.168.136 because of: nxt.de: Transaction should not have recipient when setting account's own property, recipient is: 16703651475152238025, transaction 11319168567596147115 {"senderPublicKey":"7c5243c756047b755f14909756064da66263fd3a25741ac471bc7669c3443b0a","signature":"29c768064c021951e8dd4ba225f73662d13acce5cf65096a1eb87e771e2b6d088f684d552537f56c37feab0ced1f61594c55dd0ceba52513acff9dd9f142e875","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"6967523821133338355","attachment":{"property":"test Property","value":"2","version.AccountProperty":1},"subtype":10,"amountNQT":0,"recipient":"16703651475152238025","ecBlockHeight":484815,"deadline":1440,"timestamp":64251004}
nxt.de: Transaction should not have recipient when setting account's own property, recipient is: 16703651475152238025, transaction 11319168567596147115 {"senderPublicKey":"7c5243c756047b755f14909756064da66263fd3a25741ac471bc7669c3443b0a","signature":"29c768064c021951e8dd4ba225f73662d13acce5cf65096a1eb87e771e2b6d088f684d552537f56c37feab0ced1f61594c55dd0ceba52513acff9dd9f142e875","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"6967523821133338355","attachment":{"property":"test Property","value":"2","version.AccountProperty":1},"subtype":10,"amountNQT":0,"recipient":"16703651475152238025","ecBlockHeight":484815,"deadline":1440,"timestamp":64251004}
at nxt.df.a(Unknown Source)
at nxt.df.b(Unknown Source)
at nxt.df.a(Unknown Source)
at nxt.df$1.a(Unknown Source)
at nxt.df$1.a(Unknown Source)
at nxt.df$1.run(Unknown Source)
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)
2015-12-14 21:24:00 FINE: Will process a fork of 718 blocks
2015-12-14 21:24:00 FINE: Rollback from block 6038453976342745305 at height 484824 to 6038453976342745305 at 484824
2015-12-14 21:24:00 FINE: Didn't accept any blocks, pushing back my previous blocks
2015-12-14 21:24:02 FINE: Blacklisting 178.150.207.53 because of: nxt.de: Transaction should not have recipient when setting account's own property, recipient is: 16703651475152238025, transaction 11319168567596147115 {"senderPublicKey":"7c5243c756047b755f14909756064da66263fd3a25741ac471bc7669c3443b0a","signature":"29c768064c021951e8dd4ba225f73662d13acce5cf65096a1eb87e771e2b6d088f684d552537f56c37feab0ced1f61594c55dd0ceba52513acff9dd9f142e875","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"6967523821133338355","attachment":{"property":"test Property","value":"2","version.AccountProperty":1},"subtype":10,"amountNQT":0,"recipient":"16703651475152238025","ecBlockHeight":484815,"deadline":1440,"timestamp":64251004}
nxt.de: Transaction should not have recipient when setting account's own property, recipient is: 16703651475152238025, transaction 11319168567596147115 {"senderPublicKey":"7c5243c756047b755f14909756064da66263fd3a25741ac471bc7669c3443b0a","signature":"29c768064c021951e8dd4ba225f73662d13acce5cf65096a1eb87e771e2b6d088f684d552537f56c37feab0ced1f61594c55dd0ceba52513acff9dd9f142e875","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"6967523821133338355","attachment":{"property":"test Property","value":"2","version.AccountProperty":1},"subtype":10,"amountNQT":0,"recipient":"16703651475152238025","ecBlockHeight":484815,"deadline":1440,"timestamp":64251004}
at nxt.df.a(Unknown Source)
at nxt.df.b(Unknown Source)
at nxt.df.a(Unknown Source)
at nxt.df$1.a(Unknown Source)
at nxt.df$1.a(Unknown Source)
at nxt.df$1.run(Unknown Source)
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)
2015-12-14 21:24:02 FINE: Will process a fork of 718 blocks
2015-12-14 21:24:02 FINE: Rollback from block 6038453976342745305 at height 484824 to 6038453976342745305 at 484824
2015-12-14 21:24:02 FINE: Didn't accept any blocks, pushing back my previous blocks
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 14, 2015, 08:40:15 pm
If you are getting this error, you are running 1.7.1e.
Title: Re: NRS v1.7.2e
Post by: starik69 on December 14, 2015, 10:53:50 pm
If you are getting this error, you are running 1.7.1e.
Oh, yes, somehow i updated 1.7.1e to 1.7.2e but it is still 1.7.1e  :-[
Title: Re: NRS v1.7.2e
Post by: allwelder on December 15, 2015, 01:11:48 pm
Who is responsible for the Multilanguage UI?
There are many words added with 1.7x,but no task assigned on crowding (https://crowdin.com/project/nxt-ui-translation). :)
Title: Re: NRS v1.7.2e
Post by: allwelder on December 15, 2015, 01:13:47 pm
Another,How to use this account property feature?
Assign a value,but did not know what's the use case.
Title: Re: NRS v1.7.2e
Post by: Jean-Luc on December 15, 2015, 01:43:38 pm
Setting properties of ones own account can be used as a better account info, to store not just name and description but arbitrary custom fields, e.g. email, gpg fingerprint, btc address, bitmessage address, etc.

Such properties can be used instead of aliases, without having to worry whether a global alias of the same name is already reserved. Or treat them as namespaced aliases, like subdomains, if an account already owns a global alias "abc", and sets a property "xyz", the value of this property can be treated as xyz.abc alias.

Setting properties to another account can be used by services to assign metadata to user accounts, or authorization credentials, e.g. an exchange can set a "verificationLevel = 3". The recipient of a property could delete it, but cannot modify or transfer it, and the setter can always delete or update it in the future. Or a third party verification service could be responsible for processing and approving user accounts, and others can just check if an account has the required property set by this provider, and treat it as having been verified at the appropriate level.
Title: Re: NRS v1.7.2e
Post by: allwelder on December 15, 2015, 01:52:38 pm
Understanding,thanks. :)
Title: Re: NRS v1.7.2e
Post by: Coral91 on December 17, 2015, 10:17:03 am
Looks promising, downloading now and starting to stake tonight, i`m eager to test it out.
Title: Re: NRS v1.7.2e
Post by: Coral91 on December 18, 2015, 10:41:32 am
Just started staking, works like a charm, just wanted to let yall know.
Title: Re: NRS v1.7.2e
Post by: ProTrader72 on December 18, 2015, 02:45:02 pm
Just started staking, works like a charm, just wanted to let yall know.

Indeed it works like "CHARM",  but joke aside, I`ve also downloaded the new client with blockchain and it works very well. I hope the supernet gets updated to these features too.
Title: Re: NRS v1.7.2e
Post by: Coral91 on December 18, 2015, 02:56:55 pm
Just started staking, works like a charm, just wanted to let yall know.

Indeed it works like "CHARM",  but joke aside, I`ve also downloaded the new client with blockchain and it works very well. I hope the supernet gets updated to these features too.

Lol, ok.
elective-stereophonic
elective-stereophonic
assembly
assembly