Nxt Forum

Nxt Discussion => Nxt Software Releases => Official Nxt Releases => Topic started by: Jean-Luc on April 01, 2017, 09:01:23 am

Title: NRS v1.11.5
Post by: Jean-Luc on April 01, 2017, 09:01:23 am
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.11.5

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

sha256:

facb359f2a4fae62b5e2cbb2f5a41bd8cface8090ba72d3ddcba22a904fb23d3  nxt-client-1.11.5.zip

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

sha256:

863fadaedf11ca9f0317b724c0e68e549703482c30fdb07e90f16d0f1f7195bd  nxt-client-1.11.5.sh

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

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

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


Change log:

Added firstIndex, lastIndex parameters to the getUnconfirmedTransactions and
getUnconfirmedTransactionIds APIs to support pagination.

Minor performance optimizations and UI improvements.

Updated H2 to version 1.4.194 and jetty to 9.3.17.


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

iQIcBAEBCgAGBQJY31HdAAoJENqvaxkWiP4Z9A8QAOjDspfpmg1OfrErqIln2OHc
w0DUQIeGJPr/PHOuzQszqguMtw1as91OKLLg5eayGtoNPwoQiRUlOMtC1hyeSPP9
cklMPlhi8JPiaVK4uGzNGE0427cGLvXyvoFbjS0O66M08VuOBtLcdIkFM4zf/y6i
g5AqmXPO0Sf49aHG3vEBydAypfLj990zllU/svm8fW5iSCTkZdFV19ArJ5YzjHB0
Ocu6qWPvKvfNLLwD6xC6M1aogi0bgW9v0sahDROHFdSfoNdTT+j/8xCn3x3ARYej
QRZ0411AlZXbta4EC8NPTXYt/GHg47HOr+4bjg7uqjR5xJJTw2p4Tw8emKNp4ehh
ILDDVH+mnxqq05EfCdIjMuVUfbmd/Ye1FSCHUz2WKR7TG3py65zZvawxUUAezU9+
Juhz87WKBR4z8w5Bzf05yEiEgtHy0hL2TQdLoicxw4sBhWXCweEWqbaGT+ipcAY7
HdpueCn9fIDyQCBtwcpVMTYMbmtUvUnHg4zZ4m9TdDQL6me2T/9kr4Cpfng32Exc
0jRLL+xtUNqelX0v2zgCqVOsQpv6wjbs9FEK9xxQ8B7hA5BqRE3IB6culMkQ5k24
KOILr1MYD11wdwT5kpcMKmRZXr6tViXhGEk975Az9+5MLbj/qN0ly4QzDChKkR4/
V0iPVv+D6InToEXqFXJI
=S2L3
-----END PGP SIGNATURE-----
Title: Re: NRS v1.11.5
Post by: Bik_z19 on April 01, 2017, 11:08:54 pm
Thank you! Updating the nodes :)
Title: Re: NRS v1.11.5
Post by: Riker on April 02, 2017, 09:48:28 am
Android app is now available at https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-mobile-client-android-1.11.5.0.apk
Hash 94f71ed4d3762dd2e28f28bf0f8760a5a2c3cb78ee22a257639cc39dbe0c2621

The new version has been updated to:
Node v7.8.0
NPM 4.4.4
Cordova 6.5.0
Android Platform 6.1.2
All Cordova plugins were updated to their latest version
Title: Re: NRS v1.11.5
Post by: silverblade07 on April 03, 2017, 12:15:11 pm
Thank you for the update, Will be updating node soon.
Title: Re: NRS v1.11.5
Post by: Megalodon on April 07, 2017, 07:23:16 pm

SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
Got this error while downloading blockchain after upgrading to this version.

