elective-stereophonic
elective-stereophonic
NRS v1.9.2
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 2 [3] 4 5  All

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

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.9.2
« Reply #40 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.
« Last Edit: July 12, 2016, 07:50:28 am by Riker »
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

CryptKeeper

  • Hero Member
  • *****
  • Karma: +78/-5
  • Offline Offline
  • Posts: 1235
    • View Profile
Re: NRS v1.9.2
« Reply #41 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.
Logged
Follow me on twitter for the latest news on bitcoin and altcoins!
Vanity Accounts Sale :-)

bitme

  • Jr. Member
  • **
  • Karma: +22/-4
  • Offline Offline
  • Posts: 98
  • strange things happen ...
    • View Profile
Re: NRS v1.9.2
« Reply #42 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
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.9.2
« Reply #43 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 ?
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

bitme

  • Jr. Member
  • **
  • Karma: +22/-4
  • Offline Offline
  • Posts: 98
  • strange things happen ...
    • View Profile
Re: NRS v1.9.2
« Reply #44 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
Logged

altsheets

  • Full Member
  • ***
  • Karma: +31/-1
  • Offline Offline
  • Posts: 232
  • check out #AAssetNXT #AltFolio and #AssetGraphs
    • View Profile
    • AssetGraphs-v2 live examples
Re: NRS v1.9.2
« Reply #45 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) ?


Logged
AltFolio | Newbium DataSite | AAssetNXT & -HZ | AssetGraphs | ABEE | Advice | assetparser.py & shareholders.py | bamm.py | PeerCrawler | Github e.g. ChainCountDown, ethjsre | ... much more

NxtSwe

  • Hero Member
  • *****
  • Karma: +124/-9
  • Offline Offline
  • Posts: 657
    • View Profile
Re: NRS v1.9.2
« Reply #46 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.
« Last Edit: July 16, 2016, 06:10:50 am by NxtSwe »
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.9.2
« Reply #47 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
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.9.2
« Reply #48 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
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

NxtSwe

  • Hero Member
  • *****
  • Karma: +124/-9
  • Offline Offline
  • Posts: 657
    • View Profile
Re: NRS v1.9.2
« Reply #49 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.
« Last Edit: July 16, 2016, 10:57:16 am by NxtSwe »
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.

altsheets

  • Full Member
  • ***
  • Karma: +31/-1
  • Offline Offline
  • Posts: 232
  • check out #AAssetNXT #AltFolio and #AssetGraphs
    • View Profile
    • AssetGraphs-v2 live examples
Re: NRS v1.9.2
« Reply #50 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  ;)
« Last Edit: July 16, 2016, 08:20:17 pm by altsheets »
Logged
AltFolio | Newbium DataSite | AAssetNXT & -HZ | AssetGraphs | ABEE | Advice | assetparser.py & shareholders.py | bamm.py | PeerCrawler | Github e.g. ChainCountDown, ethjsre | ... much more

OBAViJEST

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 3
    • View Profile
Re: NRS v1.9.2
« Reply #51 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  :-[
Logged

ScripterRon

  • Hero Member
  • *****
  • Karma: +75/-2
  • Offline Offline
  • Posts: 523
    • View Profile
Re: NRS v1.9.2
« Reply #52 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.
Logged

wilstt

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 8
    • View Profile
Re: NRS v1.9.2
« Reply #53 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.
Logged

ScripterRon

  • Hero Member
  • *****
  • Karma: +75/-2
  • Offline Offline
  • Posts: 523
    • View Profile
Re: NRS v1.9.2
« Reply #54 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.
Logged

wilstt

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 8
    • View Profile
Re: NRS v1.9.2
« Reply #55 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
« Last Edit: July 20, 2016, 03:01:14 am by wilstt »
Logged

ScripterRon

  • Hero Member
  • *****
  • Karma: +75/-2
  • Offline Offline
  • Posts: 523
    • View Profile
Re: NRS v1.9.2
« Reply #56 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
Logged

wilstt

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 8
    • View Profile
Re: NRS v1.9.2
« Reply #57 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
Logged

ScripterRon

  • Hero Member
  • *****
  • Karma: +75/-2
  • Offline Offline
  • Posts: 523
    • View Profile
Re: NRS v1.9.2
« Reply #58 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
Logged

wilstt

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 8
    • View Profile
Re: NRS v1.9.2
« Reply #59 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
Logged
Pages: 1 2 [3] 4 5  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly