Burstcoin Wallet v1.2.8 (All Platforms)
-
-
i wouldnt recommend running a pool off this release just yet. i had mine freeze 4 times in the space of 3 days.
tross is having the same issue. i would recommend using 1.2.7 for pools atm as it seems a tad unstable. before the update i had my wallet freeze about once every 1-2 weeks
-
@Hajime said in Burstcoin Wallet v1.2.8 (All Platforms):
What is this error?
2017-02-28 19:27:57 SEVERE: Block not accepted nxt.BlockchainProcessor$TransactionNotAcceptedException: Transaction 12615558487584561666 is already in the blockchain transaction: {"senderPublicKey":"0f617b6b4e0e43693b7af851c42533a35cc07ae4e97bd1704d91b5f7722b7d4e","signature":"9053486fcd1cacd150078a7f832786780c4cc00d4c30c74cd7f98649d75c7705cfd6c3043df5790aed33046d90ef0b5dfbe07d18a3950124d43a9e41ed7d6e24","feeNQT":500000000,"type":0,"version":1,"ecBlockId":"5130721711870184961","attachment":{},"subtype":0,"amountNQT":600000000,"recipient":"8589276806381595735","ecBlockHeight":332828,"deadline":1440,"timestamp":80509123} at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:879) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)From reading the log, i clearly says that this transaction was included in a previous block, so the block you received was invalid and therefore not accepted ...
@tross The 2nd is just information in the log, for the first the whole stacktrace and not just a sniped would be interesting ... i suggest to check memory usage of wallet, for me it seam that if wallet db was copied too often (from previous versions), memory usage of wallet grows also db size is much bigger ... maybe try to make a complete resync. Check this https://forums.burst-team.us/topic/751/howto-use-opencl-gpu-for-accelerated-snyc-with-blockchain/7 fresh synced db is just 3,2GB.
But i'm just guessing.@Lexicon If you feel 1.2.7 is more stable (all from 1.2.6 is fine) ... i can not confirm that, but i'm not running a pool ... i have 4 wallets running all fine with 1.2.8 ...
I'm blocking peers running versions below 1.2.6, as they are outdated ... not sure if that improves something ... but if i look on my peers, there are ~40% running 1.2.8 already, so not all seam to have problems.
-
@luxe man totaly forgot i can blacklist those old wallets :) where is the line to add IP's?
oh and my DB is ~4GB its probably one of the cleanest dbs around :D never had an issue since 1.2.7 version released :D
-
@LithStud I use peerblock, but there must be a setting with blacklisted in nxt-default.properties.
nxt.knownBlacklistedPeers=
-
@luxe found it thanks :) i have couple wallets 1.2.2 and 1.2.3 in my peers :) been annoying me for a while with that red color :D
-
Its pretty obvious what the intentions are of someone by now using an old wallet.
-
@Burstde Some may have forgotten about a wallet running somewhere ...
-
a while back we found roughly 4 wallets running and blocked them. I think enough time has passed for these few to update. Their shouldn't be anymore links to an old 123 wallet left on the internet. So to me its obvious. We can't add an if statement that if its 123 125 then shutdown the wallet.
-
@haitch when you click download wallet on the home page it throughs this link might want to change it , if its your job there lol
https://web.burst-team.us:449/index.php/wallets/ (get site cant be reached)
-
@Bitdv yeah - that 449 needs to go, I closed up a lot of firewall holes with the new router. I'll fix. What page was it on ?
Thanks for the heads up.
-
@haitch https://web.burst-team.us/ when you click the download wallet button on top nav , thats were it redirects to
-
@Bitdv I fixed it but this is not the right thread for it. We have to use the port in parallel for some time to change the links one for one. But thank you very much, this was important!
-
@daWallet ok sorry just delete it then just was downloading the wallet and was on this page for it
-
@haitch Actually, the 449 url is out there a LOT of times - I've re-opened it for now
-
@luxe I have something new

-
@rnahlawi it is just a 'info', guess you wallet working without issue?
-
@luxe no issues at all and fully updated :) Just thought of sharing that info about a network potential threat.
-
@rnahlawi k, i also had this message once, but ignored it, due all was working ... just looked into the code, seams just a info, that not more blocks from a specific peer get requested due conditions ... nothing to worry about i guess. But this code is new, therefore you never saw this message before.
https://github.com/burst-team/burstcoin/blob/master/src/java/nxt/BlockchainProcessorImpl.java#L367
-
@luxe can you please guide me to install certificate on the wallet server and enable SSL for secure access for the wallet on port 8125?
The only settings I saw in configuration file are:
# Enable SSL for the API server (also need to set nxt.keyStorePath and nxt.keyStorePassword). nxt.apiSSL=falseI get to understand that keystorepath and keystorepasswords are the private key settings, but I cannot find the CERT file settings related to the key!