Code: [Select]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.h2.jdbc.JdbcSQLException: Error opening database: "Concurrent update" [8000-194]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
        at org.h2.message.DbException.get(DbException.java:168)
        at org.h2.store.FileLock.getExceptionFatal(FileLock.java:455)
        at org.h2.store.FileLock.lockFile(FileLock.java:363)
        at org.h2.store.FileLock.lock(FileLock.java:135)
        at org.h2.engine.Database.open(Database.java:662)
        at org.h2.engine.Database.openDatabase(Database.java:276)
        at org.h2.engine.Database.<init>(Database.java:270)
        at org.h2.engine.Engine.openSession(Engine.java:64)
        at org.h2.engine.Engine.openSession(Engine.java:176)
        at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
        at org.h2.engine.Engine.createSession(Engine.java:137)
        at org.h2.engine.Engine.createSession(Engine.java:27)
        at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)
        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
        at org.h2.Driver.connect(Driver.java:69)
        at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:188)
        at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:351)
        at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:383)
        at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:226)
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:198)
        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.get(EntityDbTable.java:103)
        ... 16 more
2017-04-07 12:03:52 FINE: Database transaction required 42.973 seconds at height 455636
  nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1702)
  nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:636)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:624)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:330)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:232)
2017-04-07 12:03:52 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
2017-04-07 12:03:52 INFO: Shutting down...
Title: Re: NRS v1.11.5
Post by: Riker on April 08, 2017, 05:22:52 am

SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
Got this error while downloading blockchain after upgrading to this version.

Code: [Select]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.h2.jdbc.JdbcSQLException: Error opening database: "Concurrent update" [8000-194]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
        at org.h2.message.DbException.get(DbException.java:168)
        at org.h2.store.FileLock.getExceptionFatal(FileLock.java:455)
        at org.h2.store.FileLock.lockFile(FileLock.java:363)
        at org.h2.store.FileLock.lock(FileLock.java:135)
        at org.h2.engine.Database.open(Database.java:662)
        at org.h2.engine.Database.openDatabase(Database.java:276)
        at org.h2.engine.Database.<init>(Database.java:270)
        at org.h2.engine.Engine.openSession(Engine.java:64)
        at org.h2.engine.Engine.openSession(Engine.java:176)
        at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
        at org.h2.engine.Engine.createSession(Engine.java:137)
        at org.h2.engine.Engine.createSession(Engine.java:27)
        at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)
        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
        at org.h2.Driver.connect(Driver.java:69)
        at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:188)
        at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:351)
        at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:383)
        at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:226)
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:198)
        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.get(EntityDbTable.java:103)
        ... 16 more
2017-04-07 12:03:52 FINE: Database transaction required 42.973 seconds at height 455636
  nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1702)
  nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:636)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:624)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:330)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:232)
2017-04-07 12:03:52 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
2017-04-07 12:03:52 INFO: Shutting down...

You are probably running out of memory "java.lang.OutOfMemoryError: GC overhead limit exceeded" and this is causing a database related error.
Would be nice if you can post the workstation specications.
Please try to increase your memory settings by adding the following command line flag to run.sh: -mx800m

If this doesn't help you may need to download the blockchain on a stronger machine then copy it to this workstation.
Title: Re: NRS v1.11.5
Post by: Megalodon on April 08, 2017, 09:28:27 am


SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
Got this error while downloading blockchain after upgrading to this version.

Code: [Select]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.h2.jdbc.JdbcSQLException: Error opening database: "Concurrent update" [8000-194]
        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
        at org.h2.message.DbException.get(DbException.java:168)
        at org.h2.store.FileLock.getExceptionFatal(FileLock.java:455)
        at org.h2.store.FileLock.lockFile(FileLock.java:363)
        at org.h2.store.FileLock.lock(FileLock.java:135)
        at org.h2.engine.Database.open(Database.java:662)
        at org.h2.engine.Database.openDatabase(Database.java:276)
        at org.h2.engine.Database.<init>(Database.java:270)
        at org.h2.engine.Engine.openSession(Engine.java:64)
        at org.h2.engine.Engine.openSession(Engine.java:176)
        at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
        at org.h2.engine.Engine.createSession(Engine.java:137)
        at org.h2.engine.Engine.createSession(Engine.java:27)
        at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)
        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
        at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
        at org.h2.Driver.connect(Driver.java:69)
        at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:188)
        at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:351)
        at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:383)
        at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:226)
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:198)
        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.get(EntityDbTable.java:103)
        ... 16 more
