- Jun 23, 2014
How were you able to shut it down with CTRL+C? As far as I'm aware, if you start darkcoind with the daemon flag, to shut it down properly, you would need to issue the command "Darkcoind stop"Yes, I shut down the daemon using CTRL+C, backed up the wallet and tried to kick it back on when I received the failed message. I guess this could be where the problem occurred.
My point was only that the way you present yourself matters. Given the tone and hysteria of the post (not to mention it was in the wrong forum) it had little chance of getting a pleasant response. And yes, in any community, there are large number in it for the money. To use this as a drawback is rather, like you always say, absurd.Did I blame the coin? I believe I was suggesting there perhaps is an issue in the bleeding edge version of the RC3 soft fork. I personally can't check the code so it is very difficult for me to determine the source of the problem. It is very clear to me many of you don't care about the code base at all and are only interested in making money.
No matter what you say next, you either running stable version and not RC, or your darkcoind.conf has masternode=0 instread of masternode=1, both a clear indication almost nothing you say makes sense.Also when I first loaded the new soft fork I did this:
./darkcoind masternode list
And got an empty hash
Just because I didn't run nodes on the test net does not mean I was not participating in other ways. Also first to report such a phenomena does not mean I'm the only one, the wallet could have been corrupting in other situations but no one reported it because they didn't lose coins.As long time supporter and being software dev, why on earth did you not join testnet, and ran a test on mainnet?
Not trying to pick a fight, truly! But you're not making sense. No testnet, dont agree with the absolutely logical and understandable closed-source, for a "massive loss" you dont even have private keys dumped, you didnt encrypt the wallet, c'mon!
You cannot stop the daemon with CTRL+C. Its "darkcoind stop".
You are the first and only to experience such phenomena.
Could please stop antagonizing an obvious community desperately trying to help you?
If you press <CTRL><C> on linux you send a request to kill the process. This can be intercepted by the process (darkcoin) to cleanly shutdown itself or ignored (you get a error message back)Yes, I shut down the daemon using CTRL+C, backed up the wallet and tried to kick it back on when I received the failed message. I guess this could be where the problem occurred.
A good idea would to make a backup of the swap partition/file, too. Hopefully one of the developers/experts is able to recover the private keys from mem/swap (if they are stored there).The darkcoin instance is definitely shut down by now, I have dd'd my mem in the hopes I might be able to find it in there but I can't think of anything else to do.
Based on this alone, I think it is now safe to say that the issue isn't from the Darkcoin daemon.I tried loading an older wallet file I was using for software I'm building with the new bitcoind. After closing it out and attempting to open it, it is now it is also corrupted in the same way. All zeroes and is the same file size as the one I sent 1k DRK too. Something very weird is going on, I have a working backup of that wallet file so something was lost, but it is very strange occurrence.
Have you checked "binary wallet compatibility" ?I tried loading an older wallet file I was using for software I'm building with the new bitcoind. After closing it out and attempting to open it, it is now it is also corrupted in the same way. All zeroes and is the same file size as the one I sent 1k DRK too. Something very weird is going on, I have a working backup of that wallet file so something was lost, but it is very strange occurrence.
Dependency Build Instructions: Ubuntu & Debian
sudo apt-get install build-essential
sudo apt-get install libssl-dev
for Ubuntu 12.04:
sudo apt-get install libboost-all-dev
db4.8 packages are available here.
Ubuntu precise has packages for libdb5.1-dev and libdb5.1++-dev, but using these will break binary wallet compatibility, and is not recommended.
for other Ubuntu & Debian:
sudo apt-get install libdb4.8-dev
sudo apt-get install libdb4.8++-dev
sudo apt-get install libboost1.37-dev
Yes, very important: Never ever mix clients built against different libdb versions (e.g. libdb-4.8 and libdb.5.1) - the db-format is incompatible, will break your wallet.dat and leave it corrupt.Have you checked "binary wallet compatibility" ?
libdb break compatibility.