Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on July 02, 2016, 09:11:06 am

Title: NRS v1.9.2
Post by: Jean-Luc on July 02, 2016, 09:11:06 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.9.2

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

sha256:

4fe0520e5b4d0fe244dc9d8ab7943c1a107a7e4227ce4ae9f3236ae1dcc1a8ab  nxt-client-1.9.2.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.9.2.sh

sha256:

bf135f9d7280860b59fb69d4753e436ed23ebbcf95e1e4112cb707c7a64a20b4  nxt-client-1.9.2.sh

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

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

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


Change log:

This is the first stable release in the 1.9 series. Update to this release on
mainnet is optional up until block 1000000 (Oct 12), however users are advised
to do it earlier, as after July 14th updating will trigger a blockchain rescan.

The main new feature in 1.9 is the distribution of ARDR assets. See the 1.9.0e
changelog for details.

Performance optimizations for blockchain rescans and for snapshot balance
calculations. Added nxt.dbMaxMemoryRows property to allow setting the H2
MAX_MEMORY_ROWS parameter.

Updated Jetty to version 9.3.10, delete the old lib folder before unpacking on
top.


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

iQIcBAEBCgAGBQJXd3ZbAAoJENqvaxkWiP4Zp/0QANrLL2btWeenChio8CH4AqGu
hXR7uXNyA9skL9R3ji7GqrcF2yuFwgUSOOiu9+P2sZQ2vLvMQkL+hNHv58ivw/1h
OfuDGSKMEJvKCNxX2nWuub6BIciXdbbfijpnJv6MPLc5mMmW+ooKcoaX0dZu1FnK
vWC0UNrHDWjQw0gtu2xh8yWr3/ySgX2v9dfhw88rZJ+nqRUpR+WYyaKJjW+Ihxos
lZrt8T01HuUHPlP2wxOSAzw9zMk79fLJJXwN6VrMbOS9zQ9maKzhwaRAzv9yia5/
BeyH+C7fCCQcLYKPboENZJckr/PWGpl1FftBAB6DaRVrW0qtNYUShouz6XHARnu6
12xhsaY9PWvUgpR+FpnJJxKnLk8CiUepfvlJhIMQ3OTEQtWEac+FMpFMpPbuDUqM
WawwONOId6iE1R9Sa/nIPvErBBMFSP/asyStu5+71+QJhj0Ey5Yk9rvqV5hzisb+
iOKU4DtVatCvb89aIdTh3EBZtKiPDU3M9ftddu2riNtXMSddlLGLq3kEVp5/tP29
JPUHoBq6HYiniLLwR5UbGbIBKy9maGoCzjHJMyVC8hLzKV427jZ+Ac+Qwo+7D+Gj
a9Z347s/5oAwI2obWzXm0BonW5f158ufP9zZGjj2NeyxyVvKFYlCo482uTYjWvGz
gPh4V23KxxU2Xw7kZ3H3
=lOJA
-----END PGP SIGNATURE-----
Title: Re: NRS v1.9.2
Post by: qq2536007339 on July 02, 2016, 09:21:07 am
Thank you,JL,can't wait to try!
Title: Re: NRS v1.9.2
Post by: Nextshares on July 02, 2016, 10:30:01 am
Looks everything works perfectly in my side, thanks core dev team hard work ;)
Title: Re: NRS v1.9.2
Post by: yassin54 on July 02, 2016, 12:22:41 pm
Thanks :)
Tweeted!! https://twitter.com/NxtCommunity/status/749216358211031040  8)
Title: Re: NRS v1.9.2
Post by: rubenbc on July 02, 2016, 12:54:39 pm
Thanks @coreteam!

Enviado desde mi Redmi Note 3 mediante Tapatalk

Title: Re: NRS v1.9.2
Post by: box1413 on July 02, 2016, 01:38:10 pm
on the same boat as you. any way to lower memory requirements to 512? I have a few vps with only that much.

It is maybe not obvious for everyone how to upgrade from 1.8.3 without rescan. Here is what I did:

mv nxt nxt_old
unzip nxt-client-1.9.2.zip
cd nxt
cp -r ../nxt_old/nxt_db .
cp ../nxt_old/conf/nxt.properties conf/nxt.properties
cp ../nxt_old/keystore .

Finally: ./run.sh
Keystore is optional if API-SSL is activated.

By the way, what is the Java memory requirements? On a VM with 0,75GB I keep getting Java Out of Memory. With 2GB RAM it works fine, but it would be beneficial to be able to use the cheapest VM on Microsoft Azure which has only 0,75GB.
Title: Re: NRS v1.9.2
Post by: Riker on July 02, 2016, 02:54:19 pm
Please post the nxt.log with the OutOfMemory error. There are several types of OOM messages, not necessarily indicating shortage in heap space.
Title: Re: NRS v1.9.2
Post by: chevdor on July 02, 2016, 03:24:43 pm
on the same boat as you. any way to lower memory requirements to 512? I have a few vps with only that much.

I am using the nxt-docker Docker image (disclaimer: I am the author of the image). Its runs now for months without any single problem.
I update the image for each version and migrate, other than that, it keeps on running smooth.
The image for 1.9.2 will be available soon. You can find the Docker related topics here: https://nxtforum.org/general-discussion/nxt-in-a-docker-container/msg217714/#msg217714
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 02, 2016, 03:36:19 pm
It seems to me that the new version download buttons don't work in the desktop app.
Is that already known?
If this not a bug but a known limitation of the underlying JavaFX system, I want to suggest to hide the whole dialog. I've just had a support request on our helpdesk because of this issue. I assume that every outgoing link wouldn't work then, or is putting the forums announcement link there an option?
Title: Re: NRS v1.9.2
Post by: chevdor on July 02, 2016, 05:54:25 pm
From what I can say, upgrading now does not trigger a full scan on mainnet but it does on testnet.
Title: Re: NRS v1.9.2
Post by: Riker on July 02, 2016, 07:54:45 pm
It seems to me that the new version download buttons don't work in the desktop app.
Is that already known?
If this not a bug but a known limitation of the underlying JavaFX system, I want to suggest to hide the whole dialog. I've just had a support request on our helpdesk because of this issue. I assume that every outgoing link wouldn't work then, or is putting the forums announcement link there an option?

I can probably fix this. Please open a ticket on bitbucket.
Title: Re: NRS v1.9.2
Post by: NXT ENTERPRISE on July 03, 2016, 12:34:56 am
Hi to just have the client run on my laptop is it as simple as copy and paste the database folder over to the update?

Is there an exact file to move or the folder etc?

Title: Re: NRS v1.9.2
Post by: qq2536007339 on July 03, 2016, 03:58:39 am
After update,I get lots "WebSocket session is not open" error,is that normal?

Code: [Select]
2016-07-03 11:44:02 FINE: Error sending request to peer 52.0.72.67: WebSocket session is not open
2016-07-03 11:44:02 FINE: Error sending request to peer 80.150.243.12: WebSocket session is not open
2016-07-03 11:44:02 FINE: Error sending request to peer 198.46.193.111: WebSocket session is not open
2016-07-03 11:44:02 FINE: Error sending request to peer 188.226.174.169: WebSocket session is not open
2016-07-03 11:44:23 FINE: Error sending request to peer 5.9.155.145: WebSocket session is not open
2016-07-03 11:44:23 FINE: Error sending request to peer 136.243.5.70: WebSocket session is not open
2016-07-03 11:44:23 FINE: Error sending request to peer 95.42.223.181: WebSocket session is not open
2016-07-03 11:44:53 FINE: Error sending request to peer 83.243.149.195: WebSocket session is not open
2016-07-03 11:44:53 FINE: Error sending request to peer 128.199.176.34: WebSocket session is not open
2016-07-03 11:44:53 FINE: Error sending request to peer 37.187.96.196: WebSocket session is not open
2016-07-03 11:44:53 FINE: Error sending request to peer 176.58.120.181: WebSocket session is not open
2016-07-03 11:44:53 FINE: Error sending request to peer 163.172.25.123: WebSocket session is not open
2016-07-03 11:45:23 FINE: Error sending request to peer 85.10.201.15: WebSocket session is not open
2016-07-03 11:45:23 FINE: Error sending request to peer 150.140.159.246: WebSocket session is not open
2016-07-03 11:45:23 FINE: Error sending request to peer 178.162.198.109: WebSocket session is not open
2016-07-03 11:45:23 FINE: Error sending request to peer 73.40.166.127: WebSocket session is not open
2016-07-03 11:45:23 FINE: Error sending request to peer 80.150.243.95: WebSocket session is not open
2016-07-03 11:45:53 FINE: Error sending request to peer 185.56.139.251: WebSocket session is not open
2016-07-03 11:45:53 FINE: Error sending request to peer 96.236.143.175: WebSocket session is not open
2016-07-03 11:45:53 FINE: Error sending request to peer 89.250.243.240: WebSocket session is not open
2016-07-03 11:46:23 FINE: Error sending request to peer 83.43.229.95: WebSocket session is not open
2016-07-03 11:46:23 FINE: Error sending request to peer 78.47.58.62: WebSocket session is not open
2016-07-03 11:46:23 FINE: Error sending request to peer 46.101.137.39: WebSocket session is not open
2016-07-03 11:46:23 FINE: Error sending request to peer 81.82.189.178: WebSocket session is not open
2016-07-03 11:46:23 FINE: Error sending request to peer 212.227.135.232: WebSocket session is not open
2016-07-03 11:46:23 FINE: Error sending request to peer 99.249.104.230: WebSocket session is not open
2016-07-03 11:46:24 FINE: Error sending request to peer 69.163.47.173: WebSocket session is not open
2016-07-03 11:46:53 FINE: Error sending request to peer 72.182.27.227: WebSocket session is not open
2016-07-03 11:46:53 FINE: Connect: announced address nxt.cryonet.de now points to 78.51.161.12, replacing peer 78.51.123.132
2016-07-03 11:46:53 FINE: Error sending request to peer 80.150.243.13: WebSocket session is not open
2016-07-03 11:46:53 FINE: Error sending request to peer 148.251.57.155: WebSocket session is not open
2016-07-03 11:46:53 FINE: Error sending request to peer 46.101.112.58: WebSocket session is not open
2016-07-03 11:46:53 FINE: Error sending request to peer 62.75.159.113: WebSocket session is not open
2016-07-03 11:46:53 FINE: Error sending request to peer 91.116.242.163: WebSocket session is not open
2016-07-03 11:46:53 FINE: Error sending request to peer 144.76.94.38: WebSocket session is not open
2016-07-03 11:47:33 FINE: Error sending request to peer 176.128.198.189: WebSocket session is not open
2016-07-03 11:47:33 FINE: Error sending request to peer 162.243.242.8: WebSocket session is not open
2016-07-03 11:47:33 FINE: Error sending request to peer 80.150.243.88: WebSocket session is not open
2016-07-03 11:47:33 FINE: Error sending request to peer 12.133.228.183: WebSocket session is not open
2016-07-03 11:47:46 FINE: Peer 50.81.64.183 version 1.8.3 returned error: {"error":"Blockchain download in progress"}, request was: {"protocol":1,"requestType":"getCumulativeDifficulty"}, disconnecting
2016-07-03 11:48:03 FINE: Error sending request to peer 162.243.145.83: WebSocket session is not open
2016-07-03 11:48:03 FINE: Error sending request to peer 84.80.4.66: WebSocket session is not open
2016-07-03 11:48:03 FINE: Error sending request to peer 91.239.69.78: WebSocket session is not open
2016-07-03 11:48:03 FINE: Error sending request to peer 89.250.240.60: WebSocket session is not open
2016-07-03 11:48:03 FINE: Error sending request to peer 91.121.193.26: WebSocket session is not open
2016-07-03 11:48:33 FINE: Error sending request to peer 85.25.200.125: WebSocket session is not open
2016-07-03 11:48:33 FINE: Error sending request to peer 87.139.122.48: WebSocket session is not open
2016-07-03 11:48:33 FINE: Error sending request to peer 162.210.92.46: WebSocket session is not open
2016-07-03 11:48:33 FINE: Error sending request to peer 23.239.27.64: WebSocket session is not open
2016-07-03 11:48:33 FINE: Error sending request to peer 83.136.86.67: WebSocket session is not open
2016-07-03 11:49:03 FINE: Error sending request to peer 135.23.200.186: WebSocket session is not open
2016-07-03 11:49:03 FINE: Error sending request to peer 78.63.207.76: WebSocket session is not open
2016-07-03 11:49:03 FINE: Error sending request to peer 91.122.131.231: WebSocket session is not open
2016-07-03 11:49:03 FINE: Error sending request to peer 31.30.6.130: WebSocket session is not open
2016-07-03 11:49:04 FINE: Error sending request to peer 146.185.168.142: WebSocket session is not open
2016-07-03 11:49:05 FINE: Peer 176.74.212.129 version null returned error: {"cause":"Old version: 1.5.12","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":7876,"application":"NRS","requestType":"getInfo","services":"6","version":"1.9.2","platform":"Linux arm","shareAddress":true}, disconnecting
2016-07-03 11:49:33 FINE: Error sending request to peer 45.32.12.214: WebSocket session is not open
2016-07-03 11:49:33 FINE: Error sending request to peer 77.225.180.158: WebSocket session is not open
2016-07-03 11:49:33 FINE: Error sending request to peer 192.3.196.10: WebSocket session is not open
2016-07-03 11:49:33 FINE: Error sending request to peer 5.146.64.45: WebSocket session is not open
2016-07-03 11:49:34 FINE: Error sending request to peer 95.252.28.16: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 88.198.15.19: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 87.138.221.20: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 75.110.141.159: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 84.105.2.156: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 85.242.177.64: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 88.0.253.100: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 78.244.125.22: WebSocket session is not open
2016-07-03 11:50:04 FINE: Error sending request to peer 120.25.65.184: WebSocket session is not open
2016-07-03 11:50:05 FINE: Peer 85.214.37.185 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"apiPort":7876,"application":"NRS","requestType":"getInfo","services":"6","version":"1.9.2","platform":"Linux arm","shareAddress":true}, disconnecting
2016-07-03 11:50:34 FINE: Error sending request to peer 85.159.46.2: WebSocket session is not open
2016-07-03 11:50:34 FINE: Error sending request to peer 80.98.81.73: WebSocket session is not open
2016-07-03 11:50:34 FINE: Error sending request to peer 178.33.203.157: WebSocket session is not open
2016-07-03 11:50:34 FINE: Error sending request to peer 142.4.218.174: WebSocket session is not open
2016-07-03 11:50:34 FINE: Error sending request to peer 164.132.96.27: WebSocket session is not open
2016-07-03 11:50:34 FINE: Error sending request to peer 84.106.253.6: WebSocket session is not open
2016-07-03 11:51:04 FINE: Error sending request to peer 80.150.243.98: WebSocket session is not open
2016-07-03 11:51:04 FINE: Error sending request to peer 69.163.40.132: WebSocket session is not open
2016-07-03 11:51:04 FINE: Error sending request to peer 73.158.152.6: WebSocket session is not open
2016-07-03 11:51:04 FINE: Error sending request to peer 24.62.44.165: WebSocket session is not open
2016-07-03 11:51:04 FINE: Error sending request to peer 176.97.2.179: WebSocket session is not open
2016-07-03 11:51:04 FINE: Error sending request to peer 176.94.115.161: WebSocket session is not open
2016-07-03 11:51:34 FINE: Error sending request to peer 76.88.91.67: WebSocket session is not open
2016-07-03 11:51:34 FINE: Error sending request to peer 2.94.255.230: WebSocket session is not open
2016-07-03 11:51:34 FINE: Error sending request to peer 5.147.32.49: WebSocket session is not open
2016-07-03 11:51:34 FINE: Error sending request to peer 81.83.17.240: WebSocket session is not open
2016-07-03 11:51:34 FINE: Error sending request to peer 188.78.24.184: WebSocket session is not open
2016-07-03 11:51:34 FINE: Error sending request to peer 85.159.209.154: WebSocket session is not open
2016-07-03 11:52:04 FINE: Error sending request to peer 54.213.222.141: WebSocket session is not open
2016-07-03 11:52:04 FINE: Error sending request to peer 85.65.145.4: WebSocket session is not open
2016-07-03 11:52:04 FINE: Error sending request to peer 174.140.167.239: WebSocket session is not open
2016-07-03 11:52:04 FINE: Error sending request to peer 83.83.161.46: WebSocket session is not open
2016-07-03 11:52:04 FINE: Error sending request to peer 27.121.134.84: WebSocket session is not open
2016-07-03 11:52:35 FINE: Error sending request to peer 194.135.85.170: WebSocket session is not open
2016-07-03 11:52:35 FINE: Error sending request to peer 162.243.122.251: WebSocket session is not open
2016-07-03 11:52:35 FINE: Error sending request to peer 104.168.174.36: WebSocket session is not open
2016-07-03 11:52:35 FINE: Error sending request to peer 163.172.7.30: WebSocket session is not open
2016-07-03 11:52:35 FINE: Error sending request to peer 188.165.250.19: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 86.32.94.104: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 109.192.12.87: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 87.138.143.21: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 62.138.2.47: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 198.199.95.15: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 5.135.181.38: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 46.108.156.144: WebSocket session is not open
2016-07-03 11:53:05 FINE: Error sending request to peer 80.150.243.99: WebSocket session is not open
2016-07-03 11:53:35 FINE: Error sending request to peer 82.165.145.37: WebSocket session is not open
2016-07-03 11:53:35 FINE: Error sending request to peer 188.226.179.119: WebSocket session is not open
2016-07-03 11:53:35 FINE: Error sending request to peer 23.102.0.45: WebSocket session is not open
2016-07-03 11:53:35 FINE: Error sending request to peer 84.242.91.139: WebSocket session is not open
2016-07-03 11:53:35 FINE: Error sending request to peer 91.7.18.12: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 52.0.72.67: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 31.128.67.247: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 90.196.20.226: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 80.150.243.11: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 176.9.138.21: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 107.181.152.205: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 198.46.193.111: WebSocket session is not open
2016-07-03 11:54:05 FINE: Error sending request to peer 188.226.174.169: WebSocket session is not open
2016-07-03 11:54:25 FINE: Error sending request to peer 211.149.213.86: WebSocket session is not open
2016-07-03 11:54:25 FINE: Error sending request to peer 80.150.243.12: WebSocket session is not open
2016-07-03 11:54:25 FINE: Error sending request to peer 80.150.243.97: WebSocket session is not open
2016-07-03 11:54:25 FINE: Error sending request to peer 67.165.94.162: WebSocket session is not open
2016-07-03 11:54:25 FINE: Error sending request to peer 178.150.207.53: WebSocket session is not open
2016-07-03 11:54:25 FINE: Error sending request to peer 81.82.186.92: WebSocket session is not open
2016-07-03 11:54:55 FINE: Error sending request to peer 128.199.176.34: WebSocket session is not open
2016-07-03 11:54:55 FINE: Error sending request to peer 78.46.233.109: WebSocket session is not open
2016-07-03 11:54:55 FINE: Error sending request to peer 198.211.127.34: WebSocket session is not open
2016-07-03 11:54:55 FINE: Error sending request to peer 176.58.120.181: WebSocket session is not open
2016-07-03 11:54:56 FINE: Error sending request to peer 163.172.25.123: WebSocket session is not open
2016-07-03 11:55:25 FINE: Error sending request to peer 95.42.223.181: WebSocket session is not open
2016-07-03 11:55:25 FINE: Error sending request to peer 128.199.189.226: WebSocket session is not open
2016-07-03 11:55:25 FINE: Error sending request to peer 80.150.243.95: WebSocket session is not open
2016-07-03 11:55:25 FINE: Error sending request to peer 178.162.198.109: WebSocket session is not open
2016-07-03 11:55:25 FINE: Error sending request to peer 150.140.159.246: WebSocket session is not open
2016-07-03 11:55:33 INFO: Shutting down...
2016-07-03 11:55:33 INFO: nxt.maxNumberOfMonitors = "100"
2016-07-03 11:55:33 INFO: Stopping background jobs...
2016-07-03 11:55:33 INFO: shutting down scheduledThreadPool
2016-07-03 11:55:43 INFO: some threads in scheduledThreadPool didn't terminate, forcing shutdown
2016-07-03 11:55:43 INFO: ...Done
2016-07-03 11:55:43 INFO: shutting down sendingService
2016-07-03 11:55:43 INFO: shutting down peersService
2016-07-03 11:55:49 INFO: Database shutdown completed
2016-07-03 11:55:49 INFO: Nxt server 1.9.2 stopped.
Title: Re: NRS v1.9.2
Post by: OutSL on July 04, 2016, 07:28:12 am
Hello World  :D

Thank you for your ardor in the task and your sublime work  :D
the NXT3D node is active and running prefectly under ubuntu 14.04/last java
https://nxt3d.net:7876/index.html

i want just to report 2 minor bugs in the Web UI using firefox browser:
1) when i use this link in firefox:
https://nxt3d.net:7876/index.html?account=NXT-PC8Q-ZW86-7UYK-CC4XJ
happen the following:
https://nxtforum.org/nrs-releases/nrs-v1-8-0e/msg214885/#msg214885

i think something in the account switch button/list produce this problem and block the loading of the left menu

2) In the peers page, when i pass the cursor over the services letters like "AI" or "HK" sometimes the info-bubble do not disapear even if i change the page... for eg; if i switch to the dashboard, the info-bubble stay visible in the UI...

i have some questions about the account snapshots:
what is your estimation of the NXT database size after the snapshots periode ? is the NXT blockchain will be cleansed from the accounts data later or will stay stored in it?

Thank you and good continuation  :D
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 04, 2016, 09:20:08 am
There's a support request from a mac guy:

Quote
Here is the log and i dont think it holds anything usefull :/ I really wonder why i can get to the contents of the folder and start the server directly with the nxt.jar file and access it later on browser.
I need to kill the jar proccess on console to disable it again.
The client itself when i start still pops up the nxt icon and the jar icon and close before it opens.

Here is the nxt.log:
Code: [Select]
<snip>
2016-07-02 16:18:58 FINE: My peer info:
{"application":"NRS","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}
2016-07-02 16:18:58 INFO: nxt.defaultPeers = "104.193.41.253; 23.239.27.64; infame.ddns.net; nxt.cryonet.de; 88.166.170.251; 85.10.201.15; 79.178.75.62; 80.150.243.88; 73.158.152.6; 109.159.113.28; 87.138.221.20; 76.67.136.229; 188.226.179.119; 88.129.180.157; 70.189.253.107; 68.197.13.94; 67.165.94.162; nxt4.y.cz; 89.212.19.49; 122.9.34.152; nxt01.now.im; nrs.scripterron.org; 5.147.32.49; 75.110.141.159; 85.197.29.126; 73.40.166.72; 62.138.2.47; 73.40.166.127; 174.140.167.239; 69.163.40.132; 78.71.123.156; strat.hd.free.fr; 83.243.149.195; 76.88.91.67; nxt3.y.cz; 85.65.145.4; 150.140.159.246; 85.206.100.75; 73.211.90.130; 148.251.57.155; 191.114.224.104; 72.82.151.130; 80.150.243.95; 80.150.243.96; 51.254.99.240; 80.150.243.97; 80.150.243.98; enricoip.no-ip.biz; pakisnxt.no-ip.org; 12.154.107.207; 80.150.243.99; 211.149.213.86; 80.150.243.12; 176.9.138.21; 198.46.193.111; 176.128.198.189; 80.150.243.13; 77.53.127.188; 99.240.108.15; 73.174.145.153; nxt.scryptmh.eu; 24.214.71.4; 167.114.233.141; 46.108.156.144; 90.196.20.226; 103.250.83.112; 173.76.241.120; 86.76.26.250; nxt1.testdruif.be; 104.238.188.179; 62.194.6.113; nxt.arguseyes.net; 84.80.4.66; 103.250.83.127; 106.185.44.110; 73.79.66.116; 87.139.122.48; srvnxt.ddns.net; nxt1.y.cz; 14.202.115.247; 87.139.122.157; 84.105.2.156; petko.ddns.net; 93.211.248.187; 212.232.49.28; nxt3d.net; 70.233.131.247; 24.62.44.165; 192.3.196.10; 80.98.81.73; 96.236.141.73; 142.4.218.174; 72.182.27.227; 178.33.203.157; 108.32.156.188; nxt.noip.me; 12.133.228.183; 136.243.5.70; 109.192.12.87; megaman.thican.net; 54.213.222.141; humanoide.thican.net; 95.183.53.131; zdani.szn.dk; 96.236.143.175; 217.26.24.27; 178.148.72.52; 73.187.9.170; 52.0.72.67; 135.23.200.186; nxt8.y.cz; 82.71.38.134; 71.60.209.122; bug.airdns.org; 78.46.109.176; nxt.notbot.me; nxt1.scriba.io; 85.25.200.125; 37.136.88.175; 92.236.121.198; gunka.szn.dk; sluni.szn.dk; 78.47.115.250; 84.246.228.249; 202.96.138.245; 81.2.103.237; 144.76.94.38; 78.46.233.109; 162.243.194.123; 82.165.145.37; 46.4.74.71; 78.47.58.62; f376.ddns.net; 96.2.22.105; 37.244.157.205; 162.243.242.8; 86.96.21.149; 90.190.175.217; abuminer.ddns.net; www.ardorwallet.com; neawanna.duckdns.org; 91.239.69.78; 62.75.145.171; 50.165.213.42; paynet.org; 162.243.145.83; 136.243.249.132; 83.83.161.46; 153.160.236.19; 78.61.48.176; 23.94.134.161; 85.159.46.2; 78.63.207.76; 90.154.170.235; 86.155.151.106; 73.198.149.219; node.netbash.org; www.funkymonkey.org; 83.82.131.238; 176.97.2.179; 99.249.104.230;"
2016-07-02 16:18:58 INFO: nxt.wellKnownPeers not defined
2016-07-02 16:18:58 INFO: nxt.knownBlacklistedPeers not defined
2016-07-02 16:18:58 INFO: nxt.maxNumberOfInboundConnections = "250"
2016-07-02 16:18:58 INFO: nxt.maxNumberOfOutboundConnections = "50"
2016-07-02 16:18:58 INFO: nxt.maxNumberOfConnectedPublicPeers = "20"
2016-07-02 16:18:58 INFO: nxt.maxNumberOfKnownPeers = "2000"
2016-07-02 16:18:58 INFO: nxt.minNumberOfKnownPeers = "1000"
2016-07-02 16:18:58 INFO: nxt.connectTimeout = "10000"
2016-07-02 16:18:58 INFO: nxt.readTimeout = "20000"
2016-07-02 16:18:58 INFO: nxt.enableHallmarkProtection = "true"
2016-07-02 16:18:58 INFO: nxt.pushThreshold = "0"
2016-07-02 16:18:58 INFO: nxt.pullThreshold = "0"
2016-07-02 16:18:58 INFO: nxt.useWebSockets = "true"
2016-07-02 16:18:58 INFO: nxt.webSocketIdleTimeout = "900000"
2016-07-02 16:18:58 INFO: nxt.enablePeerServerGZIPFilter = "true"
2016-07-02 16:18:58 INFO: nxt.blacklistingPeriod = "600000"
2016-07-02 16:18:58 INFO: nxt.communicationLoggingMask = "0"
2016-07-02 16:18:58 INFO: nxt.sendToPeersLimit = "10"
2016-07-02 16:18:58 INFO: nxt.usePeersDb = "true"
2016-07-02 16:18:58 INFO: nxt.savePeers = "true"
2016-07-02 16:18:58 INFO: nxt.getMorePeers = "true"
2016-07-02 16:18:58 INFO: nxt.cjdnsOnly = "false"
2016-07-02 16:18:58 INFO: nxt.ignorePeerAnnouncedAddress = "false"
2016-07-02 16:18:58 INFO: nxt.disablePeerConnectingThread not defined, assuming false
2016-07-02 16:18:58 INFO: nxt.disablePeerUnBlacklistingThread not defined, assuming false
2016-07-02 16:18:58 INFO: nxt.disableGetMorePeersThread not defined, assuming false
2016-07-02 16:18:58 INFO: nxt.peerServerHost = "0.0.0.0"
2016-07-02 16:18:58 INFO: nxt.peerServerIdleTimeout = "30000"
2016-07-02 16:18:58 INFO: nxt.enablePeerServerDoSFilter = "true"
2016-07-02 16:18:58 INFO: nxt.peerServerDoSFilter.maxRequestsPerSec = "30"
2016-07-02 16:18:58 INFO: nxt.peerServerDoSFilter.delayMs = "1000"
2016-07-02 16:18:58 INFO: nxt.peerServerDoSFilter.maxRequestMs = "300000"
2016-07-02 16:18:58 INFO: nxt.maxNumberOfForgers = "100"
2016-07-02 16:18:58 INFO: nxt.enableFakeForging not defined, assuming false
2016-07-02 16:18:58 INFO: nxt.disableGenerateBlocksThread not defined, assuming false
2016-07-02 16:18:58 INFO: nxt.addOns not defined
2016-07-02 16:18:58 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-07-02 16:18:58 INFO: nxt.enableUIServer = "false"
2016-07-02 16:18:58 INFO: User interface server not enabled
2016-07-02 16:18:58 INFO: nxt.debugTraceQuote = """
2016-07-02 16:18:58 INFO: nxt.debugTraceSeparator = " "
2016-07-02 16:18:58 INFO: nxt.debugLogUnconfirmed = "false"
2016-07-02 16:18:58 INFO: nxt.debugTraceAccounts not defined
2016-07-02 16:18:58 INFO: nxt.debugTraceLog = "nxt-trace.csv"
2016-07-02 16:18:58 FINE: Running 2 tasks...
2016-07-02 16:18:58 FINE: Loading known peers from the database...
2016-07-02 16:18:58 FINE: Database connection pool current size: 2
2016-07-02 16:18:58 INFO: Genesis block already in database
2016-07-02 16:18:58 FINE: Rollback from block 4898744352561956279 at height 853015 to 4898744352561956279 at 853015
2016-07-02 16:18:59 FINE: Average database transaction time is 1,267 seconds
2016-07-02 16:18:59 INFO: Last block height: 853015
2016-07-02 16:18:59 INFO: nxt.forceScan = "false"
2016-07-02 16:18:59 FINE: Running 2 final tasks...
2016-07-02 16:18:59 INFO: Looking for UPnP gateway device...
2016-07-02 16:18:59 INFO: nxt.apiServerEnforcePOST = "true"
2016-07-02 16:18:59 INFO: nxt.upnpGatewayTimeout not defined or not numeric, using default value 7000
2016-07-02 16:18:59 INFO: nxt.upnpDiscoverTimeout not defined or not numeric, using default value 3000
2016-07-02 16:18:59 INFO: Started API server at 127.0.0.1:7876
2016-07-02 16:18:59 FINE: UPnP gateway device found on 192.168.178.28
2016-07-02 16:18:59 FINE: Using UPnP gateway device on 192.168.178.28
2016-07-02 16:18:59 INFO: External IP address is 37.201.3.0
2016-07-02 16:18:59 FINE: Unable to map port 7874
2016-07-02 16:18:59 INFO: Started peer networking server at 0.0.0.0:7874
2016-07-02 16:18:59 FINE: Starting 9 background jobs
2016-07-02 16:18:59 FINE: Starting 2 delayed tasks
2016-07-02 16:18:59 FINE: Known peers: 289
2016-07-02 16:18:59 INFO: Initialization took 9 seconds
2016-07-02 16:18:59 INFO: Nxt server 1.9.2 started successfully.
2016-07-02 16:18:59 INFO: Copyright © 2013-2016 The Nxt Core Developers.
2016-07-02 16:18:59 INFO: Distributed under GPLv2, with ABSOLUTELY NO WARRANTY.
2016-07-02 16:18:59 INFO: Client UI is at http://localhost:7876/index.html
2016-07-02 16:18:59 FINE: Peer 62.75.159.113 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-02 16:19:07 FINE: Database connection pool current size: 3
2016-07-02 16:19:07 FINE: Database connection pool current size: 4
2016-07-02 16:19:07 FINE: Database connection pool current size: 5
2016-07-02 16:19:30 FINE: Peer 217.26.24.27 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-02 16:20:20 FINE: Peer 164.132.96.27 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-02 16:20:27 FINE: Peer 178.150.207.53 version 1.9.2 returned error: {"error":"Blockchain download in progress"}, request was: {"protocol":1,"requestType":"processTransactions","transactions":[{"senderPublicKey":"4589d4b1d7fb7dcc7330772174088826140bb18a683128739b3234d0bade8b60","attachment":{"currency":"12966877553254092177","units":1,"version.ExchangeBuy":1,"rateNQT":9621473948},"subtype":5,"amountNQT":0,"signature":"64ff9186f3d131dde50ac306df056e46ca85a9b9f4fd0a7f161b544e17ae1b030346dc8e699114f90e712a0ad49620c32f97f1ec038ec5f7ae400a45524581f8","feeNQT":100000000,"ecBlockHeight":853006,"type":5,"deadline":1440,"version":1,"timestamp":82174821,"ecBlockId":"16360037864598716898"}]}, disconnecting
2016-07-02 16:20:50 FINE: Peer 40.117.102.79 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-02 16:20:51 FINE: Peer 78.244.125.22 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-02 19:28:11 FINE: Peer 99.224.242.103 version 1.9.1e returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-03 13:06:13 FINE: Error sending request to peer 122.9.34.152: WebSocket session is not open
2016-07-03 13:06:34 FINE: Connect: announced address home.kaerner.net now points to 91.7.18.12, replacing peer 91.7.29.208
2016-07-03 13:06:43 FINE: Blacklisting 212.227.135.232 because of: java.net.UnknownHostException: paynet.org: unknown error
2016-07-03 13:06:43 FINE: Blacklisting 188.78.24.184 because of: java.net.UnknownHostException: abuminer.ddns.net: unknown error
2016-07-03 13:06:45 FINE: Peer 80.150.243.11 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-03 13:06:51 FINE: Peer 136.243.5.70 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-03 13:06:54 FINE: Average database transaction time is 0,022 seconds
2016-07-03 13:06:56 FINE: Peer 40.117.102.79 version 1.9.2 returned error: {"error":"Blockchain download in progress"}, request was: {"protocol":1,"requestType":"getCumulativeDifficulty"}, disconnecting
2016-07-03 13:07:24 FINE: Will process a fork of 719 blocks, mine is 1
2016-07-03 13:07:24 FINE: Rollback from block 2137618009458082601 at height 853024 to 3637974694739851623 at 853023
2016-07-03 13:08:12 FINE: Blacklisting 88.130.202.12 because of: java.net.UnknownHostException: ct.flipflop.mooo.com: unknown error
2016-07-03 13:08:22 FINE: SQL statement required 57,515 seconds at height 853032:
SELECT 1 FROM account WHERE id = ?  AND height < ? LIMIT 1
  nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:319)
  nxt.db.VersionedEntityDbTable.delete(VersionedEntityDbTable.java:56)
  nxt.Account.save(Account.java:1120)
  nxt.Account.addToBalanceNQT(Account.java:1669)
  nxt.TransactionType.apply(TransactionType.java:235)
  nxt.Attachment$AbstractAttachment.apply(Attachment.java:64)
  nxt.TransactionImpl.apply(TransactionImpl.java:1056)
  nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:1568)
  nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:1380)
  nxt.BlockchainProcessorImpl.access$1100(BlockchainProcessorImpl.java:64)
  nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:605)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:586)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:287)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:200)
2016-07-03 13:08:23 FINE: Database transaction required 58,671 seconds at height 853032
  nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:1388)
  nxt.BlockchainProcessorImpl.access$1100(BlockchainProcessorImpl.java:64)
  nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:605)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:586)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:287)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:200)
2016-07-03 13:08:37 FINE: Transaction 13181342206891055227 has been released
2016-07-03 13:08:37 FINE: Early finish of transaction 13181342206891055227 at height 853374
2016-07-03 13:08:40 FINE: Transaction 9096774363849097625 has been rejected
2016-07-03 13:08:48 FINE: Switched to peer's fork
2016-07-03 13:08:48 INFO: Blockchain download in progress
2016-07-03 13:08:49 FINE: Got 2 confirmations
2016-07-03 13:08:49 INFO: Downloaded 719 blocks in 112 s, 6 per s, 1 min left
2016-07-03 13:09:29 FINE: Got 2 confirmations
2016-07-03 13:09:29 INFO: Downloaded 469 blocks in 39 s, 7 per s, 0 min left
2016-07-03 13:09:32 FINE: Peer 217.26.24.27 version null returned error: {"error":"Maximum number of inbound connections exceeded"}, request was: {"protocol":1,"application":"NRS","requestType":"getInfo","services":"0","version":"1.9.2","platform":"Mac OS X x86_64","shareAddress":true}, disconnecting
2016-07-03 13:10:02 INFO: Finished blockchain download
2016-07-03 13:10:13 FINE: Deleted 61 expired prunable data from prunable_message
2016-07-03 13:10:13 FINE: Reduced tag count for nxttycoin by 1
2016-07-03 13:10:13 FINE: Deleted 1 expired prunable data from tagged_data
2016-07-03 13:10:13 FINE: Database transaction required 61,374 seconds at height 854212
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1082)
  nxt.BlockchainProcessorImpl.lambda$null$32(BlockchainProcessorImpl.java:1007)
<snip>
2016-07-03 14:46:41 INFO: Shutting down...
2016-07-03 14:46:41 INFO: nxt.maxNumberOfMonitors = "100"
2016-07-03 14:46:41 INFO: Stopping background jobs...
2016-07-03 14:46:41 INFO: shutting down scheduledThreadPool
2016-07-03 14:46:41 INFO: ...Done
2016-07-03 14:46:41 FINE: Mapping deleted for port 7874
2016-07-03 14:46:41 INFO: shutting down sendingService
2016-07-03 14:46:41 INFO: shutting down peersService
2016-07-03 14:46:46 INFO: Database shutdown completed
2016-07-03 14:46:46 INFO: Nxt server 1.9.2 stopped.

There are a lot of "Maximum number of inbound connections exceeded" errors, is this normal?
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 04, 2016, 09:25:40 am
It seems to me that the new version download buttons don't work in the desktop app.
Is that already known?
If this not a bug but a known limitation of the underlying JavaFX system, I want to suggest to hide the whole dialog. I've just had a support request on our helpdesk because of this issue. I assume that every outgoing link wouldn't work then, or is putting the forums announcement link there an option?

I can probably fix this. Please open a ticket on bitbucket.

Done.
Title: Re: NRS v1.9.2
Post by: lurker10 on July 04, 2016, 09:34:30 am
There's a support request from a mac guy:

Quote
Here is the log and i dont think it holds anything usefull :/ I really wonder why i can get to the contents of the folder and start the server directly with the nxt.jar file and access it later on browser.
I need to kill the jar proccess on console to disable it again.
The client itself when i start still pops up the nxt icon and the jar icon and close before it opens.

Here is the nxt.log:

There are a lot of "Maximum number of inbound connections exceeded" errors, is this normal?

To kill the java process.
Open Terminal, type 'top', you will see all running processes on your Mac. Note the java process, and its PID.
type 'q' to exit the top command.
type 'kill -15 PID' where PID is the number of the java process.

"Maximum number of inbound connections exceeded" errors are fine, they indicate that the peer your client tries to make connection to doesn't accept more connections. Your client will go on to connect to other peers, there are many.

Clicking on the .jar file should be able to start nxt, because .jar files are associated with java application, so it's perfectly normal that nxt starts when you click on nxt.jar.
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 04, 2016, 09:36:57 am
There's a support request from a mac guy:

Quote
Here is the log and i dont think it holds anything usefull :/ I really wonder why i can get to the contents of the folder and start the server directly with the nxt.jar file and access it later on browser.
I need to kill the jar proccess on console to disable it again.
The client itself when i start still pops up the nxt icon and the jar icon and close before it opens.

Here is the nxt.log:

There are a lot of "Maximum number of inbound connections exceeded" errors, is this normal?

To kill the java process.
Open Terminal, type 'top', you will see all running processes on your Mac. Note the java process, and its PID.
type 'q' to exit the top command.
type 'kill -15 PID' where PID is the number of the java process.

"Maximum number of inbound connections exceeded" errors are fine, they indicate that the peer your client tries to make connection to doesn't accept more connections. Your client will go on to connect to other peers, there are many.

Clicking on the .jar file should be able to start nxt, because .jar files are associated with java application, so it's perfectly normal that nxt starts when you click on nxt.jar.

Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.
Title: Re: NRS v1.9.2
Post by: lurker10 on July 04, 2016, 09:40:42 am
There's a support request from a mac guy:

Quote
Here is the log and i dont think it holds anything usefull :/ I really wonder why i can get to the contents of the folder and start the server directly with the nxt.jar file and access it later on browser.
I need to kill the jar proccess on console to disable it again.
The client itself when i start still pops up the nxt icon and the jar icon and close before it opens.

Here is the nxt.log:

There are a lot of "Maximum number of inbound connections exceeded" errors, is this normal?

To kill the java process.
Open Terminal, type 'top', you will see all running processes on your Mac. Note the java process, and its PID.
type 'q' to exit the top command.
type 'kill -15 PID' where PID is the number of the java process.

"Maximum number of inbound connections exceeded" errors are fine, they indicate that the peer your client tries to make connection to doesn't accept more connections. Your client will go on to connect to other peers, there are many.

Clicking on the .jar file should be able to start nxt, because .jar files are associated with java application, so it's perfectly normal that nxt starts when you click on nxt.jar.

Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.

I haven't run JavaFX app, just the standard nxt client.
I remember there was an issue of the app shutting down immediately because Mac had Java 7. Are you sure you run Java 8?
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 04, 2016, 09:44:38 am
There's a support request from a mac guy:

Quote
Here is the log and i dont think it holds anything usefull :/ I really wonder why i can get to the contents of the folder and start the server directly with the nxt.jar file and access it later on browser.
I need to kill the jar proccess on console to disable it again.
The client itself when i start still pops up the nxt icon and the jar icon and close before it opens.

Here is the nxt.log:

There are a lot of "Maximum number of inbound connections exceeded" errors, is this normal?

To kill the java process.
Open Terminal, type 'top', you will see all running processes on your Mac. Note the java process, and its PID.
type 'q' to exit the top command.
type 'kill -15 PID' where PID is the number of the java process.

"Maximum number of inbound connections exceeded" errors are fine, they indicate that the peer your client tries to make connection to doesn't accept more connections. Your client will go on to connect to other peers, there are many.

Clicking on the .jar file should be able to start nxt, because .jar files are associated with java application, so it's perfectly normal that nxt starts when you click on nxt.jar.

Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.

I haven't run JavaFX app, just the standard nxt client.
I remember there was an issue of the app shutting down immediately because Mac had Java 7. Are you sure you run Java 8?

IMHO the NRS brings it's own java with it.
Here's the start of the logfile with the relevant information, I had to snip it because of the forum's post size limitations:
Code: [Select]
2016-07-02 16:18:49 INFO: nxt.enableStackTraces = "true"
2016-07-02 16:18:49 INFO: nxt.enableLogTraceback = "false"
2016-07-02 16:18:49 INFO: logging enabled
2016-07-02 16:18:49 INFO: socksProxyHost not defined
2016-07-02 16:18:49 INFO: socksProxyPort not defined
2016-07-02 16:18:49 FINE: java.version = 1.8.0_91
2016-07-02 16:18:49 FINE: java.vm.version = 25.91-b14
2016-07-02 16:18:49 FINE: java.vm.name = Java HotSpot(TM) 64-Bit Server VM
2016-07-02 16:18:49 FINE: java.vendor = Oracle Corporation
2016-07-02 16:18:49 FINE: java.vm.vendor = Oracle Corporation
2016-07-02 16:18:49 FINE: java.home = /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
2016-07-02 16:18:49 FINE: java.library.path = /Users/christiangrieger/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
2016-07-02 16:18:49 FINE: java.class.path = /Applications/nxt.app/nxt.jar
2016-07-02 16:18:49 FINE: os.arch = x86_64
2016-07-02 16:18:49 FINE: sun.arch.data.model = 64
2016-07-02 16:18:49 FINE: os.name = Mac OS X
2016-07-02 16:18:49 FINE: file.encoding = UTF-8
2016-07-02 16:18:49 FINE: java.security.policy = null
2016-07-02 16:18:49 FINE: java.security.manager = null
2016-07-02 16:18:49 FINE: nxt.runtime.mode = null
2016-07-02 16:18:49 FINE: nxt.runtime.dirProvider = null
2016-07-02 16:18:49 FINE: availableProcessors = 4
2016-07-02 16:18:49 FINE: maxMemory = 1908932608
2016-07-02 16:18:49 FINE: processId = 7709
2016-07-02 16:18:49 INFO: nxt.isTestnet = "false"
2016-07-02 16:18:49 INFO: nxt.isOffline = "false"
2016-07-02 16:18:49 INFO: nxt.maxRollback = "800"
2016-07-02 16:18:49 INFO: nxt.forgingDelay = "20"
2016-07-02 16:18:49 INFO: nxt.forgingSpeedup = "3"
2016-07-02 16:18:49 INFO: nxt.maxPrunableLifetime = "7776000"
2016-07-02 16:18:49 INFO: nxt.includeExpiredPrunable = "true"
2016-07-02 16:18:49 INFO: nxt.correctInvalidFees = "false"
2016-07-02 16:18:49 INFO: nxt.statementLogThreshold = "10000"
2016-07-02 16:18:49 INFO: nxt.transactionLogThreshold = "15000"
2016-07-02 16:18:49 INFO: nxt.transactionLogInterval = "15"
2016-07-02 16:18:49 INFO: nxt.dbCacheKB = "0"
2016-07-02 16:18:49 INFO: nxt.dbUrl not defined
2016-07-02 16:18:49 INFO: nxt.dbType = "h2"
2016-07-02 16:18:49 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-07-02 16:18:49 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-07-02 16:18:49 INFO: nxt.dbUsername = "sa"
2016-07-02 16:18:49 INFO: nxt.dbPassword = "{not logged}"
2016-07-02 16:18:49 INFO: nxt.maxDbConnections = "30"
2016-07-02 16:18:49 INFO: nxt.dbLoginTimeout = "70"
2016-07-02 16:18:49 INFO: nxt.dbDefaultLockTimeout = "60"
2016-07-02 16:18:49 INFO: nxt.dbMaxMemoryRows = "1000000"
2016-07-02 16:18:49 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-07-02 16:18:50 INFO: nxt.useStrongSecureRandom = "false"
2016-07-02 16:18:57 FINE: Database connection pool current size: 1
2016-07-02 16:18:57 INFO: Database update may take a while if needed, current db version 489...
2016-07-02 16:18:57 INFO: nxt.enableTransactionRebroadcasting = "true"
2016-07-02 16:18:57 INFO: nxt.testUnconfirmedTransactions not defined, assuming false
2016-07-02 16:18:57 INFO: nxt.maxUnconfirmedTransactions = "2000"
2016-07-02 16:18:57 INFO: nxt.trimDerivedTables = "true"
2016-07-02 16:18:57 INFO: nxt.numberOfForkConfirmations = "2"
2016-07-02 16:18:57 INFO: nxt.trimFrequency = "1000"
2016-07-02 16:18:57 INFO: nxt.disableGetMoreBlocksThread not defined, assuming false
2016-07-02 16:18:57 INFO: nxt.disableProcessTransactionsThread not defined, assuming false
2016-07-02 16:18:57 INFO: nxt.disableRemoveUnconfirmedTransactionsThread not defined, assuming false
2016-07-02 16:18:57 INFO: nxt.disableProcessWaitingTransactionsThread not defined, assuming false
2016-07-02 16:18:57 INFO: nxt.disableRebroadcastTransactionsThread not defined, assuming false
2016-07-02 16:18:57 INFO: nxt.enablePublicKeyCache = "true"
2016-07-02 16:18:57 INFO: nxt.ledgerTrimKeep = "30000"
2016-07-02 16:18:57 INFO: nxt.ledgerAccounts = "*"
2016-07-02 16:18:57 INFO: Account ledger is tracking all accounts
2016-07-02 16:18:57 INFO: nxt.ledgerLogUnconfirmed = "2"
2016-07-02 16:18:57 INFO: nxt.processPolls = "true"
2016-07-02 16:18:57 INFO: nxt.deleteFinishedShufflings = "false"
2016-07-02 16:18:57 INFO: nxt.logFxtBalance not defined
2016-07-02 16:18:57 INFO: nxt.hideErrorDetails = "false"
2016-07-02 16:18:57 INFO: nxt.myPlatform not defined
2016-07-02 16:18:57 INFO: nxt.myAddress not defined
2016-07-02 16:18:57 INFO: nxt.peerServerPort = "7874"
2016-07-02 16:18:57 INFO: nxt.shareMyAddress = "true"
2016-07-02 16:18:57 INFO: nxt.enablePeerUPnP = "true"
2016-07-02 16:18:57 INFO: nxt.myHallmark not defined
2016-07-02 16:18:57 INFO: nxt.adminPassword not defined
2016-07-02 16:18:57 INFO: nxt.maxAPIRecords = "100"
2016-07-02 16:18:57 INFO: nxt.enableAPIUPnP = "false"
2016-07-02 16:18:57 INFO: nxt.disabledAPIs not defined
2016-07-02 16:18:57 INFO: nxt.disabledAPITags not defined
2016-07-02 16:18:57 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-07-02 16:18:57 INFO: nxt.enableAPIServer = "true"
2016-07-02 16:18:57 INFO: nxt.apiServerPort = "7876"
2016-07-02 16:18:57 INFO: nxt.apiServerSSLPort = "7876"
2016-07-02 16:18:57 INFO: nxt.apiServerHost = "127.0.0.1"
2016-07-02 16:18:57 INFO: nxt.disableAdminPassword = "false"
2016-07-02 16:18:57 INFO: nxt.apiSSL = "false"
2016-07-02 16:18:57 INFO: nxt.apiServerIdleTimeout = "30000"
2016-07-02 16:18:57 INFO: API server using HTTP port 7876
2016-07-02 16:18:57 INFO: nxt.apiResourceBase = "./html/ui"
2016-07-02 16:18:57 INFO: nxt.apiWelcomeFile = "index.html"
2016-07-02 16:18:57 INFO: nxt.javadocResourceBase = "./html/doc"
2016-07-02 16:18:57 INFO: nxt.maxUploadFileSize not defined or not numeric, using default value 0
2016-07-02 16:18:58 INFO: nxt.enableAPIServerGZIPFilter = "false"
2016-07-02 16:18:58 INFO: nxt.apiServerCORS = "false"
2016-07-02 16:18:58 INFO: nxt.apiFrameOptionsSameOrigin = "true"
Title: Re: NRS v1.9.2
Post by: lurker10 on July 04, 2016, 09:47:05 am
IMHO the NRS brings it's own java with it.
Here's the start of the logfile with the relevant information, I had to snip it because of the forum's post size limitations:

ok, you do have Java 8.
Then I am out of here, haven't dealt with JavaFX app, can only advise on the standard console client.
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 04, 2016, 09:47:48 am
IMHO the NRS brings it's own java with it.
Here's the start of the logfile with the relevant information, I had to snip it because of the forum's post size limitations:

ok, you do have Java 8.
Then I am out of here, haven't dealt with JavaFX app, can only advise on the standard console client.

No problem, thanks for your help!  :)
Title: Re: NRS v1.9.2
Post by: Riker on July 04, 2016, 10:29:11 am
Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.

Perhaps he logs out from the user session and this kills the Java process ?
Please double check with the user.
If so, he will have to start the process from the command line using nohup command or a similar Mac specific procedure to make the application run in the background.
Title: Re: NRS v1.9.2
Post by: lurker10 on July 04, 2016, 06:19:05 pm
I found settings which seem to work reasonably stable with version 1.9.2 (at least for 24 hours) on a virtual machine on Windows Azure (Size A0, Ubuntu, RAM 0,75 GB). See: https://azure.microsoft.com/en-in/pricing/details/virtual-machines/

The settings are:
In run.sh add parameters: ${JAVA} -Xms200m -Xmx200m
In nxt.properties:
nxt.maxNumberOfInboundConnections=30
nxt.maxNumberOfOutboundConnections=15
nxt.maxNumberOfConnectedPublicPeers=15
nxt.maxNumberOfKnownPeers=500
nxt.minNumberOfKnownPeers=100

However, with these settings, the node is not accepted at: nsc.nxt.org
Even with: nxt.wellKnownPeers=nsc.nxt.org
The node is visible at: www.peerexplorer.com/nodes

I will also try with a Raspberry Pi (1GB RAM). To get more permanent public nodes in the future, I think support for VMs on Amazon and Azure + low-cost devices such as the Pi is a good way to go.

It doesn't make a lot of sense to set up many nodes at two hosting companies. You need them all around the world, decentralized.
Title: Re: NRS v1.9.2
Post by: abctc on July 04, 2016, 07:15:58 pm
I found settings which seem to work reasonably stable with version 1.9.2 (at least for 24 hours) on a virtual machine on Windows Azure (Size A0, Ubuntu, RAM 0,75 GB). ...
- also you can try this:

Code: [Select]
nxt.dbCacheKB=16000
nxt.enablePublicKeyCache=false
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 05, 2016, 09:26:15 am
Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.

Perhaps he logs out from the user session and this kills the Java process ?
Please double check with the user.
If so, he will have to start the process from the command line using nohup command or a similar Mac specific procedure to make the application run in the background.

The user answered:
Quote
The nxt.jar runs well without interface in the background when i double click it :) just the problem with the inbuild browser that does not start when i click the icon.
IMHO the problem is JavaFX-related but I don't know how to trouble-shoot this on a mac.  ::)
Title: Re: NRS v1.9.2
Post by: qq2536007339 on July 06, 2016, 02:22:09 am
NRS 1.9.2 seems need less memory than 1.9.1e,but still I get "java.lang.OutOfMemoryError: Java heap space" at block 858000,after restart back to normal.
Title: Re: NRS v1.9.2
Post by: Riker on July 06, 2016, 05:19:13 am
Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.

Perhaps he logs out from the user session and this kills the Java process ?
Please double check with the user.
If so, he will have to start the process from the command line using nohup command or a similar Mac specific procedure to make the application run in the background.

The user answered:
Quote
The nxt.jar runs well without interface in the background when i double click it :) just the problem with the inbuild browser that does not start when i click the icon.
IMHO the problem is JavaFX-related but I don't know how to trouble-shoot this on a mac.  ::)

Still don't understand the issue. Is it the Java processes that's being terminated or just the JavaFX wallet window ?
If the it's just the Window they should see the tray icon still available. From the log it looks like the Java process itself was closed more than an hour after it was started.
Code: [Select]
2016-07-03 13:10:13 FINE: Database transaction required 61,374 seconds at height 854212
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1082)
  nxt.BlockchainProcessorImpl.lambda$null$32(BlockchainProcessorImpl.java:1007)
<snip>
2016-07-03 14:46:41 INFO: Shutting down...
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 06, 2016, 06:41:00 am
Thanks but the real problem is that the JavaFX app is immediately shutting down after starting.

Perhaps he logs out from the user session and this kills the Java process ?
Please double check with the user.
If so, he will have to start the process from the command line using nohup command or a similar Mac specific procedure to make the application run in the background.

The user answered:
Quote
The nxt.jar runs well without interface in the background when i double click it :) just the problem with the inbuild browser that does not start when i click the icon.
IMHO the problem is JavaFX-related but I don't know how to trouble-shoot this on a mac.  ::)

Still don't understand the issue. Is it the Java processes that's being terminated or just the JavaFX wallet window ?
If the it's just the Window they should see the tray icon still available. From the log it looks like the Java process itself was closed more than an hour after it was started.
Code: [Select]
2016-07-03 13:10:13 FINE: Database transaction required 61,374 seconds at height 854212
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1082)
  nxt.BlockchainProcessorImpl.lambda$null$32(BlockchainProcessorImpl.java:1007)
<snip>
2016-07-03 14:46:41 INFO: Shutting down...

Just the JavaFX wallet window. Has the tray icon the same functions on a mac like on windows? I will ask the user about it, maybe he has missed it.
Title: Re: NRS v1.9.2
Post by: Riker on July 06, 2016, 07:43:25 am
Just the JavaFX wallet window. Has the tray icon the same functions on a mac like on windows? I will ask the user about it, maybe he has missed it.

On my mac, the NXT tray icon appears in the upper right status bar. It has the same functions as on Windows except that the left and right mouse buttons are switched.
So far no one has complained about this.
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 06, 2016, 09:48:57 am
Just the JavaFX wallet window. Has the tray icon the same functions on a mac like on windows? I will ask the user about it, maybe he has missed it.

On my mac, the NXT tray icon appears in the upper right status bar. It has the same functions as on Windows except that the left and right mouse buttons are switched.
So far no one has complained about this.

The user wrote:
Quote
Yep the Icon is there for about 5 seconds and i am able to Click one Time to Open the App but then it Close the Icon and no App Starts.

Could it happen that the JavaFX part crashes and the Java code continue to run? Because after that the user can successfully start the wallet in a browser.
What JavaFX version do we have in 1.9.2?
Title: Re: NRS v1.9.2
Post by: farl4bit on July 07, 2016, 08:02:52 am
I reported this problem before: On my mac the client will get stuck after a few days forging and staying open. I see a hand-cursor when I hover above links in the client, but when I click on them nothing happens.

When I keep the app open and I go to http://localhost:7876/index.html. I get homescreen of Nxt with the options "Returning User" or "New? Create your own account". Can this be fixed? And am I forging correctly then? It seems I get much less blocks even I bought a bigger stake.  :(
Title: Re: NRS v1.9.2
Post by: farl4bit on July 07, 2016, 09:08:51 am
Another thing that is not right for people using a Mac:

When I download the Nxt-installer I see this window:

(http://i.imgur.com/uUDPOmB.png)

But why would I want to add the installer to my Application folder? After this installation I have the Nxt client and the Nxt installer in my Applications folder. On a Mac this is not normal usage.

Hope you can fix this too? It would help the Mac-users.   :)
Title: Re: NRS v1.9.2
Post by: chevdor on July 07, 2016, 09:34:12 am
Another thing that is not right for people using a Mac:

When I download the Nxt-installer I see this window:

(http://i.imgur.com/uUDPOmB.png)

But why would I want to add the installer to my Application folder? After this installation I have the Nxt client and the Nxt installer in my Applications folder. On a Mac this is not normal usage.

Hope you can fix this too? It would help the Mac-users.   :)

I agree :)
The good things are:
- even if this is not optimum, it will work for the regular Joe
- since the executable is named properly, the advanced Joe will know it makes no sense and running the installer from the DMG without putting it in the Applications will be better

Title: Re: NRS v1.9.2
Post by: Riker on July 07, 2016, 03:27:43 pm
I reported this problem before: On my mac the client will get stuck after a few days forging and staying open. I see a hand-cursor when I hover above links in the client, but when I click on them nothing happens.

When I keep the app open and I go to http://localhost:7876/index.html. I get homescreen of Nxt with the options "Returning User" or "New? Create your own account". Can this be fixed? And am I forging correctly then? It seems I get much less blocks even I bought a bigger stake.  :(

Do you see any errors in the nxt.log when this happens ?
I'll try to forge on my Mac for a while to see if I can reproduce this.

The fact that the web wallet treats you as a new user is normal since the desktop wallet and web wallet does not share their local storage. Accounts that one of them remembers the other does not.
Title: Re: NRS v1.9.2
Post by: Riker on July 07, 2016, 03:39:21 pm
Another thing that is not right for people using a Mac:

But why would I want to add the installer to my Application folder? After this installation I have the Nxt client and the Nxt installer in my Applications folder. On a Mac this is not normal usage.

Hope you can fix this too? It would help the Mac-users.   :)

I agree :)
The good things are:
- even if this is not optimum, it will work for the regular Joe
- since the executable is named properly, the advanced Joe will know it makes no sense and running the installer from the DMG without putting it in the Applications will be better

Not sure I can do much about this. The NXT Java based installer (IzPack) is reused between Windows, Linux and Mac. This has many benefits from maintenance perspective, just recall the Wesley installer that always lagged few versions behind. Now we have an installer which can be automatically generated in minutes, digitally signed and also bundles Java inside it.

Mac being IzPack's least supported platform is quite a challenge to work with.
Eventually I used another tool called "Java packager" to package the IzPack installer itself as a Mac application and hacked the resulting NXT package to look like yet another Mac application. This is the reason you actually see two applications.
My understanding is that the dialog you are seeing when running the .dmg file is pretty standard.
And the NXT installer is really an application that it's sole purpose is to install the NXT package.
Not sure how we can further simplify this.
Title: Re: NRS v1.9.2
Post by: farl4bit on July 07, 2016, 08:49:29 pm
I don't know too. But this is not how it works on a Mac. Very confusing. Installing Nxt not being an administrator is also very difficult. Can't seem to create the correct folder properly.
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 12, 2016, 06:18:18 am
I have this strange issue as a support request in our Helpdesk.
This guy uses the browser wallet on a mac. He has created two different accounts with one passphrase (apparently with a  typo). But the strange thing is that his wallet showed him the exact same public key for both accounts. Now the one account he can't get access to is initialized and he funded it with 21k NXT. He already tried Jones' typo generator tool but hasn't found the correct passphrase yet. :(

Quote
Thanks so much for your suggestion.  I find one thing curious though about my 2 accounts.  My “good account”, the original one that I know the passphrase for…..when I logged in yesterday with the passphrase, I got the message….

 Welcome to your new NXT account. Your account ID is NXT-C34X-95UD-99U4-82DQB - When funding your account for the first time, you can increase security by also providing your public key, which is 98bc089eac6592d3c15f9e813530a8a8053d903538a2a04c231617e422c3103c

When I just logged in to this account with the passphrase, I got the message…

Welcome to your new NXT account. Your account ID is NXT-C34X-95UD-99U4-82DQB - When funding your account for the first time, you can increase security by also providing your public key, which is 5efe8c27ab516c810fb22d487af312580a9b5f4d47556292bdcca84fe815f77e

As you suggested previously, I will not fund either account, but I am curious that I have 2 public keys for the account.  Once again, I thank you for your patience and help!!

He created the first account with version 1.8.2 and the second with 1.9.2. Is this a strange browser refresh issue or what can be the cause for the wrong public key?
Title: Re: NRS v1.9.2
Post by: Riker on July 12, 2016, 06:58:51 am
I have this strange issue as a support request in our Helpdesk.
This guy uses the browser wallet on a mac. He has created two different accounts with one passphrase (apparently with a  typo). But the strange thing is that his wallet showed him the exact same public key for both accounts. Now the one account he can't get access to is initialized and he funded it with 21k NXT. He already tried Jones' typo generator tool but hasn't found the correct passphrase yet. :(

Quote
Thanks so much for your suggestion.  I find one thing curious though about my 2 accounts.  My “good account”, the original one that I know the passphrase for…..when I logged in yesterday with the passphrase, I got the message….

 Welcome to your new NXT account. Your account ID is NXT-C34X-95UD-99U4-82DQB - When funding your account for the first time, you can increase security by also providing your public key, which is 98bc089eac6592d3c15f9e813530a8a8053d903538a2a04c231617e422c3103c

When I just logged in to this account with the passphrase, I got the message…

Welcome to your new NXT account. Your account ID is NXT-C34X-95UD-99U4-82DQB - When funding your account for the first time, you can increase security by also providing your public key, which is 5efe8c27ab516c810fb22d487af312580a9b5f4d47556292bdcca84fe815f77e

As you suggested previously, I will not fund either account, but I am curious that I have 2 public keys for the account.  Once again, I thank you for your patience and help!!

He created the first account with version 1.8.2 and the second with 1.9.2. Is this a strange browser refresh issue or what can be the cause for the wrong public key?

Using the getAccountId API on both public keys I can see that:
Public key 98bc089eac6592d3c15f9e813530a8a8053d903538a2a04c231617e422c3103c maps to account NXT-DK8F-53F8-MK2C-BVS78 - this account has balance of 21002 NXT
Public key 5efe8c27ab516c810fb22d487af312580a9b5f4d47556292bdcca84fe815f77e maps to account NXT-C34X-95UD-99U4-82DQB which is not initialized.
Therefore you need to find the secret phrase for account NXT-DK8F-53F8-MK2C-BVS78 not NXT-C34X-95UD-99U4-82DQB
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 12, 2016, 07:03:31 am
I have this strange issue as a support request in our Helpdesk.
This guy uses the browser wallet on a mac. He has created two different accounts with one passphrase (apparently with a  typo). But the strange thing is that his wallet showed him the exact same public key for both accounts. Now the one account he can't get access to is initialized and he funded it with 21k NXT. He already tried Jones' typo generator tool but hasn't found the correct passphrase yet. :(

Quote
Thanks so much for your suggestion.  I find one thing curious though about my 2 accounts.  My “good account”, the original one that I know the passphrase for…..when I logged in yesterday with the passphrase, I got the message….

 Welcome to your new NXT account. Your account ID is NXT-C34X-95UD-99U4-82DQB - When funding your account for the first time, you can increase security by also providing your public key, which is 98bc089eac6592d3c15f9e813530a8a8053d903538a2a04c231617e422c3103c

When I just logged in to this account with the passphrase, I got the message…

Welcome to your new NXT account. Your account ID is NXT-C34X-95UD-99U4-82DQB - When funding your account for the first time, you can increase security by also providing your public key, which is 5efe8c27ab516c810fb22d487af312580a9b5f4d47556292bdcca84fe815f77e

As you suggested previously, I will not fund either account, but I am curious that I have 2 public keys for the account.  Once again, I thank you for your patience and help!!

He created the first account with version 1.8.2 and the second with 1.9.2. Is this a strange browser refresh issue or what can be the cause for the wrong public key?

Using the getAccountId API on both public keys I can see that:
Public key 98bc089eac6592d3c15f9e813530a8a8053d903538a2a04c231617e422c3103c maps to account NXT-DK8F-53F8-MK2C-BVS78 - this account has balance of 21002 NXT
Public key 5efe8c27ab516c810fb22d487af312580a9b5f4d47556292bdcca84fe815f77e maps to account NXT-C34X-95UD-99U4-82DQB which is not initialized.
Therefore you need to find the secret phrase for account NXT-DK8F-53F8-MK2C-BVS78 not NXT-C34X-95UD-99U4-82DQB

Yes of course. His question was, why was the wrong public key displayed in the browser wallet.
Title: Re: NRS v1.9.2
Post by: Riker on July 12, 2016, 07:36:32 am
Yes of course. His question was, why was the wrong public key displayed in the browser wallet.

I can reproduce the problem, it goes like this:
1. Login with passphrase1 to a new account and check the "Remember Account" option to get publickey1 and account1
2. Logout and login with passphrase2 for a new account to get publickey2 and account2
3. Use "switch account" to switch back to account1 --> you'll now see account1 with publickey2

In the past we used to completely reload the page during "switch account" but now we only update the account state.
However for new account which does not have a public key on the blockchain, we do not update the public key.
Will fix for the next release.

Meanwhile the only option for the user is to try to recover the original passphrase.
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 12, 2016, 09:44:47 am
Yes of course. His question was, why was the wrong public key displayed in the browser wallet.

I can reproduce the problem, it goes like this:
1. Login with passphrase1 to a new account and check the "Remember Account" option to get publickey1 and account1
2. Logout and login with passphrase2 for a new account to get publickey2 and account2
3. Use "switch account" to switch back to account1 --> you'll now see account1 with publickey2

In the past we used to completely reload the page during "switch account" but now we only update the account state.
However for new account which does not have a public key on the blockchain, we do not update the public key.
Will fix for the next release.

Meanwhile the only option for the user is to try to recover the original passphrase.

Thank you, this is very helpful. I will inform the affected user.
Title: Re: NRS v1.9.2
Post by: bitme on July 12, 2016, 01:42:10 pm
I can't send messages in latest version. I get information :
Cannot read property 'files' of undefined
Title: Re: NRS v1.9.2
Post by: Riker on July 13, 2016, 06:03:51 am
I can't send messages in latest version. I get information :
Cannot read property 'files' of undefined

Are you using the desktop wallet ?
Is this a simple message or a file message ?
Title: Re: NRS v1.9.2
Post by: bitme on July 13, 2016, 10:21:01 am
@Riker
 Today I'm sending messages without problem. I'm using desktop wallet and it was information on top of window. Thanks for Your interest in this matter - everything is fine now and i can't repeat that error
Title: Re: NRS v1.9.2
Post by: altsheets on July 13, 2016, 11:11:21 am
1.9.2 is working well.

Just as a side-note: I have always -and now still with 1.9.2.- been getting these, quite often, usually during syncing:

Code: [Select]
2016-07-13 13:00:37 FINE: Error processing API request
java.lang.RuntimeException: java.sql.SQLException: Login timeout
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:237)
        at nxt.Account.getLessors(Account.java:1282)
        at nxt.Account.getLessorsGuaranteedBalanceNQT(Account.java:1233)
        at nxt.Account.getEffectiveBalanceNXT(Account.java:1221)
        at nxt.http.JSONData.accountBalance(JSONData.java:73)
        at nxt.http.JSONData.accountBalance(JSONData.java:55)
        at nxt.http.GetAccount.processRequest(GetAccount.java:46)
        at nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:93)
        at nxt.http.APIServlet.process(APIServlet.java:491)
        at nxt.http.APIServlet.doGet(APIServlet.java:420)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
        at nxt.http.API$XFrameOptionsFilter.doFilter(API.java:374)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:406)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1182)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
        at org.eclipse.jetty.server.Server.handle(Server.java:524)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
        at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Login timeout
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208)
        at nxt.db.BasicDb.getPooledConnection(BasicDb.java:184)
        at nxt.db.BasicDb.getConnection(BasicDb.java:178)
        at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:218)
        ... 36 more
2016-07-13 13:00:37 FINE: Error processing API request
java.lang.RuntimeException: java.sql.SQLException: Login timeout
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:237)
        at nxt.Account.getLessors(Account.java:1282)
        at nxt.Account.getLessorsGuaranteedBalanceNQT(Account.java:1233)
        at nxt.Account.getEffectiveBalanceNXT(Account.java:1221)
        at nxt.http.JSONData.accountBalance(JSONData.java:73)
        at nxt.http.JSONData.accountBalance(JSONData.java:55)
        at nxt.http.GetAccount.processRequest(GetAccount.java:46)
        at nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:93)
        at nxt.http.APIServlet.process(APIServlet.java:491)
        at nxt.http.APIServlet.doGet(APIServlet.java:420)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
        at nxt.http.API$XFrameOptionsFilter.doFilter(API.java:374)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:406)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1182)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
        at org.eclipse.jetty.server.Server.handle(Server.java:524)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
        at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Login timeout
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208)
        at nxt.db.BasicDb.getPooledConnection(BasicDb.java:184)
        at nxt.db.BasicDb.getConnection(BasicDb.java:178)
        at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:218)
        ... 36 more
2016-07-13 13:00:37 FINE: Error processing API request
java.lang.RuntimeException: java.sql.SQLException: Login timeout
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:237)
        at nxt.Account.getLessors(Account.java:1282)
        at nxt.Account.getLessorsGuaranteedBalanceNQT(Account.java:1233)
        at nxt.Account.getEffectiveBalanceNXT(Account.java:1221)
        at nxt.http.JSONData.accountBalance(JSONData.java:73)
        at nxt.http.JSONData.accountBalance(JSONData.java:55)
        at nxt.http.GetAccount.processRequest(GetAccount.java:46)
        at nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:93)
        at nxt.http.APIServlet.process(APIServlet.java:491)
        at nxt.http.APIServlet.doGet(APIServlet.java:420)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
        at nxt.http.API$XFrameOptionsFilter.doFilter(API.java:374)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:406)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1182)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
        at org.eclipse.jetty.server.Server.handle(Server.java:524)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
        at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Login timeout
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208)
        at nxt.db.BasicDb.getPooledConnection(BasicDb.java:184)
        at nxt.db.BasicDb.getConnection(BasicDb.java:178)
        at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:218)
        ... 36 more
2016-07-13 13:00:37 FINE: Error processing API request
java.lang.RuntimeException: java.sql.SQLException: Login timeout
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:237)
        at nxt.Account.getLessors(Account.java:1282)
        at nxt.Account.getLessorsGuaranteedBalanceNQT(Account.java:1233)
        at nxt.Account.getEffectiveBalanceNXT(Account.java:1221)
        at nxt.http.JSONData.accountBalance(JSONData.java:73)
        at nxt.http.JSONData.accountBalance(JSONData.java:55)
        at nxt.http.GetAccount.processRequest(GetAccount.java:46)
        at nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:93)
        at nxt.http.APIServlet.process(APIServlet.java:491)
        at nxt.http.APIServlet.doGet(APIServlet.java:420)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
        at nxt.http.API$XFrameOptionsFilter.doFilter(API.java:374)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:406)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1182)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
        at org.eclipse.jetty.server.Server.handle(Server.java:524)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
        at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Login timeout
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208)
        at nxt.db.BasicDb.getPooledConnection(BasicDb.java:184)
        at nxt.db.BasicDb.getConnection(BasicDb.java:178)
        at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:218)
        ... 36 more
2016-07-13 13:00:37 FINE: Error processing API request
java.lang.RuntimeException: java.sql.SQLException: Login timeout
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:237)
        at nxt.Account.getLessors(Account.java:1282)
        at nxt.Account.getLessorsGuaranteedBalanceNQT(Account.java:1233)
        at nxt.Account.getEffectiveBalanceNXT(Account.java:1221)
        at nxt.http.JSONData.accountBalance(JSONData.java:73)
        at nxt.http.JSONData.accountBalance(JSONData.java:55)
        at nxt.http.GetAccount.processRequest(GetAccount.java:46)
        at nxt.http.APIServlet$APIRequestHandler.processRequest(APIServlet.java:93)
        at nxt.http.APIServlet.process(APIServlet.java:491)
        at nxt.http.APIServlet.doGet(APIServlet.java:420)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
        at nxt.http.API$XFrameOptionsFilter.doFilter(API.java:374)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:406)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1182)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
        at org.eclipse.jetty.server.Server.handle(Server.java:524)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
        at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
        at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: Login timeout
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208)
        at nxt.db.BasicDb.getPooledConnection(BasicDb.java:184)
        at nxt.db.BasicDb.getConnection(BasicDb.java:178)
        at nxt.db.TransactionalDb.getConnection(TransactionalDb.java:62)
        at nxt.db.EntityDbTable.getManyBy(EntityDbTable.java:218)
        ... 36 more

It might be because my machine is not new, and quite weak, but:
Is there a way perhaps to balance the peers functions (syncing the chain) better with the local functions (answering the requests of the web frontend) ?


Title: Re: NRS v1.9.2
Post by: NxtSwe on July 16, 2016, 06:06:53 am
Anyone else having db problems after snapshotting period started?
There seem to be some db transaction locking up the db for very long period of time and then the api becomes unresponsive, and the output is filled with database-transaction errors saying they time out.

The BlockchainProcessorImpl.trimDerivedTables() seem to require quite a bit of time since the snapshot perdiod started.
I suspect it's because of my unconventional nxt.ledgerTrimKeep=-1 setting on a public node that is the main cause of this.
Perhaps in combination with other nxt.maxPrunableLifetime=-1 setting.

I accidently restarted the node and thus removed the logs, but I will post them here next time I get them.
Title: Re: NRS v1.9.2
Post by: Riker on July 16, 2016, 06:47:01 am
altsheets and NxtSwe - try to compact the database and see if this solves or reduces the frequency of the problem
Title: Re: NRS v1.9.2
Post by: Riker on July 16, 2016, 06:48:38 am
When I search for "Monetary System - Currencies - Search Currencies" and enter NSC, it says: No currencies available. But NSC is in the list at 121-135. I have tried 3 different browsers, same result. NRS version 1.9.2.

Try running the "Refresh Search Index" from the cogwheel menu
Title: Re: NRS v1.9.2
Post by: NxtSwe on July 16, 2016, 10:52:26 am
altsheets and NxtSwe - try to compact the database and see if this solves or reduces the frequency of the problem
Thanx,

It turned out to be a VPS issue where I had run out of disk space, even though I should have > 30GB remeaining.  >:(
It's been reported to the VPS provider and has nothing to do with NRS.
Title: Re: NRS v1.9.2
Post by: altsheets on July 16, 2016, 07:34:11 pm
altsheets and NxtSwe - try to compact the database and see if this solves or reduces the frequency of the problem

Thanks for the hint. Doing that now. Any ideas how long that can take?

Edit: 55 minutes  ;)
Title: Re: NRS v1.9.2
Post by: OBAViJEST on July 17, 2016, 01:25:58 am
Could someone help out this NXT newbie on how to upgrade from 1.8.3 in the safest manner?  I have no idea how to even create a proper backup yet  :-[
Title: Re: NRS v1.9.2
Post by: ScripterRon on July 17, 2016, 04:44:33 pm
altsheets and NxtSwe - try to compact the database and see if this solves or reduces the frequency of the problem

Thanks for the hint. Doing that now. Any ideas how long that can take?

Edit: 55 minutes  ;)
It is a good idea to periodically compact the database (perhaps once a month).  It normally requires 5-10 minutes for me (the time depends on the degree of fragmentation in the database).  If you are running on Windows, it also helps to defragment the disk containing the database.
Title: Re: NRS v1.9.2
Post by: wilstt on July 19, 2016, 03:13:24 pm
syncing very slow after the upgrade, it even stucked

Quote
2016-07-19 11:01:58 FINE: SQL statement required 11.788 seconds at height 874316:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$98/576618813.run(Unknown Source)
2016-07-19 11:02:39 FINE: SQL statement required 11.509 seconds at height 874316:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$98/576618813.run(Unknown Source)
2016-07-19 11:02:59 FINE: Unblacklisting 31.192.139.0
2016-07-19 11:03:05 FINE: SQL statement required 23.691 seconds at height 874316:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$98/576618813.run(Unknown Source)

add -Xmx2048m argument didn't solve the issue. tried compact.sh, no improvement. any ideas?

it runs on 4gb ubuntu 14.04 machine.
Title: Re: NRS v1.9.2
Post by: ScripterRon on July 19, 2016, 07:33:36 pm
syncing very slow after the upgrade, it even stucked

Quote
2016-07-19 11:01:58 FINE: SQL statement required 11.788 seconds at height 874316:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$98/576618813.run(Unknown Source)
2016-07-19 11:02:39 FINE: SQL statement required 11.509 seconds at height 874316:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$98/576618813.run(Unknown Source)
2016-07-19 11:02:59 FINE: Unblacklisting 31.192.139.0
2016-07-19 11:03:05 FINE: SQL statement required 23.691 seconds at height 874316:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$98/576618813.run(Unknown Source)

add -Xmx2048m argument didn't solve the issue. tried compact.sh, no improvement. any ideas?

it runs on 4gb ubuntu 14.04 machine.
What type of disk do you have?  My VPS has SSD and table trim operations typically take less than 5 seconds with an average time of 0.002 seconds.  My development machine has SATA and trim operations can take as long as 20 seconds with an average time of 0.006 seconds.
Title: Re: NRS v1.9.2
Post by: wilstt on July 20, 2016, 02:57:40 am
What type of disk do you have?  My VPS has SSD and table trim operations typically take less than 5 seconds with an average time of 0.002 seconds.  My development machine has SATA and trim operations can take as long as 20 seconds with an average time of 0.006 seconds.

it is an SSD, i see that the i/o wait is normal. so i guess it is not a disk issue?

more log:

Quote
2016-07-19 22:33:33 FINE: SQL statement required 10.053 seconds at height 875035:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$100/1330630814.run(Unknown Source)
2016-07-19 22:36:33 FINE: SQL statement required 163.115 seconds at height 875035:
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:1092)
  nxt.BlockchainProcessorImpl.trimDerivedTables(BlockchainProcessorImpl.java:1075)
  nxt.BlockchainProcessorImpl.lambda$null$2(BlockchainProcessorImpl.java:1007)
  nxt.BlockchainProcessorImpl$$Lambda$100/1330630814.run(Unknown Source)

if i restarted the java process then syncing worked normally for maybe 1000 blocks and stucked again
Title: Re: NRS v1.9.2
Post by: ScripterRon on July 20, 2016, 03:33:17 am
it is an SSD, i see that the i/o wait is normal. so i guess it is not a disk issue?

if i restarted the java process then syncing worked normally for maybe 1000 blocks and stucked again
The derived tables are trimmed every 1000 blocks.
How big is the database file in the nxt_db subdirectory?
How much memory does Java think it has?  Look for the maxMemory line at the top of nxt.log.  For example, on my development system:
Code: [Select]
2016-07-19 10:15:54 FINE: Nxt.logSystemProperties: availableProcessors = 8
2016-07-19 10:15:54 FINE: Nxt.logSystemProperties: maxMemory = 716177408
Title: Re: NRS v1.9.2
Post by: wilstt on July 20, 2016, 04:17:12 am
The derived tables are trimmed every 1000 blocks.
How big is the database file in the nxt_db subdirectory?
# du -h nxt_db
1.8M   nxt_db/nxt
3.3G   nxt_db

# ll
total 3436132
drwxr-xr-x  3 root root       4096 Jul 20 00:13 ./
drwx------ 13 root root       4096 Jul 19 11:21 ../
drwxr-xr-x  2 root root       4096 Jul 19 23:25 nxt/
-rw-r--r--  1 root root    1160560 Jul 20 00:13 nxt.1774422513.50.temp.db
-rw-r--r--  1 root root 3617607680 Jul 20 00:17 nxt.h2.db
-rw-r--r--  1 root root         99 Jul 19 23:00 nxt.lock.db
-rw-r--r--  1 root root  143655248 Jul 19 23:26 nxt.trace.db

How much memory does Java think it has?  Look for the maxMemory line at the top of nxt.log.  For example, on my development system:

2016-07-19 10:15:54 FINE: Nxt.logSystemProperties: availableProcessors = 8
2016-07-19 10:15:54 FINE: Nxt.logSystemProperties: maxMemory = 716177408


2016-07-19 23:00:08 FINE: availableProcessors = 2
2016-07-19 23:00:08 FINE: maxMemory = 2863661056
Title: Re: NRS v1.9.2
Post by: ScripterRon on July 20, 2016, 02:01:09 pm
It looks like the database needs to be compacted.  It should be between 1.0 and 1.5GB.  This is what it is on my system:
Code: [Select]
ubuntu@aws:~$ ls -lh nxt/nxt_db
total 1.4G
drwxrwxr-x 2 ubuntu ubuntu 4.0K Jul 20 10:12 nxt
-rw-rw-r-- 1 ubuntu ubuntu 1.4G Jul 20 13:52 nxt.mv.db
I'm using the H2 MVSTORE support instead of the default PAGESTORE, so your database size will be different.  But I don't think it should be 3.3GB.  Try compacting it and then see if the size has been reduced.

The heap size is plenty as long as it is all RAM and not being swapped to disk.  I run with a 784MB heap without any problems.

Take a look at nxt.trace.db.  This is a text file containing H2 error messages.  You seem to be having a lot of H2 problems (this file is typically absent or very small).

The derived tables are trimmed every 1000 blocks.
How big is the database file in the nxt_db subdirectory?
# du -h nxt_db
1.8M   nxt_db/nxt
3.3G   nxt_db

# ll
total 3436132
drwxr-xr-x  3 root root       4096 Jul 20 00:13 ./
drwx------ 13 root root       4096 Jul 19 11:21 ../
drwxr-xr-x  2 root root       4096 Jul 19 23:25 nxt/
-rw-r--r--  1 root root    1160560 Jul 20 00:13 nxt.1774422513.50.temp.db
-rw-r--r--  1 root root 3617607680 Jul 20 00:17 nxt.h2.db
-rw-r--r--  1 root root         99 Jul 19 23:00 nxt.lock.db
-rw-r--r--  1 root root  143655248 Jul 19 23:26 nxt.trace.db

How much memory does Java think it has?  Look for the maxMemory line at the top of nxt.log.  For example, on my development system:

2016-07-19 10:15:54 FINE: Nxt.logSystemProperties: availableProcessors = 8
2016-07-19 10:15:54 FINE: Nxt.logSystemProperties: maxMemory = 716177408


2016-07-19 23:00:08 FINE: availableProcessors = 2
2016-07-19 23:00:08 FINE: maxMemory = 2863661056
Title: Re: NRS v1.9.2
Post by: wilstt on July 20, 2016, 06:20:40 pm
It looks like the database needs to be compacted.
the database already compacted before i post the issue here. will try to compact again

The heap size is plenty as long as it is all RAM and not being swapped to disk.

swap is untouched, the box has 4gb of ram
Title: Re: NRS v1.9.2
Post by: ScripterRon on July 20, 2016, 06:40:41 pm
It looks like the database needs to be compacted.
the database already compacted before i post the issue here. will try to compact again

The heap size is plenty as long as it is all RAM and not being swapped to disk.

swap is untouched, the box has 4gb of ram
It doesn't look like the compact is successful.  Also, look at nxt.trace.db since you are getting a lot of H2 error messages.
Title: Re: NRS v1.9.2
Post by: wilstt on July 21, 2016, 06:56:44 am
It doesn't look like the compact is successful.  Also, look at nxt.trace.db since you are getting a lot of H2 error messages.

please check this nxt.trace.db. mean while i will re-compact my db

Quote
2016-07-14 16:07:37 jdbc[4]: exception
org.h2.jdbc.JdbcSQLException: File corrupted while reading record: "page[643388] data leaf table:91 ACCOUNT entries:58 parent:644223 keys:[2687070, 2687071, 2687072, 2687073, 2687074, 2687075, 2687076, 2687077, 2687078, 2687079, 2687080, 2687083, 2687084, 2687085, 2687087, 2687088, 2687089, 2687096, 2687097, 2687098, 2687099, 2687100, 2687101, 2687102, 2687103, 2687104, 2687105, 2687106, 2687107, 2687108, 2687109, 2687110, 2687111, 2687112, 2687113, 2687114, 2687115, 2687116, 2687117, 2687118, 2687119, 2687120, 2687121, 2687122, 2687123, 2687124, 2687125, 2687126, 2687127, 2687128, 2687129, 2687130, 2687131, 2687132, 2687133, 2687134, 2687135, 2687136] offsets:[4059, 4022, 3985, 3941, 3904, 3865, 3828, 3803, 3761, 3716, 3679, 3642, 3598, 3551, 3504, 3457, 3410, 3363, 3320, 3285, 3241, 3196, 3151, 3107, 3064, 3029, 2992, 2948, 2911, 2872, 2828, 2791, 2752, 2709, 2666, 2622, 2575, 2538, 2495, 2452, 2410, 2362, 2318, 2279, 2235, 2196, 2148, 2105, 2062, 2018, 1983, 1948, 1901, 1856, 1821, 1782, 1737, 1704]". Possible solution: use the recovery tool; SQL statement:
UPDATE public_key AS a SET a.latest = TRUE WHERE a.latest = FALSE AND a.height =  (SELECT MAX(height) FROM public_key AS b WHERE  a.account_id = b.account_id ) [90030-192]
   at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
   at org.h2.message.DbException.get(DbException.java:179)
   at org.h2.message.DbException.get(DbException.java:155)
   at org.h2.index.PageBtreeIndex.getPage(PageBtreeIndex.java:157)
   at org.h2.index.PageBtreeNode.find(PageBtreeNode.java:308)
   at org.h2.index.PageBtreeNode.find(PageBtreeNode.java:309)
   at org.h2.index.PageBtreeIndex.find(PageBtreeIndex.java:184)
   at org.h2.index.PageBtreeIndex.find(PageBtreeIndex.java:174)
   at org.h2.index.BaseIndex.find(BaseIndex.java:128)
   at org.h2.index.MultiVersionIndex.find(MultiVersionIndex.java:78)
   at org.h2.index.IndexCursor.find(IndexCursor.java:169)
   at org.h2.table.TableFilter.next(TableFilter.java:466)
   at org.h2.command.dml.Select.queryGroup(Select.java:335)
   at org.h2.command.dml.Select.queryWithoutCache(Select.java:649)
   at org.h2.command.dml.Query.query(Query.java:341)
   at org.h2.command.dml.Query.query(Query.java:309)
   at org.h2.expression.Subquery.getValue(Subquery.java:36)
   at org.h2.expression.Comparison.getValue(Comparison.java:248)
   at org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:93)
   at org.h2.expression.Expression.getBooleanValue(Expression.java:178)
   at org.h2.command.dml.Update.update(Update.java:107)
   at org.h2.command.CommandContainer.update(CommandContainer.java:98)
   at org.h2.command.Command.executeUpdate(Command.java:258)
   at org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:160)
   at org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:146)
   at nxt.db.FilteredPreparedStatement.executeUpdate(FilteredPreparedStatement.java:64)
   at nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:327)
   at nxt.db.VersionedPrunableDbTable.rollback(VersionedPrunableDbTable.java:46)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1677)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   
   ... about 1000 rows of this line
   
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   at nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1686)
   
2016-07-14 16:07:37 jdbc[4]: exception
org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[643401] data leaf table:18 BLOCK entries:10 parent:636038 keys:[871409, 871410, 871411, 871412, 871413, 871414, 871415, 871417, 871419, 871420] offsets:[3854, 3609, 3359, 3114, 2875, 2622, 2383, 2144, 1905, 1666] parent 636038 expected 644223"; SQL statement:
SELECT * FROM account WHERE id = ?  AND latest = TRUE LIMIT 1 [50000-192]
   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.command.Command.executeQuery(Command.java:213)
   at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:110)
   at nxt.db.FilteredPreparedStatement.executeQuery(FilteredPreparedStatement.java:59)
   at nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:316)
   at nxt.db.EntityDbTable.get(EntityDbTable.java:163)
   at nxt.db.EntityDbTable.get(EntityDbTable.java:101)
   at nxt.db.EntityDbTable.get(EntityDbTable.java:87)
   at nxt.Account.getAccount(Account.java:817)
   at nxt.peer.PeerImpl.getWeight(PeerImpl.java:302)
   at nxt.peer.Peers.lambda$sendToSomePeers$10(Peers.java:1006)
   at nxt.peer.Peers$$Lambda$120/922137940.run(Unknown Source)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   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)
Caused by: java.lang.RuntimeException: page[643401] data leaf table:18 BLOCK entries:10 parent:636038 keys:[871409, 871410, 871411, 871412, 871413, 871414, 871415, 871417, 871419, 871420] offsets:[3854, 3609, 3359, 3114, 2875, 2622, 2383, 2144, 1905, 1666] parent 636038 expected 644223
   at org.h2.message.DbException.throwInternalError(DbException.java:242)
   at org.h2.index.PageDataIndex.getPage(PageDataIndex.java:245)
   at org.h2.index.PageDataNode.getRowWithKey(PageDataNode.java:279)
   at org.h2.index.PageDataNode.getRowWithKey(PageDataNode.java:280)
   at org.h2.index.PageDataIndex.getRowWithKey(PageDataIndex.java:426)
   at org.h2.index.PageDataIndex.getRow(PageDataIndex.java:415)
   at org.h2.table.RegularTable.getRow(RegularTable.java:106)
   at org.h2.index.PageBtreeIndex.getRow(PageBtreeIndex.java:303)
   at org.h2.index.PageBtreeCursor.get(PageBtreeCursor.java:45)
   at org.h2.index.MultiVersionCursor.get(MultiVersionCursor.java:82)
   at org.h2.index.IndexCursor.get(IndexCursor.java:288)
   at org.h2.table.TableFilter.getValue(TableFilter.java:1068)
   at org.h2.expression.ExpressionColumn.getValue(ExpressionColumn.java:186)
   at org.h2.expression.Comparison.getValue(Comparison.java:228)
   at org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:93)
   at org.h2.expression.Expression.getBooleanValue(Expression.java:178)
   at org.h2.command.dml.Select.queryFlat(Select.java:543)
   at org.h2.command.dml.Select.queryWithoutCache(Select.java:654)
   at org.h2.command.dml.Query.query(Query.java:341)
   at org.h2.command.dml.Query.query(Query.java:309)
   at org.h2.command.dml.Query.query(Query.java:36)
   at org.h2.command.CommandContainer.query(CommandContainer.java:110)
   at org.h2.command.Command.executeQuery(Command.java:201)
   ... 15 more
2016-07-14 16:07:37 jdbc[4]: exception
org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[643412] data leaf table:119 TRANSACTION entries:12 parent:628619 keys:[2175885, 2175886, 2175887, 2175888, 2175889, 2175890, 2175891, 2175892, 2175893, 2175894, 2175895, 2175896] offsets:[3855, 3638, 3403, 3186, 2980, 2774, 2569, 2334, 2094, 1887, 1646, 1439] parent 628619 expected 644223"; SQL statement:
SELECT * FROM account WHERE id = ?  AND latest = TRUE LIMIT 1 [50000-192]
   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.command.Command.executeQuery(Command.java:213)
   at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:110)
   at nxt.db.FilteredPreparedStatement.executeQuery(FilteredPreparedStatement.java:59)
   at nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:316)
   at nxt.db.EntityDbTable.get(EntityDbTable.java:163)
   at nxt.db.EntityDbTable.get(EntityDbTable.java:101)
   at nxt.db.EntityDbTable.get(EntityDbTable.java:87)
   at nxt.Account.getAccount(Account.java:817)
   at nxt.peer.PeerImpl.getWeight(PeerImpl.java:302)
   at nxt.peer.Peers.lambda$sendToSomePeers$10(Peers.java:1006)
   at nxt.peer.Peers$$Lambda$120/922137940.run(Unknown Source)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
   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)
Caused by: java.lang.RuntimeException: page[643412] data leaf table:119 TRANSACTION entries:12 parent:628619 keys:[2175885, 2175886, 2175887, 2175888, 2175889, 2175890, 2175891, 2175892, 2175893, 2175894, 2175895, 2175896] offsets:[3855, 3638, 3403, 3186, 2980, 2774, 2569, 2334, 2094, 1887, 1646, 1439] parent 628619 expected 644223
   at org.h2.message.DbException.throwInternalError(DbException.java:242)
   at org.h2.index.PageDataIndex.getPage(PageDataIndex.java:245)
   at org.h2.index.PageDataNode.getRowWithKey(PageDataNode.java:279)
   at org.h2.index.PageDataNode.getRowWithKey(PageDataNode.java:280)
   at org.h2.index.PageDataIndex.getRowWithKey(PageDataIndex.java:426)
   at org.h2.index.PageDataIndex.getRow(PageDataIndex.java:415)
   at org.h2.table.RegularTable.getRow(RegularTable.java:106)
   at org.h2.index.PageBtreeIndex.getRow(PageBtreeIndex.java:303)
   at org.h2.index.PageBtreeCursor.get(PageBtreeCursor.java:45)
   at org.h2.index.MultiVersionCursor.get(MultiVersionCursor.java:82)
   at org.h2.index.IndexCursor.get(IndexCursor.java:288)
   at org.h2.table.TableFilter.getValue(TableFilter.java:1068)
   at org.h2.expression.ExpressionColumn.getValue(ExpressionColumn.java:186)
   at org.h2.expression.Comparison.getValue(Comparison.java:228)
   at org.h2.expression.ConditionAndOr.getValue(ConditionAndOr.java:93)
   at org.h2.expression.Expression.getBooleanValue(Expression.java:178)
   at org.h2.command.dml.Select.queryFlat(Select.java:543)
   at org.h2.command.dml.Select.queryWithoutCache(Select.java:654)
   at org.h2.command.dml.Query.query(Query.java:341)
   at org.h2.command.dml.Query.query(Query.java:309)
   at org.h2.command.dml.Query.query(Query.java:36)
   at org.h2.command.CommandContainer.query(CommandContainer.java:110)
   at org.h2.command.Command.executeQuery(Command.java:201)
   ... 15 more
2016-07-19 03:10:38 pageStore: Transaction log could not be truncated; size: 21 MB
2016-07-19 05:54:08 pageStore: Transaction log could not be truncated; size: 61 MB
2016-07-19 07:58:45 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: Out of memory.; SQL statement:
RUNSCRIPT FROM './nxt_db/backup.sql.gz' COMPRESSION GZIP CHARSET 'UTF-8' [90108-192]
   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:289)
   at org.h2.command.Command.executeUpdate(Command.java:264)
   at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:184)
   at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:158)
   at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:174)
   at nxt.tools.CompactDatabase.main(CompactDatabase.java:56)
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.h2.value.ValueLong.get(ValueLong.java:213)
   at org.h2.store.Data.readValue(Data.java:742)
   at org.h2.index.PageDataLeaf.readRow(PageDataLeaf.java:624)
   at org.h2.index.PageDataLeaf.getRowAt(PageDataLeaf.java:334)
   at org.h2.index.PageDataCursor.nextRow(PageDataCursor.java:101)
   at org.h2.index.PageDataCursor.next(PageDataCursor.java:67)
   at org.h2.table.RegularTable.addIndex(RegularTable.java:271)
   at org.h2.command.ddl.CreateIndex.update(CreateIndex.java:105)
   at org.h2.command.dml.RunScriptCommand.execute(RunScriptCommand.java:78)
   at org.h2.command.dml.RunScriptCommand.update(RunScriptCommand.java:57)
   at org.h2.command.CommandContainer.update(CommandContainer.java:98)
   at org.h2.command.Command.executeUpdate(Command.java:258)
   ... 4 more
2016-07-19 07:58:45 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: The database has been closed [90098-192]
   at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
   at org.h2.message.DbException.get(DbException.java:179)
   at org.h2.message.DbException.get(DbException.java:155)
   at org.h2.message.DbException.get(DbException.java:144)
   at org.h2.engine.Database.checkPowerOff(Database.java:519)
   at org.h2.engine.Session.close(Session.java:817)
   at org.h2.jdbc.JdbcConnection.close(JdbcConnection.java:397)
   at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:176)
   at nxt.tools.CompactDatabase.main(CompactDatabase.java:56)
2016-07-19 09:09:02 pageStore: Transaction log could not be truncated; size: 23 MB
2016-07-19 09:29:03 pageStore: Transaction log could not be truncated; size: 20 MB
2016-07-19 11:35:13 pageStore: Transaction log could not be truncated; size: 52 MB
2016-07-19 23:26:38 pageStore: Transaction log could not be truncated; size: 27 MB
2016-07-20 00:32:46 pageStore: Transaction log could not be truncated; size: 25 MB
2016-07-20 09:16:07 pageStore: Transaction log could not be truncated; size: 39 MB
2016-07-20 12:35:35 pageStore: Transaction log could not be truncated; size: 23 MB
Title: Re: NRS v1.9.2
Post by: farl4bit on July 21, 2016, 08:10:31 am
My Nxt Wallet (mac) often crashes after it's been forging for days/weeks.

Would be great if we have more stable and modern client software in Ardor. Take for example IOTA, it's an easy installation and very userfriendly. Nxt looks old compare to that. With all respect of course.  :)
Title: Re: NRS v1.9.2
Post by: lurker10 on July 21, 2016, 08:21:20 am
My Nxt Wallet (mac) often crashes after it's been forging for days/weeks.

Would be great if we have more stable and modern client software in Ardor. Take for example IOTA, it's an easy installation and very userfriendly. Nxt looks old compare to that. With all respect of course.  :)

This has got to be a MAC thing. I have NXT running and forging on my linux box for 6 months with no restarts or crashes.

IOTA isn't exactly stable, in fact far from it. The GUI may look nice, but on the inside, the core has got annoying bugs, it requires quite a bit of polishing before considered stable.
Title: Re: NRS v1.9.2
Post by: Riker on July 21, 2016, 08:24:37 am
My Nxt Wallet (mac) often crashes after it's been forging for days/weeks.

Would be great if we have more stable and modern client software in Ardor. Take for example IOTA, it's an easy installation and very userfriendly. Nxt looks old compare to that. With all respect of course.  :)

My Mac works for weeks without interruption.
What exactly "crashes" on your Mac ? Is it the Java process itself ? The desktop wallet ? The browser window ?
Do you see any error messages in the nxt.log ?

Regarding the "un-friendliness" issue, if you like to seriously discuss this we need to open a separate thread and identify the exact pain points.
Surely you don't like us to rewrite the client wallet from scratch after investing around 10 man years in its development.
Title: Re: NRS v1.9.2
Post by: farl4bit on July 21, 2016, 08:38:37 am
My Nxt Wallet (mac) often crashes after it's been forging for days/weeks.

Would be great if we have more stable and modern client software in Ardor. Take for example IOTA, it's an easy installation and very userfriendly. Nxt looks old compare to that. With all respect of course.  :)

This has got to be a MAC thing. I have NXT running and forging on my linux box for 6 months with no restarts or crashes.

IOTA isn't exactly stable, in fact far from it. The GUI may look nice, but on the inside, the core has got annoying bugs, it requires quite a bit of polishing before considered stable.

I am talking more about the installation progress of the Nxt Desktop Wallet. It looks old, doesn't work well on computer accounts which are not the Administrator. The installation is not how software works on a Mac. Normally you download a DMG, unpack it, and place the app in your application folder. That's it.


My Mac works for weeks without interruption.
What exactly "crashes" on your Mac ? Is it the Java process itself ? The desktop wallet ? The browser window ?
Do you see any error messages in the nxt.log ?

Regarding the "un-friendliness" issue, if you like to seriously discuss this we need to open a separate thread and identify the exact pain points.
Surely you don't like us to rewrite the client wallet from scratch after investing around 10 man years in its development.

Sorry, I didn't safe the error message. The desktop app crashes every two weeks or so. And it gets stuck every week (but then the browser version is still available and working).  I addressed these issues before.
Title: Re: NRS v1.9.2
Post by: Riker on July 21, 2016, 08:54:27 am
We discussed before the design of the mac installer, not much we can do about this, let's move on.
As far as I can tell, there is no problem to install without admin rights. Just install to the user folder instead of to the /Applications folder.

Regarding the desktop wallet getting stuck, I think I've seen it happen as well. This does not "crash" anything since your node continues to forge.
Just close the wallet and re-open it.
I'm adding to my to do list to figure out this problem, I speculate that it's something specific for JavaFx webview on Mac. Perhaps Java 9 will fix it.
Title: Re: NRS v1.9.2
Post by: wilstt on July 21, 2016, 08:58:50 am
well, i just removed the old data and unzip brand new nxt client, just found that we can import the whole blocks from peerexplorer.com

the wallet is now online and synced, it only takes 10 minutes of work.

thanks @ScripterRon
Title: Re: NRS v1.9.2
Post by: farl4bit on July 21, 2016, 09:18:58 am
We discussed before the design of the mac installer, not much we can do about this, let's move on.
As far as I can tell, there is no problem to install without admin rights. Just install to the user folder instead of to the /Applications folder.

Regarding the desktop wallet getting stuck, I think I've seen it happen as well. This does not "crash" anything since your node continues to forge.
Just close the wallet and re-open it.
I'm adding to my to do list to figure out this problem, I speculate that it's something specific for JavaFx webview on Mac. Perhaps Java 9 will fix it.

My goal is to make it as userfriendly as possible to new Nxt users. I had lot of trouble with chosing the right folder for the installation. I see a lot of errors that it's not possible to create the folder. It only works in administrator account.

Client stuck and crashes will be great if they get fixed. :)
Title: Re: NRS v1.9.2
Post by: ScripterRon on July 21, 2016, 02:52:59 pm
It doesn't look like the compact is successful.  Also, look at nxt.trace.db since you are getting a lot of H2 error messages.

please check this nxt.trace.db. mean while i will re-compact my db

Your database is corrupted.  You need to delete the nxt_db directory and then download the blockchain again.
Title: Re: NRS v1.9.2
Post by: nxtcoinspeaker on July 27, 2016, 05:38:38 pm
hello,

i have problem my nxt wallet doesn't can't download the blockchain, i exe run.bat because .exe isn't compatible with my systeme, now i wait blockchain downloading but it dont...so someone can help me pls ?
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 27, 2016, 06:12:45 pm
hello,

i have problem my nxt wallet doesn't can't download the blockchain, i exe run.bat because .exe isn't compatible with my systeme, now i wait blockchain downloading but it dont...so someone can help me pls ?

Please try bootstrapping your blockchain database with the latest snapshot from peerexplorer.com.
Title: Re: NRS v1.9.2
Post by: spring on July 28, 2016, 10:34:03 am
is nxt open source?
Title: Re: NRS v1.9.2
Post by: lurker10 on July 28, 2016, 10:40:51 am
is nxt open source?

https://bitbucket.org/JeanLucPicard/nxt/src
Title: Re: NRS v1.9.2
Post by: spring on July 28, 2016, 11:11:56 am
is nxt open source?

/bitbucket.org/JeanLucPicard/nxt/src

Fantastic! ::) ::) ::)
Title: Re: NRS v1.9.2
Post by: nxtcoinspeaker on July 31, 2016, 12:45:30 am
hello,

i have problem my nxt wallet doesn't can't download the blockchain, i exe run.bat because .exe isn't compatible with my systeme, now i wait blockchain downloading but it dont...so someone can help me pls ?

Please try bootstrapping your blockchain database with the latest snapshot from peerexplorer.com.

how i do  ?
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 31, 2016, 07:17:44 am
hello,

i have problem my nxt wallet doesn't can't download the blockchain, i exe run.bat because .exe isn't compatible with my systeme, now i wait blockchain downloading but it dont...so someone can help me pls ?

Please try bootstrapping your blockchain database with the latest snapshot from peerexplorer.com.

how i do  ?

Use this link: http://www.peerexplorer.com (http://www.peerexplorer.com)
You find the download link at the bottom of the page, a popup will appear with instructions.
Before copying the downloaded zip content into your nxt folder you should completely delete the nxt_db folder.
Title: Re: NRS v1.9.2
Post by: nxtcoinspeaker on July 31, 2016, 05:37:25 pm
hello,

i have problem my nxt wallet doesn't can't download the blockchain, i exe run.bat because .exe isn't compatible with my systeme, now i wait blockchain downloading but it dont...so someone can help me pls ?

Please try bootstrapping your blockchain database with the latest snapshot from peerexplorer.com.

how i do  ?

Use this link: http://www.peerexplorer.com (http://www.peerexplorer.com)
You find the download link at the bottom of the page, a popup will appear with instructions.
Before copying the downloaded zip content into your nxt folder you should completely delete the nxt_db folder.

its ok working, yu have really help me, send me yu nxt add in pm i will sent something when i can  ;D
Title: Re: NRS v1.9.2
Post by: CryptKeeper on July 31, 2016, 05:47:15 pm
hello,

i have problem my nxt wallet doesn't can't download the blockchain, i exe run.bat because .exe isn't compatible with my systeme, now i wait blockchain downloading but it dont...so someone can help me pls ?

Please try bootstrapping your blockchain database with the latest snapshot from peerexplorer.com.

how i do  ?

Use this link: http://www.peerexplorer.com (http://www.peerexplorer.com)
You find the download link at the bottom of the page, a popup will appear with instructions.
Before copying the downloaded zip content into your nxt folder you should completely delete the nxt_db folder.

its ok working, yu have really help me, send me yu nxt add in pm i will sent something when i can  ;D

My address is public: NXT-CRPT-KEEP-R3DV-AXCDR
Tips are rare but very welcome!  ;)

I'm glad I could help you! One more happy nxter!
 :D  :D  :D
Title: Re: NRS v1.9.2
Post by: Bik_z19 on August 11, 2016, 06:28:36 pm
Could it be that the client doesnt run on 32-bits Vista? I've started an old pc to create a steady node but it says:
The version of this file is not compatible with the Windows-version currently being run. Please check the systeminformation of you PC to check whether you need a 32-bits(x86) or 64-bit version of the application. Then contact the publisher of the software.

(Translated from Dutch, poorly I'm afraid  ;D)

It would appear that the client can run on Vista, but I have had this problem before where it was just due to an outdated JAVA version. So of course, I updated JAVA. Any other things that may trigger this error?
Title: Re: NRS v1.9.2
Post by: altsheets on September 22, 2016, 09:07:53 pm
with   compact.bat   I got these errors:

Code: [Select]
2016-09-22 22:33:58 INFO: nxt.enableStackTraces = "true"
2016-09-22 22:33:59 INFO: nxt.enableLogTraceback = "false"
2016-09-22 22:33:59 INFO: logging enabled
2016-09-22 22:33:59 INFO: nxt.isTestnet = "false"
2016-09-22 22:33:59 INFO: nxt.isOffline = "false"
2016-09-22 22:33:59 INFO: nxt.maxRollback = "800"
2016-09-22 22:33:59 INFO: nxt.forgingDelay = "20"
2016-09-22 22:33:59 INFO: nxt.forgingSpeedup = "3"
2016-09-22 22:33:59 INFO: nxt.maxPrunableLifetime = "7776000"
2016-09-22 22:33:59 INFO: nxt.includeExpiredPrunable = "true"
2016-09-22 22:33:59 INFO: nxt.correctInvalidFees = "false"
2016-09-22 22:33:59 INFO: nxt.dbType = "h2"
2016-09-22 22:33:59 INFO: nxt.dbUrl not defined
2016-09-22 22:33:59 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-09-22 22:33:59 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-09-22 22:33:59 INFO: nxt.dbUsername = "sa"
2016-09-22 22:33:59 INFO: nxt.dbPassword = "{not logged}"
2016-09-22 22:33:59 INFO: Database directory is 'C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db"
2016-09-22 22:33:59 INFO: Creating the SQL script
2016-09-22 22:51:39 INFO: Creating the new database
2016-09-22 22:53:35 SEVERE: Unable to compact the database
org.h2.jdbc.JdbcSQLException: Out of memory.; SQL statement:
RUNSCRIPT FROM 'C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db\backup.sql.gz' COMPRESSION GZIP CHARSET 'UTF-8' [90108-192]
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:289)
at org.h2.command.Command.executeUpdate(Command.java:264)
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:184)
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:158)
at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:174)
at nxt.tools.CompactDatabase.main(CompactDatabase.java:56)
Suppressed: org.h2.jdbc.JdbcSQLException: The database has been closed [90098-192]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.engine.Database.checkPowerOff(Database.java:519)
at org.h2.engine.Session.close(Session.java:817)
at org.h2.jdbc.JdbcConnection.close(JdbcConnection.java:397)
at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:176)
... 1 more
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.h2.value.ValueLong.get(ValueLong.java:213)
at org.h2.store.Data.readValue(Data.java:742)
at org.h2.index.PageDataLeaf.readRow(PageDataLeaf.java:624)
at org.h2.index.PageDataLeaf.getRowAt(PageDataLeaf.java:334)
at org.h2.index.PageDataCursor.nextRow(PageDataCursor.java:101)
at org.h2.index.PageDataCursor.next(PageDataCursor.java:67)
at org.h2.table.RegularTable.addIndex(RegularTable.java:271)
at org.h2.command.ddl.CreateIndex.update(CreateIndex.java:105)
at org.h2.command.dml.RunScriptCommand.execute(RunScriptCommand.java:78)
at org.h2.command.dml.RunScriptCommand.update(RunScriptCommand.java:57)
at org.h2.command.CommandContainer.update(CommandContainer.java:98)
at org.h2.command.Command.executeUpdate(Command.java:258)
... 4 more
Title: Re: NRS v1.9.2
Post by: Riker on September 23, 2016, 07:55:15 am
with   compact.bat   I got these errors:

Code: [Select]
2016-09-22 22:33:58 INFO: nxt.enableStackTraces = "true"
2016-09-22 22:33:59 INFO: nxt.enableLogTraceback = "false"
2016-09-22 22:33:59 INFO: logging enabled
2016-09-22 22:33:59 INFO: nxt.isTestnet = "false"
2016-09-22 22:33:59 INFO: nxt.isOffline = "false"
2016-09-22 22:33:59 INFO: nxt.maxRollback = "800"
2016-09-22 22:33:59 INFO: nxt.forgingDelay = "20"
2016-09-22 22:33:59 INFO: nxt.forgingSpeedup = "3"
2016-09-22 22:33:59 INFO: nxt.maxPrunableLifetime = "7776000"
2016-09-22 22:33:59 INFO: nxt.includeExpiredPrunable = "true"
2016-09-22 22:33:59 INFO: nxt.correctInvalidFees = "false"
2016-09-22 22:33:59 INFO: nxt.dbType = "h2"
2016-09-22 22:33:59 INFO: nxt.dbUrl not defined
2016-09-22 22:33:59 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-09-22 22:33:59 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-09-22 22:33:59 INFO: nxt.dbUsername = "sa"
2016-09-22 22:33:59 INFO: nxt.dbPassword = "{not logged}"
2016-09-22 22:33:59 INFO: Database directory is 'C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db"
2016-09-22 22:33:59 INFO: Creating the SQL script
2016-09-22 22:51:39 INFO: Creating the new database
2016-09-22 22:53:35 SEVERE: Unable to compact the database
org.h2.jdbc.JdbcSQLException: Out of memory.; SQL statement:
RUNSCRIPT FROM 'C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db\backup.sql.gz' COMPRESSION GZIP CHARSET 'UTF-8' [90108-192]
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:289)
at org.h2.command.Command.executeUpdate(Command.java:264)
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:184)
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:158)
at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:174)
at nxt.tools.CompactDatabase.main(CompactDatabase.java:56)
Suppressed: org.h2.jdbc.JdbcSQLException: The database has been closed [90098-192]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.engine.Database.checkPowerOff(Database.java:519)
at org.h2.engine.Session.close(Session.java:817)
at org.h2.jdbc.JdbcConnection.close(JdbcConnection.java:397)
at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:176)
... 1 more
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.h2.value.ValueLong.get(ValueLong.java:213)
at org.h2.store.Data.readValue(Data.java:742)
at org.h2.index.PageDataLeaf.readRow(PageDataLeaf.java:624)
at org.h2.index.PageDataLeaf.getRowAt(PageDataLeaf.java:334)
at org.h2.index.PageDataCursor.nextRow(PageDataCursor.java:101)
at org.h2.index.PageDataCursor.next(PageDataCursor.java:67)
at org.h2.table.RegularTable.addIndex(RegularTable.java:271)
at org.h2.command.ddl.CreateIndex.update(CreateIndex.java:105)
at org.h2.command.dml.RunScriptCommand.execute(RunScriptCommand.java:78)
at org.h2.command.dml.RunScriptCommand.update(RunScriptCommand.java:57)
at org.h2.command.CommandContainer.update(CommandContainer.java:98)
at org.h2.command.Command.executeUpdate(Command.java:258)
... 4 more
Make sure you have enough available memory and increase memory allocation in compact.bat to 1.5 GB by changing the existing -Xmx1024m flag to -Xmx1500m
Title: Re: NRS v1.9.2
Post by: Riker on September 23, 2016, 07:57:37 am
Could it be that the client doesnt run on 32-bits Vista? I've started an old pc to create a steady node but it says:
The version of this file is not compatible with the Windows-version currently being run. Please check the systeminformation of you PC to check whether you need a 32-bits(x86) or 64-bit version of the application. Then contact the publisher of the software.

(Translated from Dutch, poorly I'm afraid  ;D)

It would appear that the client can run on Vista, but I have had this problem before where it was just due to an outdated JAVA version. So of course, I updated JAVA. Any other things that may trigger this error?

The Java version distributed with the Windows installer is 64 bit and therefore won't run on a 32 bit operating system.
You'll need to install Java 32 bit separately (http://www.oracle.com/technetwork/java/javase/downloads/index-jsp-138363.html) download the x86 JRE then point run.bat to use it instead of the pre-installed 64 bit version.
Title: Re: NRS v1.9.2
Post by: altsheets on October 07, 2016, 01:54:05 am
with   compact.bat   I got these errors:

Code: [Select]
2016-09-22 22:33:58 INFO: nxt.enableStackTraces = "true"
2016-09-22 22:33:59 INFO: nxt.enableLogTraceback = "false"
2016-09-22 22:33:59 INFO: logging enabled
2016-09-22 22:33:59 INFO: nxt.isTestnet = "false"
2016-09-22 22:33:59 INFO: nxt.isOffline = "false"
2016-09-22 22:33:59 INFO: nxt.maxRollback = "800"
2016-09-22 22:33:59 INFO: nxt.forgingDelay = "20"
2016-09-22 22:33:59 INFO: nxt.forgingSpeedup = "3"
2016-09-22 22:33:59 INFO: nxt.maxPrunableLifetime = "7776000"
2016-09-22 22:33:59 INFO: nxt.includeExpiredPrunable = "true"
2016-09-22 22:33:59 INFO: nxt.correctInvalidFees = "false"
2016-09-22 22:33:59 INFO: nxt.dbType = "h2"
2016-09-22 22:33:59 INFO: nxt.dbUrl not defined
2016-09-22 22:33:59 INFO: nxt.dbDir = "./nxt_db/nxt"
2016-09-22 22:33:59 INFO: nxt.dbParams = "DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;MV_STORE=FALSE"
2016-09-22 22:33:59 INFO: nxt.dbUsername = "sa"
2016-09-22 22:33:59 INFO: nxt.dbPassword = "{not logged}"
2016-09-22 22:33:59 INFO: Database directory is 'C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db"
2016-09-22 22:33:59 INFO: Creating the SQL script
2016-09-22 22:51:39 INFO: Creating the new database
2016-09-22 22:53:35 SEVERE: Unable to compact the database
org.h2.jdbc.JdbcSQLException: Out of memory.; SQL statement:
RUNSCRIPT FROM 'C:\Users\USERNAME\AppData\Roaming\NXT\.\nxt_db\backup.sql.gz' COMPRESSION GZIP CHARSET 'UTF-8' [90108-192]
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:289)
at org.h2.command.Command.executeUpdate(Command.java:264)
at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:184)
at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:158)
at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:174)
at nxt.tools.CompactDatabase.main(CompactDatabase.java:56)
Suppressed: org.h2.jdbc.JdbcSQLException: The database has been closed [90098-192]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.engine.Database.checkPowerOff(Database.java:519)
at org.h2.engine.Session.close(Session.java:817)
at org.h2.jdbc.JdbcConnection.close(JdbcConnection.java:397)
at nxt.tools.CompactDatabase.compactDatabase(CompactDatabase.java:176)
... 1 more
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.h2.value.ValueLong.get(ValueLong.java:213)
at org.h2.store.Data.readValue(Data.java:742)
at org.h2.index.PageDataLeaf.readRow(PageDataLeaf.java:624)
at org.h2.index.PageDataLeaf.getRowAt(PageDataLeaf.java:334)
at org.h2.index.PageDataCursor.nextRow(PageDataCursor.java:101)
at org.h2.index.PageDataCursor.next(PageDataCursor.java:67)
at org.h2.table.RegularTable.addIndex(RegularTable.java:271)
at org.h2.command.ddl.CreateIndex.update(CreateIndex.java:105)
at org.h2.command.dml.RunScriptCommand.execute(RunScriptCommand.java:78)
at org.h2.command.dml.RunScriptCommand.update(RunScriptCommand.java:57)
at org.h2.command.CommandContainer.update(CommandContainer.java:98)
at org.h2.command.Command.executeUpdate(Command.java:258)
... 4 more
Make sure you have enough available memory and increase memory allocation in compact.bat to 1.5 GB by changing the existing -Xmx1024m flag to -Xmx1500m

Yes, that must have been it. I've now seen peak mem values of 1,173,000 K.

Code: [Select]
INFO: Database successfully compacted
Thank you very much!



elective-stereophonic
elective-stereophonic
assembly
assembly