2017-04-07 12:03:52 FINE: Database transaction required 42.973 seconds at height 455636
  nxt.BlockchainProcessorImpl.popOffTo(BlockchainProcessorImpl.java:1702)
  nxt.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:636)
  nxt.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:624)
  nxt.BlockchainProcessorImpl$1.downloadPeer(BlockchainProcessorImpl.java:330)
  nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:232)
2017-04-07 12:03:52 SEVERE: CRITICAL ERROR. PLEASE REPORT TO THE DEVELOPERS.
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
2017-04-07 12:03:52 INFO: Shutting down...


You are probably running out of memory "java.lang.OutOfMemoryError: GC overhead limit exceeded" and this is causing a database related error.
Would be nice if you can post the workstation specications.
Please try to increase your memory settings by adding the following command line flag to run.sh: -mx800m

If this doesn't help you may need to download the blockchain on a stronger machine then copy it to this workstation.

Have been running nrs on this VPS (Ubuntu 14.04 64-BIT, 2G memory) for years without similar problem.
Tried running with -mx800m flag, same problem.
Resolved with fresh blockchain from another machine.
Hope this helps.
Title: Re: NRS v1.11.5
Post by: Riker on April 08, 2017, 04:43:23 pm
Have been running nrs on this VPS (Ubuntu 14.04 64-BIT, 2G memory) for years without similar problem.
Tried running with -mx800m flag, same problem.
Resolved with fresh blockchain from another machine.
Hope this helps.

I thought you were using a 1GB VPS. 2GB should be more than enough.

If you still have the nxt.log from the 2nd attempt:
Did you get the same "Error opening database: "Concurrent update" [8000-194]" exception in nxt.log after setting -mx800m ?
Did you also get the "java.lang.OutOfMemoryError: GC overhead limit exceeded" message?
Can you still tell how far did the blockchain download go before your node was stopped?
Title: Re: NRS v1.11.5
Post by: Megalodon on April 08, 2017, 09:39:45 pm

Have been running nrs on this VPS (Ubuntu 14.04 64-BIT, 2G memory) for years without similar problem.
Tried running with -mx800m flag, same problem.
Resolved with fresh blockchain from another machine.
Hope this helps.


I thought you were using a 1GB VPS. 2GB should be more than enough.

If you still have the nxt.log from the 2nd attempt:
Did you get the same "Error opening database: "Concurrent update" [8000-194]" exception in nxt.log after setting -mx800m ?
Did you also get the "java.lang.OutOfMemoryError: GC overhead limit exceeded" message?
Can you still tell how far did the blockchain download go before your node was stopped?

Sorry, I no longer have the nxt.log from the second attempt.
"Can you still tell how far did the blockchain download go before your node was stopped?" - It stopped almost immediately.
One "unusual" thing I did was to use my nxt_db backup from v1.8.11 as the starting point after it failed immediately after upgrading. That was when I got the Critical Error. Could this be the culprit?
Title: Re: NRS v1.11.5
Post by: Riker on April 09, 2017, 05:46:08 am
Sorry, I no longer have the nxt.log from the second attempt.
"Can you still tell how far did the blockchain download go before your node was stopped?" - It stopped almost immediately.
[/size]One "unusual" thing I did was to use my nxt_db backup from v1.8.11 as the starting point after it failed immediately after upgrading. That was when I got the Critical Error. Could this be the culprit?

Possibly, sometimes the H2 database needs compaction after a while.
For this purpose we developed the compact.sh / compact.bat script. Run it from the command line in order to compact the database which may solve this type of problems. It also considerably reduces the database size.
Title: Re: NRS v1.11.5
Post by: MrV777 on May 20, 2017, 11:03:34 am
I finally upgraded to 1.11.x :) but I am getting this error in the Chrome Console when I try to load the client and it just stays on the blue screen then:
Code: [Select]
GET http://192.168.13.15:57876/cordova.js 404 (Not Found)
jquery.js:8554 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery.js:8554
ajax @ jquery.js:8152
jQuery.(anonymous function) @ jquery.js:8298
NRS.loadLockscreenHTML @ nrs.sitebuild.js:27
(anonymous) @ index.html:90
nrs.js:1611 document.ready
nrs.settings.js:461 Uncaught TypeError: $.t is not a function
    at Object.NRS.createRegionalFormatSelect (nrs.settings.js:461)
    at Object.NRS.getSettings (nrs.settings.js:479)
    at Object.NRS.init (nrs.js:172)
    at HTMLDocument.<anonymous> (nrs.js:1612)
    at fire (jquery.js:3073)
    at Object.fireWith [as resolveWith] (jquery.js:3185)
    at Function.ready (jquery.js:3391)
    at HTMLDocument.completed (jquery.js:3407)
NRS.createRegionalFormatSelect @ nrs.settings.js:461
NRS.getSettings @ nrs.settings.js:479
NRS.init @ nrs.js:172
(anonymous) @ nrs.js:1612
fire @ jquery.js:3073
fireWith @ jquery.js:3185
ready @ jquery.js:3391
completed @ jquery.js:3407
nrs.console.js:39 2017-05-20T06:02:11 navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
nrs.console.js:39 2017-05-20T06:02:11 navigator.platform = MacIntel
nrs.console.js:39 2017-05-20T06:02:11 navigator.appVersion = 5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
nrs.console.js:39 2017-05-20T06:02:11 navigator.appName = Netscape
nrs.console.js:39 2017-05-20T06:02:11 navigator.appCodeName = Mozilla
nrs.console.js:39 2017-05-20T06:02:11 navigator.hardwareConcurrency = 4
nrs.console.js:39 2017-05-20T06:02:11 navigator.maxTouchPoints = 0
nrs.console.js:39 2017-05-20T06:02:11 navigator.languages = en-US,en
nrs.console.js:39 2017-05-20T06:02:11 navigator.language = en-US
nrs.console.js:39 2017-05-20T06:02:11 navigator.userLanguage = undefined
nrs.console.js:39 2017-05-20T06:02:11 navigator.cookieEnabled = true
nrs.console.js:39 2017-05-20T06:02:11 navigator.onLine = true
nrs.console.js:39 2017-05-20T06:02:11 NRS.isTestNet = false
nrs.console.js:39 2017-05-20T06:02:11 NRS.needsAdminPassword = true
nrs.plugins.js:196 Uncaught TypeError: $.t is not a function
    at nrs.plugins.js:196
    at Object.<anonymous> (nrs.server.js:474)
    at fire (jquery.js:3073)
    at Object.fireWith [as resolveWith] (jquery.js:3185)
    at Object.then.failureArgs (ajaxretry.js:101)
    at Object.<anonymous> (jquery.js:3230)
    at fire (jquery.js:3073)
    at Object.fireWith [as resolveWith] (jquery.js:3185)
    at done (jquery.js:8251)
    at XMLHttpRequest.<anonymous> (jquery.js:8598)
Title: Re: NRS v1.11.5
Post by: Riker on May 20, 2017, 02:44:32 pm
I finally upgraded to 1.11.x :) but I am getting this error in the Chrome Console when I try to load the client and it just stays on the blue screen then:
Code: [Select]
GET http://192.168.13.15:57876/cordova.js 404 (Not Found)
jquery.js:8554 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery.js:8554
ajax @ jquery.js:8152
jQuery.(anonymous function) @ jquery.js:8298
NRS.loadLockscreenHTML @ nrs.sitebuild.js:27
(anonymous) @ index.html:90
nrs.js:1611 document.ready
nrs.settings.js:461 Uncaught TypeError: $.t is not a function
    at Object.NRS.createRegionalFormatSelect (nrs.settings.js:461)
    at Object.NRS.getSettings (nrs.settings.js:479)
    at Object.NRS.init (nrs.js:172)
    at HTMLDocument.<anonymous> (nrs.js:1612)
    at fire (jquery.js:3073)
    at Object.fireWith [as resolveWith] (jquery.js:3185)
    at Function.ready (jquery.js:3391)
    at HTMLDocument.completed (jquery.js:3407)
