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

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 ... 5 6 [7]  All

Author Topic: NRS v1.5.10  (Read 42161 times)

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.5.10
« Reply #120 on: June 08, 2015, 07:58:25 am »

I can see your vote transactions and your poll transactions:
txid 13052412304548680107 is a vote for poll id 9172782887829506520 etc.
But I cannot see it:

getTransaction 13052412304548680107

{
    "errorDescription": "Unknown transaction",
    "errorCode": 5
}
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.5.10
« Reply #121 on: June 08, 2015, 08:03:19 am »

I can see your vote transactions and your poll transactions:
txid 13052412304548680107 is a vote for poll id 9172782887829506520 etc.
But I cannot see it:

getTransaction 13052412304548680107

{
    "errorDescription": "Unknown transaction",
    "errorCode": 5
}

I see it, I'm on block height 445857 block id 12812850452418172186, txid 13052412304548680107 is included in block height 445169
What's your block height ?

Try to popOff all blocks up to height 445000 and let the blockchain sync
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

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.5.10
« Reply #122 on: June 08, 2015, 08:06:00 am »

I can see your vote transactions and your poll transactions:
txid 13052412304548680107 is a vote for poll id 9172782887829506520 etc.
But I cannot see it:

getTransaction 13052412304548680107

{
    "errorDescription": "Unknown transaction",
    "errorCode": 5
}

I see it, I'm on block height 445857 block id 12812850452418172186, txid 13052412304548680107 is included in block height 445169
What's your block height ?

Try to popOff all blocks up to height 445000 and let the blockchain sync
I'm on 445990. Will try to popOff.
Logged

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.5.10
« Reply #123 on: June 08, 2015, 08:18:27 am »

It synchronized properly after popOff.
What would happen if I'd not popOff and stayed on fork longer?
Logged

Tosch110

  • Hero Member
  • *****
  • Karma: +211/-18
  • Offline Offline
  • Posts: 2365
    • View Profile
Re: NRS v1.5.10
« Reply #124 on: June 08, 2015, 08:20:32 am »

I still get this message:

Code: [Select]
java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: unable to create new native thread
on all my ubuntu machines regularly. Most of the time, Nxt just stops while downloading the blockchain and I have to restart 5-6 times to finish blockchain downloading. Really annoying when I have to sit there all the hours while getting the blockchain to sync, just to restart every x minutes...

I have tried to get an answer to this, but the conversation stopped:
https://nxtforum.org/nrs-releases/nrs-v1-5-9/msg181620/#msg181620

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.5.10
« Reply #125 on: June 08, 2015, 08:32:58 am »

Hi Tosch, check your email, let's try to diagnose this together once and for all.
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

verymuchso

  • Hero Member
  • *****
  • Karma: +118/-2
  • Offline Offline
  • Posts: 549
    • View Profile
    • HEAT Ledger
Re: NRS v1.5.10
« Reply #126 on: June 08, 2015, 08:38:30 am »

Thanks. I'm looking forward to having message expiration. When a prunable message is deleted is it completely removed from the blockchain, or just "ignored" somehow?

I only ask because I can envisage a time in 100 years time when superfast computers have rendered the current incarnation of Nxt obsolete and all of our messages are decrypted for everyone to see.

So, is a pruned message definitively deleted forever?

Only the SHA256 HASH (which is a really big number basically) of the message is stored on the blockchain.
Not the message itself. So in an ideal world your message would not have been stored anywhere else.

But you could of course never be sure that no-one in the world would backup the message before it's pruned.
And there is absolutely no way in the world to know who would have done so.

I can imagine of all the temporary data flowing around on the internet that those encrypted prunable messages would sure be interesting to save and keep by certain government agencies. Another (almost free) method of persisting that data (without you knowing) would be if someone would write a bot that automatically tweets that data, perhaps even with metadata like sender/recipient.

So you could never really be sure it is deleted forever.
Logged
HEAT: DEX | SDK | HOME

shin

  • Sr. Member
  • ****
  • Karma: +47/-4
  • Offline Offline
  • Posts: 456
    • View Profile
Re: NRS v1.5.10
« Reply #127 on: June 08, 2015, 12:08:18 pm »

One more thing. because of the -Dnxt.runtime.mode=desktop flag, the NRS will now place the blockchain under c:\Users\<Username>\AppData\Roaming\NXT
In order to avoid full blockchain download, copy the folders nxt_db and nxt_test_db from your existing NXT installation folder to this folder and restart the server.
Is this a fixed place? Or is it possible to have it pointed to somewhere else other than drive C: ?
(Considering the very limited available disk space on drive C: in my case)
Logged
Wallet: NXT-ELEB-XT6G-L475-HXRFX • 18354136531262130569 • Twitter: Shin NXT

