Burstcoin Wallet v1.2.8 (All Platforms)
-
@Burstde It is no problem to contain use 1.2.7 if this helps until we find a solution, but you problem with pool software may also be related to burstnation spam transactions, sry no time now ... need to go to work ... thanks for info will look at it later in deep.
-
maybe I'm getting hit by DDos because the jetty ddosfilter lines show errors. Then I need to get cloudflare back on. Or burstnation transactions are too much and trigger this in our wallets
Denial of Service Filter - Eclipse
www.eclipse.org/jetty/documentation/9.4.x/dos-filter.html
The DoS filter keeps track of the number of requests from a connection per second. If the requests exceed the limit, Jetty rejects, delays, or throttles the request, ...
-
Just a guess, but i do not think 255 transactions per block cause issues but sending 4000 transaction at once ... if their spam script would send 255 transactions, wait for new block and send the next 255 ... we would maybe have no issues caused by that.
-
When I turn cloudflare on it says I'm not being attacked
-
@luxe could a config option be added to limit the number of unconfirmed transactions from peers that was added to the database to 255? assuming the sending wallet will rebroadcast them next block it would reduce the massive load from the thousands at a time. only hitch in my mind is prioritizing, ie ones with higher fees should be added and mined first.
-
@damncourier Basically i'm not in the development ... i just help doing the releases ... but yes maybe that would be possible/work.
-
been good since last post on errors so wallet has to be good its must be the in the errors
I'll check into setting some alternate code about ddos in jetty. This time I just restarted wallet again since yesterday replacing the database didn't make the difference.
-
Am I the only one with a wallet errors like this?
-
@Burstde looks like. you mentioned your running pool onto it?
-
can't fix it
-
@Burstde well if i read right the last screenshot you posted it cant read from the cache for db, so you might have lost your db.
did you try going back to 1.2.7? Just to see if the problem surfices again?
-
@LithStud yes both wallets are the same. database doesn't matter, I grab a new one from the forum all the time
-
@Burstde hmm now thats strange, since if only 1.2.8 would go bad you might at least try and find why, now 1.2.7 was running for a while and it was all good before.
ok lets try to go step by step. Now both versions go bad, what about not downloading blockchain and letting wallet to do it instead? Will it go bad or will it keep on syncing.
-
Though this 1.2.7 My Goal would be to follow same steps for 1.2.8
Step 1. Use database from last week (block 331111) and delete databases all for this week including 3 days of burst forums.
Step 2. Launch 1.2.7 and browser to make sure chain is finished.
Step 3. Launch pool.as of 4 hours ago pool survived.
- a small unleashing of adam stuff
- won a few blocks and survived to payout
- survived a two blocks in a row without crashing
Note previous database grew to 6gb so maybe a sign of corruption
-
@Burstde indeed it got corrupted if reached 6GB, now question is what made it to commit seppuku :/
-
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)
-
-
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



