Search results

Do walletpassphrase first, then the start-alias command, ie. "dash-cli walletpassphrase ********** 60" then "dash-cli masternode start-alias mn0". The 60 on the end is the number of seconds the wallet stays unlocked for, after that it goes back to locked. A warning, that will store a copy of the...

You could also mine on testnet if you just want to get a feel for the process and iirc @HashEngineering where asking for help with testing the next version of their Android wallet on testnet and where looking for miners as part of it.

Glad it's running :) You still need to move it to the extra drive? It should be possible to move the whole directory and edit a launcher to run "dash-qt -datadir=<dir on other drive>".

It sounds like a linking issue of some sort but I've no idea how that works on Windows, @bertlebbert may know? Last modified dates may tell you something, does it look like it's changing files in the old folder or the new one?

Had you tried deleting all the *.dat files (except wallet.dat ofc)? They're all safe to remove and it will cross them off the list but if mncache.dat wasn't the issue it may be something else entirely.

Delete mncache.dat, things where changed in it and it will rebuild it with the changes it's self. Should go on the reindexing after that, big job and it could take a few hours for it to get fully up to date.

Ah ok, you've got it fixed, Sorry, I thought you where still having problems with it :) EDIT: Tao's 12.1 update: https://www.dash.org/forum/threads/taos-masternode-setup-guide-for-dummies-updated.2680/#post-25672

You've changed YOURUSERNAME to the name of your home folder? It shouldn't be run as root and if it has you may need to change permissions on some files before it can be run as a normal user.

Not sure on the first, maybe spread it out over a few exchanges. Could try https://dashous.com/ too, maybe no-one on it is selling those kind of volumes but you never know. To the second, hypothetically the price would simply be unknown, it could be any value from zero to infinite. If you're...

It usually means Sentinel isn't running on the Masternode, update instructions here: https://dashpay.atlassian.net/wiki/display/DOC/Updating+to+12.1+-+Masternodes

Sentinel passed tests ok? EDIT: Special characters in rpcuser anr/or rpcpassword have also caused issues, alphanumeric only.

Nice one, I should've know you had it :) Bookmarked for future ref!

Yes, you can copy files over and it would be quicker but it's a fair bit of work from the terminal. There's also a bootstrap file somewhere to get most of the blockchain in a download but I'm not sure where.

Lol :) It might even have more free space than the newer server when it's done! Apt rocks, really powerful and well worth getting familiar with. When you have it on a desktop system going back to updating each bit of software individually is painful.

Yep, that's a lot of unused modules! Try running "apt-get autoremove", it may clean things up.

That's a bit strange, /lib will exist on both but 3.9G is an awful lot of difference. Have you tried "du -hd 1 /lib" yet? The only thing I can think of is you've update every kernel and /lib/modules is fit to burst with different versions! If it is then you can remove them using apt but it would...

It will run and it might run just fine for a long time but RAM mattered a lot during stress testing on testnet and if there are a lot of governance objects (proposals, votes, etc.) there's a good chance your MN will go down if under 1G and a couple of missed payments will wipe out anything saved...

You could try tracking it down, "du -hd 1 /" will check the root file system (-d 1 means down one level ie. just /var , not /var/log etc.), see which folder is significantly bigger and check that (ie. "du -hd 1 /home") but checking the root folder gives the hard drive a lot of work to do and...

The package manager (dpkg and apt) are taking up a lot of space, 1.4GB of cached files in there which is a lot! You can do "apt-get clean" to clear them all out and get that 1.4GB back. That much used space is normal because apt stores everything with the standard config, it's simple enough to...

Next run "sudo apt-get -f install", it will clean up whatever mess is in there and afterwards run "sudo apt-get purge" again, you may not need to but it wont do any harm. Seeing as you've added that user to the sudoers file (or you've logged in as root, if so you don't need the "sudo" part of...