Benzedi

  • Jr. Member
  • **
  • Karma: +7/-11
  • Offline Offline
  • Posts: 85
    • View Profile
Re: NRS v1.5.10
« Reply #128 on: June 08, 2015, 03:30:38 pm »

As far as I'm aware all major centralised exchanges (e.g. polo) have still disabled NXT...
Logged

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +440/-42
  • Offline Offline
  • Posts: 1796
    • View Profile
Re: NRS v1.5.10
« Reply #129 on: June 08, 2015, 05:28:37 pm »

One more thing. because of the -Dnxt.runtime.mode=desktop flag, the NRS will now place the blockchain under c:\Users\<Username>\AppData\Roaming\NXT
In order to avoid full blockchain download, copy the folders nxt_db and nxt_test_db from your existing NXT installation folder to this folder and restart the server.
Is this a fixed place? Or is it possible to have it pointed to somewhere else other than drive C: ?
(Considering the very limited available disk space on drive C: in my case)

You can use the dburl property to control this, see https://nxtforum.org/nrs-releases/nrs-v1-5-10/msg182223/#msg182223
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

coretechs

  • Sr. Member
  • ****
  • Karma: +161/-1
  • Offline Offline
  • Posts: 436
    • View Profile
Re: NRS v1.5.10
« Reply #130 on: June 08, 2015, 08:38:35 pm »

Seems that nodes that first pull blocks from a forked node can get stuck in a few cases, perhaps due to the persistence of well known peers that may be on a fork.  For anyone out of sync still, try popping off blocks to some point far enough in the past and setting your config nxt.usePeersDb=false and setting nxt.wellKnownPeers to some nodes known to be on the right chain.






Logged
https://ardorportal.org - Ardor blockchain explorer | https://nxtportal.org - Nxt blockchain explorer | http://bitcoindoc.com - The Rise and Rise of Bitcoin
ARDOR-T43P-R2K9-8W79-9W2AL | NXT-WY9K-ZMTT-QQTT-3NBL7

sigwo

  • Full Member
  • ***
  • Karma: +14/-0
  • Offline Offline
  • Posts: 128
  • Founder, Darcrus
    • View Profile
    • Sigwo Technologies
Re: NRS v1.5.10
« Reply #131 on: June 08, 2015, 11:32:07 pm »

How do I do popOff?

sigwo$ curl --data "requestType=popOff&height=445000" http://localhost:7876/nxt

in nxt window:
2015-06-08 19:43:28 INFO: Rollback to height 445000 not supported, will do a full rescan
2015-06-08 19:43:28 FINE: Scheduled scan starting from height 0

I guess it worked?
« Last Edit: June 08, 2015, 11:46:03 pm by sigwo »
Logged

Evan

  • Sr. Member
  • ****
  • Karma: +18/-2
  • Offline Offline
  • Posts: 333
    • View Profile
Re: NRS v1.5.10
« Reply #132 on: June 09, 2015, 03:43:17 am »

did not read the full thread, when I first run this version, I see the folloing messages, are there any problems?

Code: [Select]
TRUNCATE TABLE trade
  nxt.db.TransactionalDb$DbStatement.executeUpdate(TransactionalDb.java:259)
  nxt.db.DerivedDbTable.truncate(DerivedDbTable.java:57)
  nxt.db.EntityDbTable.truncate(EntityDbTable.java:429)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1503)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1464)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1448)
  nxt.BlockchainProcessorImpl.lambda$new$17(BlockchainProcessorImpl.java:799)
  nxt.BlockchainProcessorImpl$$Lambda$6/517052730.run(Unknown Source)
  nxt.util.ThreadPool$2.run(ThreadPool.java:131)
2015-06-09 11:09:39 FINE: SQL statement required 17.848 seconds at height 445299:
TRUNCATE TABLE asset_transfer
  nxt.db.TransactionalDb$DbStatement.executeUpdate(TransactionalDb.java:259)
  nxt.db.DerivedDbTable.truncate(DerivedDbTable.java:57)
  nxt.db.EntityDbTable.truncate(EntityDbTable.java:429)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1503)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1464)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1448)
  nxt.BlockchainProcessorImpl.lambda$new$17(BlockchainProcessorImpl.java:799)
  nxt.BlockchainProcessorImpl$$Lambda$6/517052730.run(Unknown Source)
  nxt.util.ThreadPool$2.run(ThreadPool.java:131)
2015-06-09 11:09:39 FINE: Rolled back derived tables
2015-06-09 11:11:19 FINE: SQL statement required 98.936 seconds at height 0:
SELECT * FROM block WHERE height >= ? ORDER BY db_id ASC
  nxt.db.TransactionalDb$DbPreparedStatement.executeQuery(TransactionalDb.java:287)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1527)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1464)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1448)
  nxt.BlockchainProcessorImpl.lambda$new$17(BlockchainProcessorImpl.java:799)
  nxt.BlockchainProcessorImpl$$Lambda$6/517052730.run(Unknown Source)
  nxt.util.ThreadPool$2.run(ThreadPool.java:131)

