borris123
|
|
August 18, 2016, 07:34:01 PM |
|
windows wallet getting annoying. it lags out then crashes. sometimes corrupts database
|
|
|
|
B1tUnl0ck3r
Sr. Member
Offline
Activity: 854
Merit: 277
liife threw a tempest at you? be a coconut !
|
|
August 18, 2016, 07:38:03 PM |
|
windows wallet getting annoying. it lags out then crashes. sometimes corrupts database
Hello borris123, you just have to use a wallet.dat pre 2.1.1.0. the last wallet update broke something in the wallet.dat. We all did it and it's working perfectly now.
|
When the people of the world will get that covid was intentionally released to frame china, steal the election from trump, assure massive bail outs and foster the forced vaccination agendas...they will forget, like 911, wmds in irak, uss liberty or pedogate.
|
|
|
Haunebu81
|
|
August 18, 2016, 07:49:42 PM |
|
The command " walletpassphrase "my pass phrase" 60" isn't working. I still have to enter my password each time I run the start-alias command. If I run start-missing, it locks up on me. Are there any other methods? I have 100 MN's here.
|
|
|
|
borris123
|
|
August 18, 2016, 07:56:41 PM |
|
The command " walletpassphrase "my pass phrase" 60" isn't working. I still have to enter my password each time I run the start-alias command. If I run start-missing, it locks up on me. Are there any other methods? I have 100 MN's here.
masternode start-alias mn1 YOURWALLETPASSWORD just keep pressing up and changing the name/number when doing militple nodes
|
|
|
|
Haunebu81
|
|
August 18, 2016, 08:22:45 PM |
|
The command " walletpassphrase "my pass phrase" 60" isn't working. I still have to enter my password each time I run the start-alias command. If I run start-missing, it locks up on me. Are there any other methods? I have 100 MN's here.
masternode start-alias mn1 YOURWALLETPASSWORD just keep pressing up and changing the name/number when doing militple nodes It worked fine for the first 9 masternodes. Now it's freezing at masternode start-alias master10 MYWALLETPASSWORD
|
|
|
|
Equalizer1970
|
|
August 18, 2016, 08:29:29 PM |
|
My wallet is now stuck on synchronizing sporks???
|
|
|
|
mxnsch
|
|
August 18, 2016, 08:47:48 PM |
|
Thought of the day ...
Masternode darknet.conf add :
reservebalance=10001
A friendly reminder. Having the switch behind us, a couple of masternode owners probably missed this valuable comment. @DEVs Please update the ANN post accordingly to avoid confused masternode owners
|
██ ███ nope ██ ███
|
|
|
borris123
|
|
August 18, 2016, 09:07:52 PM |
|
The command " walletpassphrase "my pass phrase" 60" isn't working. I still have to enter my password each time I run the start-alias command. If I run start-missing, it locks up on me. Are there any other methods? I have 100 MN's here.
masternode start-alias mn1 YOURWALLETPASSWORD just keep pressing up and changing the name/number when doing militple nodes It worked fine for the first 9 masternodes. Now it's freezing at masternode start-alias master10 MYWALLETPASSWORD Ye that's what I was saying in post above it crashes your wallet. The wallet lags out and doesn't enable then crashes. Don't think it's anything to do with wallet pre 2.1.0. Start-missing crashes it as well. But if you restart it some of them had enabled.
|
|
|
|
borris123
|
|
August 18, 2016, 09:08:21 PM |
|
Thought of the day ...
Masternode darknet.conf add :
reservebalance=10001
A friendly reminder. Having the switch behind us, a couple of masternode owners probably missed this valuable comment. @DEVs Please update the ANN post accordingly to avoid confused masternode owners what's that for?
|
|
|
|
StakeBox
|
|
August 18, 2016, 09:09:31 PM |
|
Thought of the day ...
Masternode darknet.conf add :
reservebalance=10001
A friendly reminder. Having the switch behind us, a couple of masternode owners probably missed this valuable comment. @DEVs Please update the ANN post accordingly to avoid confused masternode owners Not needed. If you have a Qt wallet as either a standalone masternode or controller wallet you can go into coin control and see that the input(s) for the masternode(s) is(are) locked.
|
|
|
|
StakeBox
|
|
August 18, 2016, 09:11:40 PM |
|
The command " walletpassphrase "my pass phrase" 60" isn't working. I still have to enter my password each time I run the start-alias command. If I run start-missing, it locks up on me. Are there any other methods? I have 100 MN's here.
masternode start-alias mn1 YOURWALLETPASSWORD just keep pressing up and changing the name/number when doing militple nodes It worked fine for the first 9 masternodes. Now it's freezing at masternode start-alias master10 MYWALLETPASSWORD Ye that's what I was saying in post above it crashes your wallet. The wallet lags out and doesn't enable then crashes. Don't think it's anything to do with wallet pre 2.1.0. Start-missing crashes it as well. But if you restart it some of them had enabled. Yeah, this has been an ongoing thing for a few versions. I have found it is best to start a few masternodes using start-alias, wait a bit, then start a few more, wait a bit, etc. We will look into it, we have had some higher priority things to work on lately.
|
|
|
|
mxnsch
|
|
August 18, 2016, 09:12:07 PM |
|
Thought of the day ...
Masternode darknet.conf add :
reservebalance=10001
A friendly reminder. Having the switch behind us, a couple of masternode owners probably missed this valuable comment. @DEVs Please update the ANN post accordingly to avoid confused masternode owners Not needed. If you have a Qt wallet as either a standalone masternode or controller wallet you can go into coin control and see that the input(s) for the masternode(s) is(are) locked. Nice, is that a new DNET specific feature? Never heard about that and i have installed hell a lot of masternodes
|
██ ███ nope ██ ███
|
|
|
StakeBox
|
|
August 18, 2016, 09:41:55 PM |
|
Thought of the day ...
Masternode darknet.conf add :
reservebalance=10001
A friendly reminder. Having the switch behind us, a couple of masternode owners probably missed this valuable comment. @DEVs Please update the ANN post accordingly to avoid confused masternode owners Not needed. If you have a Qt wallet as either a standalone masternode or controller wallet you can go into coin control and see that the input(s) for the masternode(s) is(are) locked. Nice, is that a new DNET specific feature? Never heard about that and i have installed hell a lot of masternodes While I would like to claim that bit as ours, we inherited it from Dash.
|
|
|
|
borris123
|
|
August 18, 2016, 09:46:00 PM |
|
The command " walletpassphrase "my pass phrase" 60" isn't working. I still have to enter my password each time I run the start-alias command. If I run start-missing, it locks up on me. Are there any other methods? I have 100 MN's here.
masternode start-alias mn1 YOURWALLETPASSWORD just keep pressing up and changing the name/number when doing militple nodes It worked fine for the first 9 masternodes. Now it's freezing at masternode start-alias master10 MYWALLETPASSWORD Ye that's what I was saying in post above it crashes your wallet. The wallet lags out and doesn't enable then crashes. Don't think it's anything to do with wallet pre 2.1.0. Start-missing crashes it as well. But if you restart it some of them had enabled. Yeah, this has been an ongoing thing for a few versions. I have found it is best to start a few masternodes using start-alias, wait a bit, then start a few more, wait a bit, etc. We will look into it, we have had some higher priority things to work on lately. ye fair do's. how about a google hangout with all the devs to discuss things? Blocktalk did an interview with the other coin I am invested into Nexus (defo worth a look if you not heard of it, in my sig) I found having a Q an A helped me better understand the direction it was heading. is it all steam ahead with the truly anonymous transactions now?
|
|
|
|
borris123
|
|
August 18, 2016, 10:14:32 PM Last edit: August 18, 2016, 11:01:32 PM by borris123 |
|
a few nodes stuck at 260598 a restart has fixed the problem tho.
sticking at 260709 in controller as well...looks like alot are stuck here =/
|
|
|
|
mikegi
|
|
August 18, 2016, 10:58:25 PM |
|
Ok...
A couple of my masternodes stuck at 260598,
Restarted and they are ok... "status" : "Masternode successfully started" without having to do anything on the controller. After restarting, the blockhash for 260598 changed to the hopefully correct one.
NOT stuck: darknet-cli getblockhash 260598 246a20ed8ceb48a6d7975a69993db5e4edee95470d9480e0f95673785e12a5e5
STUCK: $ darknet-cli getblockhash 260598 d0e84fd138bb89b3a8881dadd4f50baf78f992361e7715ea611235c41a6cdda0
darknet-cli getchaintips [ { "height" : 260709, "hash" : "a070dc031723cda052a3f4798c456324d6c9badddb1acb02525750697d46563d", "branchlen" : 0, "status" : "active" }, { "height" : 260598, "hash" : "d0e84fd138bb89b3a8881dadd4f50baf78f992361e7715ea611235c41a6cdda0", "branchlen" : 19, "status" : "valid-headers" }, { "height" : 260595, "hash" : "b33099e3006b92b48c60e7ca6e31eb04b2405733645245e67c6bf15e8649c0ba", "branchlen" : 1, "status" : "valid-fork" }, { "height" : 259901, "hash" : "2a83196b23e76314d50d8cdd11bb370db28a686dda852c3f9b9c9305e640255d", "branchlen" : 14, "status" : "valid-fork" }, { "height" : 259817, "hash" : "80649f7287034ff01382de577e2e4367a8dfde83b0e72d765e75a3183dc87b06", "branchlen" : 17, "status" : "valid-fork" }, { "height" : 259814, "hash" : "8602ff8f646378dfcfba163f8b428f82ddb5a42962d4b54270b323dca02f41a1", "branchlen" : 14, "status" : "headers-only" } ]
|
|
|
|
borris123
|
|
August 18, 2016, 11:02:31 PM |
|
Ok...
A couple of my masternodes stuck at 260598,
Restarted and they are ok... "status" : "Masternode successfully started" without having to do anything on the controller. After restarting, the blockhash for 260598 changed to the hopefully correct one.
NOT stuck: darknet-cli getblockhash 260598 246a20ed8ceb48a6d7975a69993db5e4edee95470d9480e0f95673785e12a5e5
STUCK: $ darknet-cli getblockhash 260598 d0e84fd138bb89b3a8881dadd4f50baf78f992361e7715ea611235c41a6cdda0
darknet-cli getchaintips [ { "height" : 260709, "hash" : "a070dc031723cda052a3f4798c456324d6c9badddb1acb02525750697d46563d", "branchlen" : 0, "status" : "active" }, { "height" : 260598, "hash" : "d0e84fd138bb89b3a8881dadd4f50baf78f992361e7715ea611235c41a6cdda0", "branchlen" : 19, "status" : "valid-headers" }, { "height" : 260595, "hash" : "b33099e3006b92b48c60e7ca6e31eb04b2405733645245e67c6bf15e8649c0ba", "branchlen" : 1, "status" : "valid-fork" }, { "height" : 259901, "hash" : "2a83196b23e76314d50d8cdd11bb370db28a686dda852c3f9b9c9305e640255d", "branchlen" : 14, "status" : "valid-fork" }, { "height" : 259817, "hash" : "80649f7287034ff01382de577e2e4367a8dfde83b0e72d765e75a3183dc87b06", "branchlen" : 17, "status" : "valid-fork" }, { "height" : 259814, "hash" : "8602ff8f646378dfcfba163f8b428f82ddb5a42962d4b54270b323dca02f41a1", "branchlen" : 14, "status" : "headers-only" } ]
restarting them fixes them abit but then gets stuck at 260709
|
|
|
|
borris123
|
|
August 18, 2016, 11:08:32 PM |
|
defo stuck at 260709
|
|
|
|
|
berron
|
|
August 18, 2016, 11:26:20 PM |
|
Same here. But due to the slow sync I have see something I think it's a bit weird. After being stucked at block260598 I have made the steps told by borris. Stop wallet, and restart wallet. As an impacient man, I have done a getinfo, and block showed was 260589, then it have reached 260709 and stuck. If you want PM a email and I will send you the screenshot. (Maybe this is normal, but for me that go back has been a bit surprising)
|
|
|
|
|