3 Wallets on 3 Different Computers Crashed at the Same Time.
-
I not sure if that IP:
192.168.0.13would make it crash, because my network is set to use IP rang of:10.0.0.xxx, 10.0.1.xxx, 10.0.2.xxx, 10.0.3.xxx, 10.0.4.xxx, and 10.0.5.xxx.But I removed that IP:192.168.0.13anyway. And yes I have been use QoS. Hope it now works. Thanks for all your help!! :-)
-
@Tate-A Yes of course, it was for example 192.168.0.13
-
@crutsy @Tate-A @HAITCH @Global-Moderators 213.160.187.186 pool.burstcoin.sk wallet ? NRS127 why ? little bit crazy situation Crowetic, pls re check again Your nice Black List
-
@FLEGI You don't have to ping Global-Moderators. Haitch and Crowetic is not even a part of them.
-
@FrilledShark Aha ok administrators, I am right ?, nice to know, Thank You ! Cheers Flegi :-)
-
@crutsy As @FLEGI said, any reason pool.burstcoin.sk ( 213.160.187.186) is included in the list ? It's a 1.2.7 wallet.
-
@FLEGI @haitch This was an ongoing list. I would update it daily. The jump from 1.2.4 to 1.2.6 happend very quick and people were not updating.
This is just my personal list. I have been meaning to update it but have not had much time. So anyone feel free to do so.
I have been assured by @Focus that the next wallet release will black list 1.2.5 and lower. So I haven't been in much of a rush to confuse everyone if 1.2.8 fixes the problem.
Long story short you don't want any walled connecting to a 1.2.5 wallet!
-
@crutsy Some more for the list:
dvcstable01.dvcnode.org
crossciv.no-ip.org
213.32.102.140
212.65.15.181
199.116.131.9
212.65.15.181
192.198.95.50
79.133.238.86
-
@haitch I'll update ASAP
-
@haitch awesome thanks!
These two are on the list they just have to be expressed in IP, format learned that the hard way.
-
@crutsy The other problem we have is that some wallets - including freshly downloaded from scratch wallets - where the DB is going to 10GB. I've fixed all mine (thanks @Focus for the clean download ) - we need everyone running a local wallet to check the burst_db folder, and if it has a 10GB burst.mv.db, stop the wallet, download a clean DB from either https://db.burst-team.us/db.zip or
. Unzip it into your burst_db overwriting the existing files, and then restart your wallet.
-
@haitch I experienced that problem when I was trying to figure this out. It stayed consistent with 1.2.5
This was months back and at the time it would jump to like 6GB. It was confusing because if you don't start with a fresh wallet and a fresh db it would happen. If you don't start fresh the old burst.jar still loads 1.2.5 and blows the DB.
I love that my wallet has been running for months and months with no problem. :)
-
@crutsy Some of mine have been absolutely fine, but when I took the onlines to 1.2.7, two have them wouldn't accept the 1.26 wallet DB, and a fresh from scratch download had them both blow up to 10GB, then the other two both also blew up to 10GB. This is something new I think, I've not seen it on any of my wallets until I did the upgrades.
-
@haitch interesting I will keep my eye open and try to get sometime to play with it.
Could those two 1.2.6 wallets possibly have databases left over from 1.2.5? Just a guess
-
@crutsy Nope, they'd both re-downloaded from scratch. All 4 had been done from scratch, and they all blew up.
-
@haitch Oh ok gotcha my bad miss understood what you were saying. I will try to replicate the problem
-
@crutsy To 100% clarify - they'd all downloaded from scratch as 1.2.6 and were fine. Two of them upgraded to 1.2.7 and were fine, then later blew up in size. The other two rejected the 1.2.6 DB's, were downloaded from scratch, and on completion of download were at 10GB
-
@crutsy @daWallet @Tate-A @ccminer @haitch I think it isn't big problem for us, but nice to have good network Peer to Peer for all. Idea is good.
May be is better create new TOPIC with, I don't know, ( Old Wallets Banned and Black Listed - Upgrade it please Right Now to minimal version NRS 126 ) What do You think about this ? Cheers FLEGI
PS: I think problem was started when Poloniex has problem https://forums.burst-team.us/topic/3311/poloniex-disabled-deps-and-wds-for-maintenance , but I don't know why our IP address was added to Black List.
Thank You all.
-
Revenue from v2Pool asset is helping support this project. When this miner is built, 10% of the mining revenue will be sent to v2Pool asset. A total of 60% of mining revenue will be sent to both assets!
Buy from Asset Issuer to help support this project. Asset ID: 14111531369712118954
See more here: https://forums.burst-team.us/post/44508



