v0.11.0 - Darkcoin Core Release
- Thread starter eduffield
- Start date
For start-many - are these the correct instructions (https://darkcointalk.org/threads/masternode-start-many-guide.2990/), od was there any update since?
Also - forum still says that latest version is 10.17.24 ...
Also - forum still says that latest version is 10.17.24 ...
Anybody is willing to answer? Only 100's denoms left in a wallet. What if I darksend few drk?
But I don't want to reveal any info. Simply I will have to mix them again.
So after shopping madness I will have to check coincontrol to see what size of denoms left
I've had 3 MNs just stop (daemon on server just quit, nothing odd in debug.log, no obvious signs in logs of RAM/CPU overuse) since updating to v11. They have all had to be restarted from the local wallet.
Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:
Yikes, that's really weird.Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:
Might just be bad luck. I left if for another hour and got a PTY 0.00 but it stayed stuck on 'Found unconfirmed... waiting...'
On Win 7, I had 1 conflict tx stuck at 39%(for 16 hrs).Had saved a wallet from the start of version 11.0.6 before mixing and did the standard copy and paste thing, re ran same version and everything tickety boo now.Local wallet got stuck after 7/8 rounds with two conflicting '!' txes, restarted with -zapwallettxes and now being hit with a string of charges and no DS progress:
I had the same problem on everything up to 0.11.0.4 - I skipped 0.11.0.5 - Have had this happen only one time since 0.11.0.6 and by pure coincidence, I was looking right at it when it happened. No output of any kind. I roll the command to execute like this in the same terminal so that any STDOUT or STDERR will hit the same screen session: ~/.darkcoin/darkcoind & tail -f ~/.darkcoin/debug.log - but nuthin'. No SEGFAULT, no stacktrace, just poof. The good news is that it is improved in it's occurrence by orders of magnitude in 0.11.0.6 - now over 40 nodes and it only happened once in 24 hours.
Evan suggested gdb to get some infos - this seems to stabilize them for some reason, and when using gdb, they won't freakin' crash anymore... I guess gdb is a workaround, lols. Doesn't get the info I'm looking for, but solves the crashing problem... [rolls eyes] It's like the problem knows I'm looking for it...
Can't offer anything on the DS issues... For the first time in months, I saw a successful denom. Not only that, but it denomed the whole stack in short order with no issues...
Just got a link to https://bitcointalk.org/index.php?topic=919373.0
According to deps-linux.yml we ARE building with Openssl-1.0.1k.
eduffield , shouldn't we temporarily use Openssl-1.0.1j ?
According to deps-linux.yml we ARE building with Openssl-1.0.1k.
eduffield , shouldn't we temporarily use Openssl-1.0.1j ?
Hi, first post here (but been into the dark for 8-9 months now).
Got a little bugreport:
Operating System: Windows 8.1 Home Ultimate 64bit
Issue: Random crashes in Wallet
Description: The wallet seems to randomly crash, the only thing I noticed during the last crash was that a block was created/found in the exactly same moment (was tailing logs).
Congrats to Dev team for a great release!
Got a little bugreport:
Operating System: Windows 8.1 Home Ultimate 64bit
Issue: Random crashes in Wallet
Description: The wallet seems to randomly crash, the only thing I noticed during the last crash was that a block was created/found in the exactly same moment (was tailing logs).
Congrats to Dev team for a great release!
Well, Darkcoil doesn't have DS (and masternode support iirc). Not sure where the optimizations lie.
Problem is with very small payments from P2Pool. I'm talking about 15 "dust" payments per day.
DS and MN should not cause it. These are incoming transactions.
Yeah, I hear you. You're left at the moment with either using with daemon to group and send dust and micro payments or Darkcoil.
flare , I just built v0.11.0.6 with OpenSSL 1.0.1j , all 3 operating systems built without problems and Win and Linux clients also run without problems.
So _if_ there should be a problem with OpenSSL 1.0.1k we can easily switch back.
Last edited by a moderator:
I found that this version of the wallet was completely unresponsive & locked up every time I went to do something with it on win7 64bit - unusable, so I went back to using darkcoil again.
I too use p2pool, so maybe this has something to do with it, but I also saw a post on bitcointalk from someone who couldn't use the daemon with p2pool at all - it wouldn't connect:
https://bitcointalk.org/index.php?topic=421615.msg10178011#msg10178011
Peace
I too use p2pool, so maybe this has something to do with it, but I also saw a post on bitcointalk from someone who couldn't use the daemon with p2pool at all - it wouldn't connect:
https://bitcointalk.org/index.php?topic=421615.msg10178011#msg10178011
Peace
Backup wallet and run once with -upgradewallet -zapwallettxesI found that this version of the wallet was completely unresponsive & locked up every time I went to do something with it on win7 64bit - unusable, so I went back to using darkcoil again.
I too use p2pool, so maybe this has something to do with it, but I also saw a post on bitcointalk from someone who couldn't use the daemon with p2pool at all - it wouldn't connect:
https://bitcointalk.org/index.php?topic=421615.msg10178011#msg10178011
Peace
I was thinking about this one : http://sourceforge.net/p/bitcoin/mailman/message/33221963/
...but if v0.11.0.6 already includes Bitcoins workaround-commit (didn't check) than you can just ignore my post...
Edit: I checked...forget my post
yeah it does, darkcoin is so freakin up-to-date since v11I was thinking about this one : http://sourceforge.net/p/bitcoin/mailman/message/33221963/
...but if v0.11.0.6 already includes Bitcoins workaround-commit (didn't check) than you can just ignore my post...
Edit: I checked...forget my post
I had the 64bit Linux client freeze on me once, which has never happened before. It's a fairly bare-bones Xubuntu installation with nothing else I've installed running.I found that this version of the wallet was completely unresponsive & locked up every time I went to do something with it on win7 64bit - unusable, so I went back to using darkcoil again.
I too use p2pool, so maybe this has something to do with it, but I also saw a post on bitcointalk from someone who couldn't use the daemon with p2pool at all - it wouldn't connect:
https://bitcointalk.org/index.php?topic=421615.msg10178011#msg10178011
Peace
Mixing seems to have hit a wall. I'm getting all sorts of funky messages above the Darksend mixing buttons. It would be great if it were possible to select the text and copy it, because it changes quite often. Some of the messages I have seen are:
Submitted to masternode, waiting in queue .
Darksend is idle.
Darksend request incomplete: transaction not valid. Will retry
Masternode: transaction not valid
Masternode: not compatible with existing transactions
Submitted to masternode, entries 2/3
Submitted to masternode, Waiting for more entries (2/3)..
... collateral not valid
Masternode: collateral not valid
I imagine that a lot of these have to do with the fact that only about 35% of Masternodes have updated to the latest version.
No, those are not "funky" messages.. lol... Those messages are letting you know what the mixing is doing.
What does collateral not valid mean? Is there some way I can make my collateral valid?
It's probably worth pointing out that since about 02:30 CET on my 'Transactions' tab I have four 'Payment to yourself' of -0.10 another one of -0.0001 and haven't had a 'Darksend Denominate' since then. The client hasn't been running the whole time but it has been running most of the time