Burstcoin Wallet v1.2.8 (All Platforms)
-
Since yesterday everytime I run the wallet it stops. bunch of error messages. run it again samething. I goback to 127 runs for days
-
@Burstde It would help, if you make a screen of errors next time, 'bunch of error messages' does not help fixing issues, thanks.
-
@luxe I do have this error but wallet still running ever since It was released
-
Deleted everything I'll set it up on the secondary server and report back
-
@thomeefl69 Yes it is basically just an info ...
-
Well looks worse than that cause the screen is in a running loop of errors then pool forks everytime
-
I can report I have 1.2.7 and 1.2.8 on the same machine. Both running solo, both running fine.
-
My wallet needs to run with the pool so maybe thats the issue.
-
I uploaded new build that does not log stacktrace on 'Block not accepted' anymore.
So if you find it annoying, please re-download and replace the burst.jar
-
@luxe Downloaded again and installed on secondary server....will keep you posted when I use it for the pool
-
@Burstde I'm sinking fast cant hold any wallets for more than an hour
-
when i run pool i get this too
-
@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?