NRS.createRegionalFormatSelect @ nrs.settings.js:461
NRS.getSettings @ nrs.settings.js:479
NRS.init @ nrs.js:172
(anonymous) @ nrs.js:1612
fire @ jquery.js:3073
fireWith @ jquery.js:3185
ready @ jquery.js:3391
completed @ jquery.js:3407
nrs.console.js:39 2017-05-20T06:02:11 navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
nrs.console.js:39 2017-05-20T06:02:11 navigator.platform = MacIntel
nrs.console.js:39 2017-05-20T06:02:11 navigator.appVersion = 5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
nrs.console.js:39 2017-05-20T06:02:11 navigator.appName = Netscape
nrs.console.js:39 2017-05-20T06:02:11 navigator.appCodeName = Mozilla
nrs.console.js:39 2017-05-20T06:02:11 navigator.hardwareConcurrency = 4
nrs.console.js:39 2017-05-20T06:02:11 navigator.maxTouchPoints = 0
nrs.console.js:39 2017-05-20T06:02:11 navigator.languages = en-US,en
nrs.console.js:39 2017-05-20T06:02:11 navigator.language = en-US
nrs.console.js:39 2017-05-20T06:02:11 navigator.userLanguage = undefined
nrs.console.js:39 2017-05-20T06:02:11 navigator.cookieEnabled = true
nrs.console.js:39 2017-05-20T06:02:11 navigator.onLine = true
nrs.console.js:39 2017-05-20T06:02:11 NRS.isTestNet = false
nrs.console.js:39 2017-05-20T06:02:11 NRS.needsAdminPassword = true
nrs.plugins.js:196 Uncaught TypeError: $.t is not a function
    at nrs.plugins.js:196
    at Object.<anonymous> (nrs.server.js:474)
    at fire (jquery.js:3073)
    at Object.fireWith [as resolveWith] (jquery.js:3185)
    at Object.then.failureArgs (ajaxretry.js:101)
    at Object.<anonymous> (jquery.js:3230)
    at fire (jquery.js:3073)
    at Object.fireWith [as resolveWith] (jquery.js:3185)
    at done (jquery.js:8251)
    at XMLHttpRequest.<anonymous> (jquery.js:8598)

