What directory should wallet.dat be in. Ubuntu 16.04
it should be in /home/you/.dashcore
It's in there but seems to be picking up a different wallet
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 867. (Read 9723733 times)
February 06, 2017, 10:08:33 PM
What directory should wallet.dat be in. Ubuntu 16.04
it should be in /home/you/.dashcore
It's in there but seems to be picking up a different wallet
February 06, 2017, 09:44:50 PM
I'm wondering if my problems are in the masternode.conf file, or the local dash.conf perhaps. Anyone know where can i find info about how to configure masternode.conf (and dash.conf) on the local wallet ?
Thanks
Thanks
Have you tried this tutorial?
https://dashpay.atlassian.net/wiki/display/DOC/Updating+to+12.1+-+Masternodes
Or Tao has one starting from scratch?
February 06, 2017, 09:43:21 PM
I'm wondering if my problems are in the masternode.conf file, or the local dash.conf perhaps. Anyone know where can i find info about how to configure masternode.conf (and dash.conf) on the local wallet ?
Thanks
Thanks
local wallet only gets minimum, like RPCuser and RPCpass
Masternode.conf is where it's at for local (where the funds are) It's exactly like it was pre 12.1 and as the sample shows.
Name ipaddress:9999 mnprivatekey(shared_with_remote) tx#from_deposit_of_1000_dash Index# which can be seen in the block explorer next to hash
February 06, 2017, 09:37:03 PM
What directory should wallet.dat be in. Ubuntu 16.04
it should be in /home/you/.dashcore
February 06, 2017, 09:31:31 PM
https://i.imgur.com/wc5gcIt.png
Dash Unveils Largest Software Upgrade Since Inception
http://paymentweek.com/2017-2-6-dash-unveils-largest-software-upgrade-since-inception/
Dash Unveils Largest Software Upgrade Since Inception
http://paymentweek.com/2017-2-6-dash-unveils-largest-software-upgrade-since-inception/
What directory should wallet.dat be in. Ubuntu 16.04
February 06, 2017, 09:06:18 PM
Well, I'm pretty much ready for the upgrade, but concerned my disk space is too low. Is there an expectation of initial extra data needed? (I only have 10gb hard drive now on VPS running linux.)
I plan on upgrading or getting a different VPS soon but wasn't sure if I need to do that today, or if I have a week+ to do some research on my options.
Anyone have an idea based on testnet?
I plan on upgrading or getting a different VPS soon but wasn't sure if I need to do that today, or if I have a week+ to do some research on my options.
Anyone have an idea based on testnet?
https://dashpay.atlassian.net/wiki/display/DOC/Masternode+Update (Work in Progress)
For the people who are not willing to pay for the increasing costs of running a masternode, I suggest you to look into setting up a Pseudonode for DASH. I'm quite certain it'll be possible with minor tweaks based on this code: https://github.com/basil00/PseudoNode
February 06, 2017, 08:02:26 PM
Dash Unveils Largest Software Upgrade Since Inception
http://paymentweek.com/2017-2-6-dash-unveils-largest-software-upgrade-since-inception/
February 06, 2017, 07:52:35 PM
Have you started masternode from your local wallet via "masternode start-alias someAliasHere"?
Hi, thanks for your reply UdjinM6, I haven't reached the point of trying to start the masternode yet which is step 9 I think, I'm still stuck on step 7. There is some problem with sentinel connecting to the daemon or something it seems like.
Can I clarify has the port changed? It used to be 9999 and is now 9998 ? Do I need to reconfigure my firewall ?
@moocowmoo did a LOT of work to put this all together, no wonder if some steps are not quite polished yet
EDIT: same issue, same solution https://www.dash.org/forum/threads/version-12-1-release.12985/#post-113033
Appreciate the help guys, but I'm not there yet, will keep going tomorrow. From TaoOfSatoshi guide looks like i need port 9999 after the IP address in dash.conf which I've put back in. Now I'm trying to remote start the masternode using "masternode start-missing
Providing password in "masternode start-
Or unlock/lock it via menu like @stray suggested.
February 06, 2017, 07:36:46 PM
Have you started masternode from your local wallet via "masternode start-alias someAliasHere"?
Hi, thanks for your reply UdjinM6, I haven't reached the point of trying to start the masternode yet which is step 9 I think, I'm still stuck on step 7. There is some problem with sentinel connecting to the daemon or something it seems like.
Can I clarify has the port changed? It used to be 9999 and is now 9998 ? Do I need to reconfigure my firewall ?
@moocowmoo did a LOT of work to put this all together, no wonder if some steps are not quite polished yet
EDIT: same issue, same solution https://www.dash.org/forum/threads/version-12-1-release.12985/#post-113033
Appreciate the help guys, but I'm not there yet, will keep going tomorrow. From TaoOfSatoshi guide looks like i need port 9999 after the IP address in dash.conf which I've put back in. Now I'm trying to remote start the masternode using "masternode start-missing
I fixed that by manually unlocking my wallet first from the tools menu
February 06, 2017, 07:32:06 PM
I'm wondering if my problems are in the masternode.conf file, or the local dash.conf perhaps. Anyone know where can i find info about how to configure masternode.conf (and dash.conf) on the local wallet ?
Thanks
Thanks
February 06, 2017, 07:20:59 PM
Have you started masternode from your local wallet via "masternode start-alias someAliasHere"?
Hi, thanks for your reply UdjinM6, I haven't reached the point of trying to start the masternode yet which is step 9 I think, I'm still stuck on step 7. There is some problem with sentinel connecting to the daemon or something it seems like.
Can I clarify has the port changed? It used to be 9999 and is now 9998 ? Do I need to reconfigure my firewall ?
@moocowmoo did a LOT of work to put this all together, no wonder if some steps are not quite polished yet
EDIT: same issue, same solution https://www.dash.org/forum/threads/version-12-1-release.12985/#post-113033
Appreciate the help guys, but I'm not there yet, will keep going tomorrow. From TaoOfSatoshi guide looks like i need port 9999 after the IP address in dash.conf which I've put back in. Now I'm trying to remote start the masternode using "masternode start-missing
February 06, 2017, 06:48:13 PM
Have you started masternode from your local wallet via "masternode start-alias someAliasHere"?
Hi, thanks for your reply UdjinM6, I haven't reached the point of trying to start the masternode yet which is step 9 I think, I'm still stuck on step 7. There is some problem with sentinel connecting to the daemon or something it seems like.
Can I clarify has the port changed? It used to be 9999 and is now 9998 ? Do I need to reconfigure my firewall ?
@moocowmoo did a LOT of work to put this all together, no wonder if some steps are not quite polished yet
EDIT: same issue, same solution https://www.dash.org/forum/threads/version-12-1-release.12985/#post-113033
February 06, 2017, 06:42:13 PM
You changed your tone aSSBREAKER.
February 06, 2017, 06:23:10 PM
when will dash evolution roll out? 
December 2017
Will Dash be able to use IPv6 by then?
It seems ridiculous for Dash to fork Bitcoin and then load on so much extra crap that IPv6 functionality is broken forever.
Quote from: crowning
That's not good for the network's diffuse/diverse properties. Any attack that only works on IPv4 takes out 100& of all Masternodes instead of only most of them.
You're right! I think we should build our own mesh network because any attack that only works on the Internet will take out 100% of all nodes. Or even use some sort of quantum communications in case they'll come up with EM jamming.
I think Dash should be able to maintain the IPv4 and IPv6 connectivity it inherited from Bitcoin. Maybe even bolt on i2p when Monero is done with Kovri.
Altcoins are supposed to push the envelope, not regress. Do you want Dash to also abandon IPv4 and to back to SmallTalk, or perhaps ARPANET NCP?
Kicking 140 Masternodes off the network just because Evan broke IPv6 compatibility is asinine. That kind of hideous kludge solution might be OK for a testnet but not the real thing. Those Masternode owners collectively paid ~$16 million USD to put their money in a HYIP that is suddenly and arbitrarily being ordered by a centralized authority to function differently than as originally sold.
Why weren't Masternodes allowed to vote on whether or not to disable IPv6 and thereby kick 140 of their own off the network?
Is that how "distributed democracy by blockchain" is supposed to work?
What's the point of Dash's governance structure and voting when it's funding scams while Evan makes all the important decisions?
February 06, 2017, 05:59:12 PM
TAO'S MASTERNODE 12.1 UPDATE GUIDE FOR DUMMIES
https://www.dash.org/forum/threads/taos-masternode-setup-guide-for-dummies-updated.2680/#post-25672
Enjoy, Dash Nation!
Tao
https://www.dash.org/forum/threads/taos-masternode-setup-guide-for-dummies-updated.2680/#post-25672
Enjoy, Dash Nation!
Tao
February 06, 2017, 05:47:43 PM
Have you started masternode from your local wallet via "masternode start-alias someAliasHere"?
Hi, thanks for your reply UdjinM6, I haven't reached the point of trying to start the masternode yet which is step 9 I think, I'm still stuck on step 7. There is some problem with sentinel connecting to the daemon or something it seems like.
Can I clarify has the port changed? It used to be 9999 and is now 9998 ? Do I need to reconfigure my firewall ?
February 06, 2017, 05:35:24 PM
I've reached this point.
Even though it seems to have synced correctly. It says,
Anyone know what I have to do to fix that?
Quote
step 7) test sentinel has nothing to say
at this point, running
venv/bin/python bin/sentinel.py
should return nothing but silence. This is how you know it's working.
at this point, running
venv/bin/python bin/sentinel.py
should return nothing but silence. This is how you know it's working.
Even though it seems to have synced correctly. It says,
Quote
Invalid Masternode Status, cannot continue.
Anyone know what I have to do to fix that?
I'm still having this problem, some more info
when I run the command,
dash-cli masternode status
it says my protocol version is wrong
Quote
"status": "Not capable masternode: Invalid protocol version"
why would that be?
running the getinfo command tells me my protocol info as
Quote
"version": 120100,
"protocolversion": 70206,
"protocolversion": 70206,
If this is not the right place to get help can someone point me where I should look?
I thought I'd be able to crack this but obviously something has gone wrong somewhere
Have you started masternode from your local wallet via "masternode start-alias someAliasHere"?
February 06, 2017, 05:26:02 PM
I've reached this point.
Even though it seems to have synced correctly. It says,
Anyone know what I have to do to fix that?
Quote
step 7) test sentinel has nothing to say
at this point, running
venv/bin/python bin/sentinel.py
should return nothing but silence. This is how you know it's working.
at this point, running
venv/bin/python bin/sentinel.py
should return nothing but silence. This is how you know it's working.
Even though it seems to have synced correctly. It says,
Quote
Invalid Masternode Status, cannot continue.
Anyone know what I have to do to fix that?
I'm still having this problem, some more info
when I run the command,
dash-cli masternode status
it says my protocol version is wrong
Quote
"status": "Not capable masternode: Invalid protocol version"
why would that be?
running the getinfo command tells me my protocol info as
Quote
"version": 120100,
"protocolversion": 70206,
"protocolversion": 70206,
If this is not the right place to get help can someone point me where I should look?
I thought I'd be able to crack this but obviously something has gone wrong somewhere
February 06, 2017, 04:58:15 PM
12.1 Update Instructions
- Read Me -
Update instructions for General Users
https://dashpay.atlassian.net/wiki/x/sZAxBg
Update instructions for Masternode Operators
https://dashpay.atlassian.net/wiki/x/HJQ4Bg
https://i.imgur.com/2DAmJrg.png
- Read Me -
Update instructions for General Users
https://dashpay.atlassian.net/wiki/x/sZAxBg
Update instructions for Masternode Operators
https://dashpay.atlassian.net/wiki/x/HJQ4Bg
https://i.imgur.com/2DAmJrg.png
Superb instructions. Thanks!
My wallet didn't quite follow the script but things turned out fine (I think).
The script said:
step 6) launch the wallet, choose "YES" I want to rebuild the block index
12.1 uses a different indexing format so must walk the entire blockchain.
step 7) take a break, grab a sandwich, enjoy some sun
this can take anywhere from 3 to 4 hours depending on your machine
once complete, enjoy your new upgrades!
----
The button actually says "OK" not "YES" (hair-splitting), and in my case the wallet crashed almost immediately after that with one of those unhelpful Windows messages "an error has occurred" (and we know what it was but we won't tell you).
I restarted the wallet and it seemed to sync up fine on its own in only about half an hour! Balance and transactions look normal.
Very nice!
I have used the updated instructions and still get the same error in reading the mncache.dat file. I have deleted all the .dat files except the wallet.dat and I still get the error.
"Failed to load masternode cache from mncache.dat"
Thats what I did, I have deleted ALL the .dat files (except wallet.dat) and I still get the same error again and again.
"Failed to load masternode cache from mncache.dat"
Check you are not deleting them from the old .dash folder by accident, instead of the new .dashcore folder ?
Yes, I am sure:
https://i.imgur.com/6OnanWw.png
the DashCore folder contains the files as you can see above.
Then I get this:
https://i.imgur.com/SwTKayz.png
February 06, 2017, 04:28:27 PM
Are there any instructions for setting up Sentinel on a remote MN running Windows Server? Trying to update to v12.1, but I'm getting a WATCHDOG_EXPIRED status on my local wallet due to Sentinel not working on my remote MN. Only instructions I've seen so far are for Linux/Ubuntu systems.
thanks in advance.
thanks in advance.
Jump to: