Topic: NRS v1.9.2 (Read 22110 times)

Jean-Luc · 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-----

qq2536007339 · July 02, 2016, 09:21:07 am

Thank you,JL,can't wait to try!

Nextshares · July 02, 2016, 10:30:01 am

Looks everything works perfectly in my side, thanks core dev team hard work

yassin54 · July 02, 2016, 12:22:41 pm

Thanks

Tweeted!! https://twitter.com/NxtCommunity/status/749216358211031040

rubenaco · July 02, 2016, 12:54:39 pm

Thanks @coreteam!

Enviado desde mi Redmi Note 3 mediante Tapatalk

box1413 · 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.

Quote from: gh on July 02, 2016, 10:10:12 am

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.

Riker · 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.

chevdor · July 02, 2016, 03:24:43 pm

Quote from: 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.

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

CryptKeeper · 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?

chevdor · 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.

Riker · July 02, 2016, 07:54:45 pm

Quote from: 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?

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

NXT ENTERPRISE · 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?

qq2536007339 · 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.

OutSL · July 04, 2016, 07:28:12 am

Hello World

Thank you for your ardor in the task and your sublime work

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

CryptKeeper · 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?

CryptKeeper · July 04, 2016, 09:25:40 am

Quote from: Riker on July 02, 2016, 07:54:45 pm

Quote from: 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?

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

Done.

lurker10 · July 04, 2016, 09:34:30 am

Quote from: 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:

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.

CryptKeeper · July 04, 2016, 09:36:57 am

Quote from: lurker10 on July 04, 2016, 09:34:30 am

Quote from: 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:

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.

lurker10 · July 04, 2016, 09:40:42 am

Quote from: CryptKeeper on July 04, 2016, 09:36:57 am

Quote from: lurker10 on July 04, 2016, 09:34:30 am
Quote from: 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:

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?

CryptKeeper · July 04, 2016, 09:44:38 am

Quote from: lurker10 on July 04, 2016, 09:40:42 am

Quote from: CryptKeeper on July 04, 2016, 09:36:57 am
Quote from: lurker10 on July 04, 2016, 09:34:30 am
Quote from: 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:

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"

News:

Author Topic: NRS v1.9.2 (Read 22110 times)