Did you refresh the browser to reload the new JavaScript code?
Title: Re: NRS v1.11.5
Post by: MrV777 on May 20, 2017, 10:29:52 pm
Interesting I did a refresh like you said, but still got the errors.  I opened it in an incognito window and it seemed to load up with the only error being about cordova.js
So something is still cached.  I hate when that happens  :(
Sorry to bother you
Title: Re: NRS v1.11.5
Post by: nxtmad2017 on May 22, 2017, 07:41:34 pm
Good day.

How can i know that the .exe file is not compromised or corrupted?. If in properties, in digital signature says by "Stichting NXT" is ok? is there any other way to check this, so i can be safe installing the exe file?

Where can i learn how to work with the .zip file. There is no .exe file, so how do i execute it?.

THANKS in advance.
Title: Re: NRS v1.11.5
Post by: qq2536007339 on May 26, 2017, 12:37:02 am
Where can i learn how to work with the .zip file. There is no .exe file, so how do i execute it?.

If you read README.txt,you will know.Execute run.bat to run if you use windows.
Title: Re: NRS v1.11.5
Post by: kpstolk on June 01, 2017, 05:09:51 pm
Just noticed that https://nxt.jelurida.com runs NRS Version: 1.11.6, but this version isn't released yet?
Title: Re: NRS v1.11.5
Post by: Jean-Luc on June 03, 2017, 09:48:06 am
1.11.6 will be released under the JPL (https://www.jelurida.com/jelurida-public-license). We must finalize the terms and conditions of the license before releasing it, so this can take some time.
Title: Re: NRS v1.11.5
Post by: qq2536007339 on June 07, 2017, 08:48:02 am
Is there a errorCode list for API error? I would like to see it.
Title: Re: NRS v1.11.5
Post by: kunibopl on June 07, 2017, 02:33:58 pm
I am running nxt on a raspi (on local network) and want to access the UI from different machines in this local network as well as do json API requests.
Right now it is open for all. What do I have to change to allow above access only from localhost and from 192.168.88.0/24?

Code: [Select]
# Hosts from which to allow http/json API requests, if enabled. Set to * to allow all.
# Can also specify networks in CIDR notation, e.g. 192.168.1.0/24.
#nxt.allowedBotHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
nxt.allowedBotHosts=*; localhost; [0:0:0:0:0:0:0:1];


# Host interface on which to listen for http/json API request, default localhost only.
# Set to 0.0.0.0 to allow the API server to accept requests from all network interfaces.
#nxt.apiServerHost=127.0.0.1
nxt.apiServerHost=0.0.0.0


# Hosts from which to allow NRS user interface requests, if enabled. Set to * to allow all.
#nxt.allowedUserHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1];
nxt.allowedUserHosts=*; localhost; [0:0:0:0:0:0:0:1];


# Host interface for NRS user interface server, default localhost only.
# Set to 0.0.0.0 to allow the UI to be accessed on all network interfaces.
#nxt.uiServerHost=127.0.0.1
nxt.uiServerHost=0.0.0.0
Title: Re: NRS v1.11.5
Post by: lurker10 on June 15, 2017, 03:38:50 pm
User reported strange behavior with the nxt.properties file, unable to save custom config.
https://www.reddit.com/r/Ardor/comments/6hewpm/does_blockchain_need_to_be_completely_dl_for/dixx9u4/
Title: Re: NRS v1.11.5
Post by: Nxtblg on June 15, 2017, 08:17:35 pm
Hi, everyone,

I'm having trouble with Arbitrary Messages. When I send an encrypted message, it goes through fine. But when I try to send an unencrypted message - the same message that goes through when encrypted - I get this error: "Peer sends invalid transactions... Invalid transaction signature for transaction".

Full error:
Code: [Select]
2017-06-15 16:08:41 FINE: Peer 50.159.16.84 version 1.11.5 returned error: {"error":"nxt.NxtException$NotValidException: Peer sends invalid transactions: [nxt.NxtException$NotValidException: Invalid transaction signature for transaction {\"senderPublicKey\":\"79536ac28d434558340bd220664b09a99a49737968467b9ed301d57ff1a34e1d\",\"signature\":\"780767372398d16b9924f484ad6e44dd1dcb32d0aab41df0c6572f71e959ff0978d0bcebfd8b44d1020227d4d1b91c81ddbe4a0298bad431584e9e2e0ff7120f\",\"feeNQT\":100000000,\"type\":1,\"version\":1,\"ecBlockId\":\"4936781828829390790\",\"attachment\":{\"version.PrunablePlainMessage\":1,\"messageIsText\":true,\"messageHash\":\"43e78621d791240a184e645eb2181badd0da86d0dd94d46adb50d152d21fa1a3\",\"message\":\"DYAAATMLIDHETLMFPCBBHINCUHMJNZOBYJTI9S9LSZKJMHHLCAXCE9CPWSJVACHWDDYG9JCAAMRGAYDSEEIUUUWDHP\\r\\n\\r\\nIn re earlier transfer of 5 KIOTA, tx id 16608535274209269220 .\\r\\n\\r\\nThe above is the new IOTA address, which I've generated, added to the Tangle and verified at http:\\\/\\\/www.iota.cool\\\/ . Feel free to check it yourself, &amp; pls send the IOTA to the above addy.\\r\\n\\r\\n\\r\\nThanks once again,\\r\\nNxtblg\",\"version.ArbitraryMessage\":0},\"subtype\":0,\"amountNQT\":0,\"recipient\":\"7391598936214566700\",\"ecBlockHeight\":1204000,\"deadline\":1440,\"timestamp\":112262919}]"}, request was: {"protocol":1,"requestType":"processTransactions","transactions":[{"senderPublicKey":"79536ac28d434558340bd220664b09a99a49737968467b9ed301d57ff1a34e1d","signature":"780767372398d16b9924f484ad6e44dd1dcb32d0aab41df0c6572f71e959ff0978d0bcebfd8b44d1020227d4d1b91c81ddbe4a0298bad431584e9e2e0ff7120f","feeNQT":100000000,"type":1,"version":1,"ecBlockId":"4936781828829390790","attachment":{"version.PrunablePlainMessage":1,"messageIsText":true,"messageHash":"43e78621d791240a184e645eb2181badd0da86d0dd94d46adb50d152d21fa1a3","message":"DYAAATMLIDHETLMFPCBBHINCUHMJNZOBYJTI9S9LSZKJMHHLCAXCE9CPWSJVACHWDDYG9JCAAMRGAYDSEEIUUUWDHP\r\n\r\nIn re earlier transfer of 5 KIOTA, tx id 16608535274209269220 .\r\n\r\nThe above is the new IOTA address, which I've generated, added to the Tangle and verified at http:\/\/www.iota.cool\/ . Feel free to check it yourself, &amp; pls send the IOTA to the above addy.\r\n\r\n\r\nThanks once again,\r\nNxtblg","version.ArbitraryMessage":0},"subtype":0,"amountNQT":0,"recipient":"7391598936214566700","ecBlockHeight":1204000,"deadline":1440,"timestamp":112262919}]}, disconnecting

The person I'm sending the message to asked me to send an abbreviated message, with just capital letters and 9s. That went through.

But there does seem to be a bug somewhere. Since the abbreviated message went through, it's likely due to a non-alphanumertic character getting caught in the wringer somewhere. FYI, and thanks.

Title: Re: NRS v1.11.5
Post by: suhtherngirl on July 12, 2017, 09:56:31 am
I experienced a serious situation in which a pair of NXT Server "features" together contributed to my sending out a significant number of NXT unintentionally:

This is in the Shapeshift pop-up transaction window.

1) The message field is not cleared upon clicking the "Send NXT" button to complete a coin trade.

2) The Send NXT button in the Shapeshift pop-up does not lock after being clicked.