Code: [Select]
2015-06-09 11:33:19 INFO: processed block 260000
2015-06-09 11:34:16 FINE: SQL statement required 10.382 seconds at height 263597:
MERGE INTO account_asset (account_id, asset_id, quantity, unconfirmed_quantity, height, latest) KEY (account_id, asset_id, height) VALUES (?, ?, ?, ?, ?, TRUE)
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:298)
  nxt.Account$AccountAsset.save(Account.java:83)
  nxt.Account$AccountAsset.access$1900(Account.java:49)
  nxt.Account$10.save(Account.java:454)
  nxt.Account$10.save(Account.java:445)
  nxt.db.EntityDbTable.insert(EntityDbTable.java:402)
  nxt.Account$AccountAsset.save(Account.java:106)
  nxt.Account$AccountAsset.access$3900(Account.java:49)
  nxt.Account.addToUnconfirmedAssetBalanceQNT(Account.java:1156)
  nxt.TransactionType$ColoredCoins$3.applyAttachmentUnconfirmed(TransactionType.java:1374)
  nxt.TransactionType.applyUnconfirmed(TransactionType.java:200)
  nxt.TransactionImpl.applyUnconfirmed(TransactionImpl.java:999)
  nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:1164)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1564)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1464)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1448)
  nxt.BlockchainProcessorImpl.lambda$new$17(BlockchainProcessorImpl.java:799)
  nxt.BlockchainProcessorImpl$$Lambda$6/517052730.run(Unknown Source)
  nxt.util.ThreadPool$2.run(ThreadPool.java:131)
2015-06-09 11:34:30 INFO: processed block 265000


Code: [Select]
2015-06-09 11:40:54 INFO: processed block 285000
2015-06-09 11:41:13 FINE: SQL statement required 11.153 seconds at height 285732:
INSERT INTO asset_transfer (id, asset_id, sender_id, recipient_id, quantity, timestamp, height) VALUES (?, ?, ?, ?, ?, ?, ?)
  nxt.db.TransactionalDb$DbPreparedStatement.executeUpdate(TransactionalDb.java:298)
  nxt.AssetTransfer.save(AssetTransfer.java:180)
  nxt.AssetTransfer.access$200(AssetTransfer.java:32)
  nxt.AssetTransfer$2.save(AssetTransfer.java:58)
  nxt.AssetTransfer$2.save(AssetTransfer.java:49)
  nxt.db.EntityDbTable.insert(EntityDbTable.java:402)
  nxt.AssetTransfer.addAssetTransfer(AssetTransfer.java:129)
  nxt.TransactionType$ColoredCoins$2.applyAttachment(TransactionType.java:1273)
  nxt.TransactionType.apply(TransactionType.java:219)
  nxt.Attachment$AbstractAttachment.apply(Attachment.java:68)
  nxt.TransactionImpl.apply(TransactionImpl.java:1019)
  nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:1178)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1564)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1464)
  nxt.BlockchainProcessorImpl.scan(BlockchainProcessorImpl.java:1448)
  nxt.BlockchainProcessorImpl.lambda$new$17(BlockchainProcessorImpl.java:799)
  nxt.BlockchainProcessorImpl$$Lambda$6/517052730.run(Unknown Source)
  nxt.util.ThreadPool$2.run(ThreadPool.java:131)
2015-06-09 11:42:27 INFO: processed block 290000
Logged
8897015223734827770
NXT-BYRU-8NKZ-PEYJ-9E6YQ

forkedchain

  • Ex-Staff Member
  • Hero Member
  • *****
  • Karma: +74/-10
  • Offline Offline
  • Posts: 1190
  • bite me
    • View Profile
Re: NRS v1.5.10
« Reply #133 on: June 09, 2015, 01:07:00 pm »

Can I send an encrypted message with an expiry time in blocks with the new client?

Send "Hello mate" and set it to expire in 14400 blocks? (about 20 days)

No, messages are either prunable, thus get deleted after two weeks exactly, or non-prunable so they are never deleted.
Setting variable pruning delay is not supported at the moment.

i dont think this will work in most cases.  in my case, I was only connected to v1.4.x peers and not to any v1.5.x peers.  so even though I got rid of all < 445000 blocks, I still redownloaded all bad blocks.

i followed coretechs advice a few posts above this one and that was the solution
Logged
NXT tips: 2319251 or NXT-8SWM-2224-YKWW-22222
Pages: 1 ... 5 6 [7]  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly