|
EcoChavCrypto
|
 |
August 19, 2016, 12:19:33 PM |
|
My wallet keeps crashing. I replaced my wallet.dat with an older one but it doesn't help.
Give this a go: Remove all addnode addresses from darknet.conf Then delete all but darknet.conf, masternodes.conf and add a backed up wallet.dat make sure you are using the latest version of the wallet from: https://github.com/Darknet-Crypto/Darknet/releases |
|
|
|
jakiman
Legendary
 Offline
Activity: 1638
Merit: 1011
jakiman is back!
|
|
August 19, 2016, 12:21:38 PM |
|
I'm happy to say that all my masternodes & controller wallet is in sync with the block hash shown in the MN info page.  http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.htmlMy wallet keeps crashing. I replaced my wallet.dat with an older one but it doesn't help.
Try resyncing from scratch with everything deleted except the 2 conf files & pre-PoS backed up wallet. (or with a chain backup taken at or before block 259200 using the pre-PoS or pre-2.1.1.0 wallet) I did this on all the masternodes & controller wallets that were crashing and none crashed since. FYI - My controller wallet's darknet.con content is as follows: (I have 94 connections right now) rpcuser=<user> rpcpassword=<pass> rpcallowip= 127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 enableobfuscate=0 addnode=coin-server.com |
|
|
|
|
EcoChavCrypto
|
|
August 19, 2016, 12:53:09 PM |
|
I'm happy to say that all my masternodes & controller wallet is in sync with the block hash shown in the MN info page. http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.htmlMy wallet keeps crashing. I replaced my wallet.dat with an older one but it doesn't help.
Try resyncing from scratch with everything deleted except the 2 conf files & pre-PoS backed up wallet. (or with a chain backup taken at or before block 259200 using the pre-PoS or pre-2.1.1.0 wallet) I did this on all the masternodes & controller wallets that were crashing and none crashed since. FYI - My controller wallet's darknet.con content is as follows: (I have 94 connections right now) rpcuser=<user> rpcpassword=<pass> rpcallowip= 127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 enableobfuscate=0 addnode=coin-server.com I am just waiting for some nodes to be activated. What masternode information do I put into the controller wallet darknet.conf? |
|
|
|
|
Haunebu81
|
|
August 19, 2016, 01:02:42 PM |
|
Are there any other easier methods of running start-missing without crashing the wallet? I've got 100 MN's and even if I do them one at a time, it freezes up on me and I have to resync all over again.
|
|
|
|
|
|
Haunebu81
|
|
August 19, 2016, 01:07:29 PM |
|
I'm happy to say that all my masternodes & controller wallet is in sync with the block hash shown in the MN info page. http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.htmlMy wallet keeps crashing. I replaced my wallet.dat with an older one but it doesn't help.
Try resyncing from scratch with everything deleted except the 2 conf files & pre-PoS backed up wallet. (or with a chain backup taken at or before block 259200 using the pre-PoS or pre-2.1.1.0 wallet) I did this on all the masternodes & controller wallets that were crashing and none crashed since. FYI - My controller wallet's darknet.con content is as follows: (I have 94 connections right now) rpcuser=<user> rpcpassword=<pass> rpcallowip= 127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 enableobfuscate=0 addnode=coin-server.com I am just waiting for some nodes to be activated. What masternode information do I put into the controller wallet darknet.conf? You create a masternode.conf file in the same folder, and it looks like this: Masternode1 140.25.78.44:9999 masternodeprivkey transactionhash index1
Masternode1 146.328.8.22:9999 masternodeprivkey transactionhash index1
Masternode1 167.44.26.19:9999 masternodeprivkey transactionhash index1
You get the masternodeprivkey my typing "masternode genkey" in the console. You get the transactionhash by either entering your DNET MN address in a block explorer, or double clicking the transaction in the transaction tab You get the index number (0 or 1) by typing "masternode outputs" in the console. |
|
|
|
|
|
mxnsch
|
|
August 19, 2016, 01:15:03 PM |
|
Are there any other easier methods of running start-missing without crashing the wallet? I've got 100 MN's and even if I do them one at a time, it freezes up on me and I have to resync all over again.
create a script that loops over the start-alias command and start them one by one via the rpc console. I will write it up tonight if it is indeed a problem for some. Luckily it seems i am not affected with about 50 masternodes via one controller wallet. |
██ ███ nope ██ ███
|
|
|
|
FogHorn_LegHorn
|
|
August 19, 2016, 01:15:43 PM |
|
The by far easiest way to do things is below.
Go to Roaming and 'Cut' DNET folder and then paste to desktop
Download latest wallet
Launch wallet
Wait until it starts to sync
Close wallet
take wallet.dat file from DNET folder saved to desktop and replace the wallet.dat file in the new DNET folder created in Roaming
Open wallet and let fully sync.
I have done this for every new wallet version so far and have never had any issues with wallet.dat file, crashes, locking up, etc.
I am on Win 64bit.
|
|
|
|
|
|
EcoChavCrypto
|
|
August 19, 2016, 01:17:02 PM |
|
I'm happy to say that all my masternodes & controller wallet is in sync with the block hash shown in the MN info page. http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.htmlMy wallet keeps crashing. I replaced my wallet.dat with an older one but it doesn't help.
Try resyncing from scratch with everything deleted except the 2 conf files & pre-PoS backed up wallet. (or with a chain backup taken at or before block 259200 using the pre-PoS or pre-2.1.1.0 wallet) I did this on all the masternodes & controller wallets that were crashing and none crashed since. FYI - My controller wallet's darknet.con content is as follows: (I have 94 connections right now) rpcuser=<user> rpcpassword=<pass> rpcallowip= 127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 enableobfuscate=0 addnode=coin-server.com I am just waiting for some nodes to be activated. What masternode information do I put into the controller wallet darknet.conf? You create a masternode.conf file in the same folder, and it looks like this: Masternode1 140.25.78.44:9999 masternodeprivkey transactionhash index1
Masternode1 146.328.8.22:9999 masternodeprivkey transactionhash index1
Masternode1 167.44.26.19:9999 masternodeprivkey transactionhash index1
You get the masternodeprivkey my typing "masternode genkey" in the console. You get the transactionhash by either entering your DNET MN address in a block explorer, or double clicking the transaction in the transaction tab You get the index number (0 or 1) by typing "masternode outputs" in the console. I get the masternode.conf, its the controller wallet darknet.conf I was wondering about. Should I remove masternode=1 and masternodeprivkey=  rpcuser=whatever rpcpassword=whatever rpcallowip=127.0.01 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 masternode=1 masternodeprivkey= Also do rpcuser= & rpcpassword= need to match up between the nodes and the controller wallet? |
|
|
|
|
borris123
|
|
August 19, 2016, 02:06:01 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
|
|
|
|
|
|
mxnsch
|
|
August 19, 2016, 02:09:25 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. |
██ ███ nope ██ ███
|
|
|
|
borris123
|
|
August 19, 2016, 02:20:38 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. so what is the workaround? was just told to use a wallet pre 2.0.1.0 version. will this get fixed in an update? |
|
|
|
|
|
StakeBox
|
|
August 19, 2016, 02:22:38 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. There is a bug that causes the client to lock up when running start-missing when you have a lot of masternodes. This has been there for a while now, it is not new to the post PoS wallets. It also rears its ugly head when using start-alias sometimes. I have found it seems to work to start just 2 or 3 masternodes with start-alias, wait a couple minutes, then repeat. It sucks, it takes a long time, we are aware of the problem and will work to get it fixed. It is not just the Windows wallet, it is all of them. For the time being we just have to grin and bear it, sorry. As far as the getting stuck on a block, or crashing out when staking it seems that everyone else has been able to eliminate that by using a wallet backup from before v2.1.0.0. If you don't have a backup from before that you can fire up the wallet, dump your private keys, and import them into a fresh wallet.dat. |
|
|
|
|
borris123
|
|
August 19, 2016, 02:29:07 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. There is a bug that causes the client to lock up when running start-missing when you have a lot of masternodes. This has been there for a while now, it is not new to the post PoS wallets. It also rears its ugly head when using start-alias sometimes. I have found it seems to work to start just 2 or 3 masternodes with start-alias, wait a couple minutes, then repeat. It sucks, it takes a long time, we are aware of the problem and will work to get it fixed. It is not just the Windows wallet, it is all of them. For the time being we just have to grin and bear it, sorry. As far as the getting stuck on a block, or crashing out when staking it seems that everyone else has been able to eliminate that by using a wallet backup from before v2.1.0.0. If you don't have a backup from before that you can fire up the wallet, dump your private keys, and import them into a fresh wallet.dat. my wallet is from may so well before that version. restarting seems to have caught it back up. |
|
|
|
|
4x13 (OP)
Legendary
Offline
Activity: 1078
Merit: 1011
|
|
August 19, 2016, 03:25:31 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. so what is the workaround? was just told to use a wallet pre 2.0.1.0 version. will this get fixed in an update? Here is a solid work around for the lagging issue in the console. walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter etc etc.. we are looking into this issue... EDIT: Make sure you have synced all the masternodes in your list before you start this, depending on the peers you have, this may take awhile after all the data has been synced. Check you masternode totals from the information tab against the Crowning stats page. You may not see all, but should see most (All depends on the peers you are connected to) |
|
|
|
|
|
cgt99
|
|
August 19, 2016, 04:20:05 PM |
|
Hi, my first time setting up masternode. I have followed the steps outlined in page 1.
When I run masternode start command, following error occurred:
Not capable masternode: Could not connect to 203.125.119.162:51472
My darknet.conf file contains:
rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
masternode=1
externalip=203.125.119.162
masternodeaddress=203.125.119.162
maxconnections=256
masternodeprivkey=xxxxx(my correct keys here)
Please assist/guide me. Thanks
Add port=51472 and try again |
|
|
|
|
Rumhurius
Legendary
Offline
Activity: 1672
Merit: 1046
Here we go again
|
|
August 19, 2016, 05:19:31 PM
Last edit: August 19, 2016, 05:30:00 PM by Rumhurius |
|
still keeps crashing on windows for me from time to time Synced from scratch before Blockdata got corrupted over this.  Problem signature:
Problem Event Name: APPCRASH
Application Name: darknet-qt.exe
Application Version: 2.1.2.0
Application Timestamp: 57b5515b
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.18233
Fault Module Timestamp: 56bb4ebb
Exception Code: c0000005
Exception Offset: 00000000000773e6
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9 |
|
|
|
|
mxnsch
|
|
August 19, 2016, 06:35:43 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. so what is the workaround? was just told to use a wallet pre 2.0.1.0 version. will this get fixed in an update? Here is a solid work around for the lagging issue in the console. walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter etc etc.. we are looking into this issue... EDIT: Make sure you have synced all the masternodes in your list before you start this, depending on the peers you have, this may take awhile after all the data has been synced. Check you masternode totals from the information tab against the Crowning stats page. You may not see all, but should see most (All depends on the peers you are connected to) Here is a solid, scripted workaround for the issue #!/bin/bash
# date: 20160819
# author: @marsmensch
# function: this script outputs a list of all configured masternodes with their alias
# this output can be used to start even big numbers of masternodes easily one-by-one
for MASTERNODE in $(darknet-cli masternode list-conf | awk -F":" '/masternode/{getline;gsub("\"",""); gsub(",",""); print $2 }')
do
echo "darknet-cli walletpassphrase <yourwalletpassphrase> 12000"
echo "darknet-cli masternode start-alias ${MASTERNODE}"
done
Example output: ....
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN6
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN7
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN8
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN9
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN10
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN11
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN12
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
....
|
██ ███ nope ██ ███
|
|
|
|
StakeBox
|
|
August 19, 2016, 06:46:22 PM |
|
still keeps crashing on windows for me from time to time Synced from scratch before Blockdata got corrupted over this. Problem signature:
Problem Event Name: APPCRASH
Application Name: darknet-qt.exe
Application Version: 2.1.2.0
Application Timestamp: 57b5515b
Fault Module Name: ntdll.dll
Fault Module Version: 6.3.9600.18233
Fault Module Timestamp: 56bb4ebb
Exception Code: c0000005
Exception Offset: 00000000000773e6
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: abcc
Additional Information 2: abcc8f7853b48d9807d6d51eb1fa5df9
Additional Information 3: abcc
Additional Information 4: abcc8f7853b48d9807d6d51eb1fa5df9 Are you using a backup of your wallet.dat that is from before v2.1.0.0? One that was made before that version, and was not used with the v2.1.0.0 wallet or the v2.1.1.0 wallet. I don't think there was any issues with the v2.1.0.0 wallet, but the v2.1.1.0 wallet corrupted wallet.dat files. If the wallet.dat was in place while using that wallet you will need to use another backup, or export your private keys and import them into a new wallet.dat. For those that seem to still be having the occasional crash, could you run the wallet for a bit with a completely new, clean wallet.dat and verify that it does not crash. I am unable to replicate the problem, so need some help from you guys to troubleshoot it. If you could shoot s3v3n a PM with an email address and get yourself a slack invite that would be great, thanks. |
|
|
|
|
Haunebu81
|
|
August 19, 2016, 06:49:49 PM |
|
Can windows wallet get fixed plz. It lags out then crashes when you start nodes one after other. Start missing instantly crashes. It is getting stuck at a block/crashing out when staking.
I have used a wallet from may. Resynced from scratch. It is the program.
It's not the program, its the new chain that your old wallet is not even aware of. I am also on Win 10 64bit. Besides that fact, it works for me and others. Sure, there are still issues. We have good workarounds for most. If you use an old wallet, your nodes are at risk of not working. so what is the workaround? was just told to use a wallet pre 2.0.1.0 version. will this get fixed in an update? Here is a solid work around for the lagging issue in the console. walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter walletpassphrase <yourwalletpassphrase> 12000 enter masternode start-alias <name of masternode> enter etc etc.. we are looking into this issue... EDIT: Make sure you have synced all the masternodes in your list before you start this, depending on the peers you have, this may take awhile after all the data has been synced. Check you masternode totals from the information tab against the Crowning stats page. You may not see all, but should see most (All depends on the peers you are connected to) Here is a solid, scripted workaround for the issue #!/bin/bash
# date: 20160819
# author: @marsmensch
# function: this script outputs a list of all configured masternodes with their alias
# this output can be used to start even big numbers of masternodes easily one-by-one
for MASTERNODE in $(darknet-cli masternode list-conf | awk -F":" '/masternode/{getline;gsub("\"",""); gsub(",",""); print $2 }')
do
echo "darknet-cli walletpassphrase <yourwalletpassphrase> 12000"
echo "darknet-cli masternode start-alias ${MASTERNODE}"
done
Example output: ....
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN6
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN7
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN8
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN9
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN10
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN11
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
darknet-cli masternode start-alias MN12
darknet-cli walletpassphrase <yourwalletpassphrase> 12000
....
Does this work in Windows too? Or just Linux? |
|
|
|
|
|
Haunebu81
|
|
August 19, 2016, 06:51:34 PM |
|
My problem with that script is that my wallet randomly crashes even when starting one MN at a time...
|
|
|
|
|
|
Poll