The result is...
Yes.  I ended up with 2 identical transactions a few seconds apart.

Very annoying.

Potentially devastating.

My system had a lot going on and so was slow.  It would be a huge help if, upon clicking the Send NXT button and before doing anything else, the pop-up immediately cleared the message field and locked the Send NXT button.
Title: Re: NRS v1.11.5
Post by: Riker on July 13, 2017, 01:14:36 pm
I experienced a serious situation in which a pair of NXT Server "features" together contributed to my sending out a significant number of NXT unintentionally:

This is in the Shapeshift pop-up transaction window.

1) The message field is not cleared upon clicking the "Send NXT" button to complete a coin trade.

2) The Send NXT button in the Shapeshift pop-up does not lock after being clicked.

The result is...
  • I mis-spelled my password.  The bad password message appeared.
  • I re-typed my password, and clicked the Send NXT button again.  The message still said that the password was bad, and so
  • I clicked the Send NXT button again.
Yes.  I ended up with 2 identical transactions a few seconds apart.

Very annoying.

Potentially devastating.

My system had a lot going on and so was slow.  It would be a huge help if, upon clicking the Send NXT button and before doing anything else, the pop-up immediately cleared the message field and locked the Send NXT button.

I pushed a fix for this, it should be resolved in the next release.
Title: Re: NRS v1.11.5
Post by: zkjiang on July 22, 2017, 01:33:15 am
Hi, I got a problem installing NXT client 1.11.5, here is the message:

C:\Users\Administrator>C:\Users\Administrator\Downloads\nxt\nxt\run.bat
Java version in "HKLM\SOFTWARE\JavaSoft\Java Runtime Environment" is "1.8" and in "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment" is ""
using Java home directory "C:\Program Files\Java\jre1.8.0_141"

Can anyone help me out?
Thanks!
Title: Re: NRS v1.11.5
Post by: Riker on July 22, 2017, 01:36:20 pm
Hi, I got a problem installing NXT client 1.11.5, here is the message:

C:\Users\Administrator>C:\Users\Administrator\Downloads\nxt\nxt\run.bat
Java version in "HKLM\SOFTWARE\JavaSoft\Java Runtime Environment" is "1.8" and in "HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment" is ""
using Java home directory "C:\Program Files\Java\jre1.8.0_141"

Can anyone help me out?
Thanks!

You should download the Windows installer nxt-client-1.11.5.exe
See https://nxtforum.org/nrs-releases/nrs-v1-11-5/
elective-stereophonic
elective-stereophonic
assembly
assembly