3 Wallets on 3 Different Computers Crashed at the Same Time.
-
@FLEGI Here my config:
############################################################ # Do not modify this file. Instead, create a # # nxt.properties file and make your changes there. # # They will overwrite the defaults! # ############################################################ #### PEER NETWORKING #### # Announce my IP address/hostname to peers and allow them to share it with other peers. # If disabled, peer networking servlet will not be started at all. nxt.shareMyAddress=true # Port for incoming peer to peer networking requests, if enabled. nxt.peerServerPort=8123 # Host interface on which to listen for peer networking requests, default all. # Use 0.0.0.0 to listen on all IPv4 interfaces or :: to listen on all IPv4 and IPv6 interfaces nxt.peerServerHost=0.0.0.0 # My externally visible IP address or host name, to be announced to peers. # It can optionally include a port number, which will also be announced to peers, # and may be different from nxt.peerServerPort (useful if you do port forwarding behind a router). nxt.myAddress= # My platform, to be announced to peers. nxt.myPlatform=PC # My hallmark, if available. nxt.myHallmark= # A list of well known peer addresses / host names, separated by '; '. # If not set, a random selection of nxtcrypto.org and nxtbase.com nodes is used. nxt.wellKnownPeers=192.168.0.13; burst.ninja; 176.9.101.198; 46.237.194.160; 80.150.243.95; 162.245.20.201; 119.81.44.170; 119.81.44.171 # Known bad peers to be blacklisted nxt.knownBlacklistedPeers= # Peers used for testnet only. nxt.testnetPeers= # Maintain active connections with at least that many peers. nxt.maxNumberOfConnectedPublicPeers=20 # Peer networking connect timeout for outgoing connections. nxt.connectTimeout=4000 # Peer networking read timeout for outgoing connections. nxt.readTimeout=8000 # Peer networking server idle timeout, milliseconds. nxt.peerServerIdleTimeout=30000 # Use the peer hallmark to only connect with peers above the defined push/pull hallmark thresholds. nxt.enableHallmarkProtection=false # Hallmark threshold to use when sending data to peers. nxt.pushThreshold=0 # Hallmark threshold to use when requesting data from peers. nxt.pullThreshold=0 # Blacklist peers for 600000 milliseconds (i.e. 10 minutes by default). nxt.blacklistingPeriod=600000 # Consider a new transaction or block sent after 10 peers have received it. nxt.sendToPeersLimit=10 # Enable the Jetty Denial of Service Filter for the peer networking server. nxt.enablePeerServerDoSFilter=true # Compress Http responses for the peer networking server. nxt.enablePeerServerGZIPFilter=true # Use testnet, leave set to false unless you are really testing. # Never unlock your real accounts on testnet! Use separate accounts for testing only. # When using testnet, all custom port settings will be ignored, # and hardcoded ports of 6874 (peer networking), 6875 (UI) and 6876 (API) will be used. nxt.isTestnet=false # Save known peers in the database nxt.savePeers=true # Set to false to disable use of the peers database. This will not delete saved peers. nxt.usePeersDb=true # Set to false to disable getting more peers from the currently connected peers. Only useful # when debugging and want to limit the peers to those in peersDb or wellKnownPeers. nxt.getMorePeers=true # Set to true to run offline - do not connect to peers and do not listen for incoming peer # connections. This is equivalent to setting nxt.shareMyAddress=false, nxt.wellKnownPeers=, # nxt.testnetPeers= and nxt.usePeersDb=false, and if set to true overrides those properties. nxt.isOffline=false # Enable re-broadcasting of new transactions until they are received back from at least one # peer, or found in the blockchain. This feature can optionally be disabled, to avoid the # risk of revealing that this node is the submitter of such re-broadcasted new transactions. nxt.enableTransactionRebroadcasting=true #### API SERVER #### # Accept http/json API requests. nxt.enableAPIServer=true # Hosts from which to allow http/json API requests, if enabled. nxt.allowedBotHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1]; pool.burstcoin.ml:8020; # Port for http/json API requests. nxt.apiServerPort=8125 # Host interface on which to listen for http/json API request, default localhost only. # Set to 0.0.0.0 to allow the API server to accept requests from all network interfaces. nxt.apiServerHost=127.0.0.1 # Idle timeout for http/json API request connections, milliseconds. nxt.apiServerIdleTimeout=30000 # Directory with html and javascript files for the new client UI, and admin tools utilizing # the http/json API. nxt.apiResourceBase=html/ui # Java API documentation directory, optional. nxt.javadocResourceBase=html/doc # Enable Cross Origin Filter for the API server. nxt.apiServerCORS=false # Enable SSL for the API server (also need to set nxt.keyStorePath and nxt.keyStorePassword). nxt.apiSSL=false # Enforce requests that require POST to only be accepted when submitted as POST. nxt.apiServerEnforcePOST=true # Compress Http responses for the API server. nxt.enableAPIServerGZIPFilter=false #### OLD NRS USER INTERFACE #### # Enable the deprecated NRS user interface. nxt.enableUIServer=false # Hosts from which to allow NRS user interface requests, if enabled. nxt.allowedUserHosts=127.0.0.1; localhost; [0:0:0:0:0:0:0:1]; # Port for NRS user interface server. nxt.uiServerPort=7875 # Host interface for NRS user interface server, default localhost only. # Set to 0.0.0.0 to allow the UI to be accessed on all network interfaces. nxt.uiServerHost=127.0.0.1 # Idle timeout for NRS user interface server, milliseconds. nxt.uiServerIdleTimeout=30000 # Directory with html and javascript files for the NRS client user interface. nxt.uiResourceBase=html/nrs # Enable Cross Origin Filter for NRS user interface server. nxt.uiServerCORS=false # Enable SSL for the NRS user interface (also need to set nxt.keyStorePath and nxt.keyStorePassword). nxt.uiSSL=false # Enforce requests that require POST to only be accepted when submitted as POST. nxt.uiServerEnforcePOST=true #### DEBUGGING #### # Log file, will be overwritten at every restart. #nxt.log=nxt.log # The log file is now specified in logging.properties. # Enable debug log output. #nxt.debug=false # Debug logging is now specified in logging properties. # Include caller traceback in log messages. nxt.enableLogTraceback=false # Enable logging of exception stack traces. nxt.enableStackTraces=true # Enable logging of Jetty messages. #nxt.debugJetty=false # Jetty logging is now specified in logging properties. # Used for debugging peer to peer communications. nxt.communicationLoggingMask=0 # Track balances of the following accounts and related events for debugging purposes. nxt.debugTraceAccounts= # File name for logging tracked account balances. nxt.debugTraceLog=nxt-trace.csv # Separator character for trace log. nxt.debugTraceSeparator=\t # Quote character for trace log. nxt.debugTraceQuote=" # Log changes to unconfirmed balances. nxt.debugLogUnconfirmed=false #### DATABASE #### # Database connection JDBC url, see the H2 documentation for possible customizations. # Append ;AUTO_SERVER=TRUE to enable automatic mixed mode access. # The nxt_db folder is expected to be in the current working directory, will be created if missing. nxt.dbUrl=jdbc:h2:./burst_db/burst;DB_CLOSE_ON_EXIT=FALSE # Database connection JDBC url to use with the test network, if isTestnet=true nxt.testDbUrl=jdbc:h2:./burst_test_db/burst;DB_CLOSE_ON_EXIT=FALSE # Database connection timeout in seconds. nxt.dbLoginTimeout=70 # Database default lock timeout in seconds. nxt.dbDefaultLockTimeout=60 # Maximum simultaneous database connections. nxt.maxDbConnections=30 # The memory allocated to database cache, in kB. # If set to 0, defaults to 50 % of the memory available to the JVM. nxt.dbCacheKB=0 #### JETTY #### # Settings for the Jetty Denial Of Service Filter, used for the peer networking server only. nxt.peerServerDoSFilter.maxRequestsPerSec=30 nxt.peerServerDoSFilter.delayMs=1000 nxt.peerServerDoSFilter.maxRequestMs=300000 # keystore file and password, required if uiSSL or apiSSL are enabled. nxt.keyStorePath=keystore nxt.keyStorePassword=password #### Developers only #### # Force re-validation of blocks and transaction at start. nxt.forceValidate=false # Force re-build of derived objects tables at start. nxt.forceScan=false # Print a list of peers having this version on exit. nxt.dumpPeersVersion= # Enable trimming of derived objects tables. nxt.trimDerivedTables=true # If trimming enabled, maintain enough previous height records to allow rollback of at least # that many blocks. Must be at least 1440 to allow normal fork resolution. After increasing # this value, a full re-scan needs to be done in order for previously trimmed records to be # re-created and preserved. nxt.maxRollback=1440 # Enable API requests used for blockchain and database manipulation. nxt.enableDebugAPI=false # Debug option for Testnet: Winning with every Deadline burst.mockMining = false # GPU Blocksync Acceleration / experimental ! burst.oclAuto=false burst.oclVerify=false # If 'burst.oclAuto=false' gpu must be specified burst.oclPlatform=0 burst.oclDevice=0 burst.oclMemPercent=50 burst.oclHashesPerEnqueue=1000
-
@Tate-A All 3 computers have the same config file
-
@Tate-A There was a huge error throughout the wallets the day or so :)
-
Delete internal network IP addresses nxt.wellKnownPeers=192.168.0.13 , and for better network performance I recommend
nxt.getMorePeers=false
-
@FLEGI Enable QoS on Your router and more Blocks for Your POOL may come.
pool 8124 tcp/udp 4000~ Highest
pool socket 4443 tcp/udp 4000~ Highest
wallet 8125 tcp/udp 4000~ Highest
wallet 8123 tcp/udp 4000~ Highest
wallet 8121 tcp/udp 4000~ Highest
DNS, Time, NT... 53,37,123,3... tcp/udp 0~10 Low
FaceTime(TCP) 443,5223 tcp 128~256 Low
FaceTime(UDP) 3478:3497,1... udp 128~256 Low
HTTP, SSL, Fi... 80,443,8080 tcp/udp ~512 Lowest
SMTP, POP3, I... 25,465,563,... tcp/udp 1024~2048 Lowest
WWW, SSL, HTT... 80,443,8080 tcp 0~512 Lowest
wallet2 8126 tcp/udp 4000~ Highest
pool2 8080 tcp/udp 4000~ Highest
pool2 4444 tcp/udp 4000~ Highest
-
@Tate-A You need to add all the bad ip's from anyone running 1.2.5. under
#Known bad peers to be blacklisted
5.9.38.137; 173.208.136.90; [2002:a772:9330:0:0:0:a772:9330]; 173.208.190.202; 192.95.29.212; 220.245.28.142; 82.69.50.50; [2002:c05f:1dd4:0:0:0:c05f:1dd4]; 176.9.101.198; 142.54.176.2; 128.199.135.188; 178.33.177.212; 92.27.7.209; [2a02:c7d:cc7d:a700:28f3:cfc3:cdfb:f7fe]; 212.65.15.181; 192.198.95.50; 194.44.30.113; [2a02:c7d:cc7d:a700:9cc1:b80c:8bc3:2a29]; 77.99.233.40;[2a01:4f8:161:228f:0:0:0:2]; 218.219.86.185; [2400:6180:0:d0:0:0:b8:e001]; 50.172.21.160; 85.25.200.125; 216.46.193.254; 23.92.53.153; [2002:615d:c2d7:0:450c:3adf:41e7:6c90]; [2605:a000:f803:7200:ed96:376c:f72f:2598]; 86.58.34.51; 79.133.238.86; [2002:4f85:ee56:0:0:0:4f85:ee56]; [2002:615d:c2d7:0:b56b:9d0d:cbe3:a439]; 203.128.6.219; [2002:615d:c2d7:0:dcce:f373:d468:894]; 107.181.133.122; 198.23.133.18; 212.24.110.109; [2a02:c7d:cc41:1f00:9cc1:b80c:8bc3:2a29]; 178.16.84.78; 213.32.102.140; [2a02:c7d:cc92:8600:684b:9254:fa5a:cd77]; [2a02:c7d:cc92:8600:9cc1:b80c:8bc3:2a29]; [2a02:c7d:cc92:8600:cde7:485f:cb3f:acc]; [2a02:c7d:cc92:8600:b457:cae8:70e:358a]; [2a02:c7d:cc92:8600:5cf3:1cd6:9493:6ba5]; 87.246.37.190; 5.9.99.103; [2002:509:6367:0:0:0:509:6367]; [2002:c2fc:b756:0:0:0:c2fc:b756]; 194.252.183.86; 199.116.131.9; [2a01:4a0:25:0:0:0:27b3:596f]; 64.71.72.56; 99.192.95.6; 87.246.37.174; 104.166.235.91; [2001:470:1f0b:ff3:0:0:0:947]; 5.9.70.198; 213.160.187.186; 107.173.57.109; 109.197.120.93;
-
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




