MEGA-"HELP! WALLET NOT SYNCING"-THREAD
- Thread starter chaeplin
- Start date
No, it's not required, AFAIK... but it sounds like he's running a much older version and is stuck on a bad fork. So if he's going to need to update, I think he should just update to x.11.5 and have the most recent version. The download page only offers x.11.5 now anyways. But x.11.4 should be fine, and it works fine for me here.
Hello. Darkcoin-qt for Windows connects fine to the Darkcoin network, but on Kubuntu 14.04 it does not. It just stays at 0 connections. I tried running it through a SOCKS Proxy but its the same.
This is what Terminal gives me:
This is what Terminal gives me:
The GUI starts up fine.Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
Please put this in our bugtracker at https://github.com/darkcoinproject/darkcoin/issues and we will have a look at this. Thanks!
Done. I didn't know where to report this, so I posted this here. I think the thread can be closed now.
Hopefully it will be solved soon.
Hopefully it will be solved soon.
thought i have solved this problem, but my darkcoin wallet-qt still not in sync, 12hrs behind now.
i had just downloaded the latest qt version.
tried sending 1drk to cryptsy account, qt shows 0 confirmations and had deducted 1 drk.
how to resolve this?
i had just downloaded the latest qt version.
tried sending 1drk to cryptsy account, qt shows 0 confirmations and had deducted 1 drk.
how to resolve this?
I am currently preparing release of v0.9.11.6/0.10.11.6 which fixes this issue, ETA later this day.
If someone wants to join the test of bugfix release 0.9.11.6 --> https://darkcointalk.org/threads/testing-bugfix-release-0-9-11-6.1743/
I tested Kubuntu 14.04 against newest version 0.9.11.6 and it resolves the connection problem for me (see https://github.com/darkcoinproject/darkcoin/issues/20)
Could you retest please --> https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.9.11.6-linux.tar.gz
"No active connections to Darkcoin networks," is the message.
Funnily enough, I withdrew some Darkcoins from my Criptsy account to my wallet but given its being "5 hours behind" and not able to synchronize I wonder how long it would take to get to normalcy?
Or is something messed up on my end that I am not aware of?
Funnily enough, I withdrew some Darkcoins from my Criptsy account to my wallet but given its being "5 hours behind" and not able to synchronize I wonder how long it would take to get to normalcy?
Or is something messed up on my end that I am not aware of?
I'm setting up Darkcoin for the first time and having problems with syncing
I'm using newest darkcoin-qt (v0.11.1.25-68f81bb-beta)
, Arch Linux x86_64, tried both the linux binary and compiling it myself, same results. It gets stuck at 2 weeks left. I've blown away my whole .darkcoin profile folder several times and started over. Also tried -reindex, makesno difference. One time it stuck at five weeks instead of two weeks but it was the same behavior.
From the log file, everything before what I pasted below is fine, just a bunch of ACCEPTED. When it fails, CPU usage goes up much higher for a minute, then goes down to almost nothing
Then it just continues on forever like the last few lines, "Got mismatched pubkey and vin" and "Misbehaving... ban threshhold exceeded" etc, with a few other things sprinkled in here and there like "no route to host"
Edit: Now it's doing something different, seems to be processing some blocks but also getting message "Chain state database corruption likely.". I'll let it go for awhile and see what happens
Edit2: It still isn't working right. Wondering if it's the openssl version I have? OpenSSL 1.0.2 22 Jan 2015
There aren't any other versions of openssl available for Arch Linux (no compat version available), and if I manually compile another version and install it I just ended up breaking half of my system including pacman, and had to manually download, extract, and copy the official 1.0.2 back into place. Wondering if Arch Linux isn't the best idea for this? I dont even know if openssl is the problem though.
I'm using newest darkcoin-qt (v0.11.1.25-68f81bb-beta)
, Arch Linux x86_64, tried both the linux binary and compiling it myself, same results. It gets stuck at 2 weeks left. I've blown away my whole .darkcoin profile folder several times and started over. Also tried -reindex, makesno difference. One time it stuck at five weeks instead of two weeks but it was the same behavior.
From the log file, everything before what I pasted below is fine, just a bunch of ACCEPTED. When it fails, CPU usage goes up much higher for a minute, then goes down to almost nothing
Code:
2015-03-08 20:27:16 CheckBlock() : Skipping masternode payment check - nHeight 220803 Hash 00000000000f372e67fd66e61e71c7177d59b62b11e3fc2bd77e9c723c72374d
2015-03-08 20:27:16 ProcessBlock: ACCEPTED
2015-03-08 20:27:22 dseep - Asking source node for missing entry CTxIn(COutPoint(c4c1ac2389ad8ab911fd25c95608fb95f5567dad82cead39cc3a4ddf805635f5, 0), scriptSig=)
2015-03-08 20:27:22 dseep - Asking source node for missing entry CTxIn(COutPoint(f958e84664343b76edcc6db9a16ccfa28681cbe5cfbf7ed757b64bca7ed030db, 0), scriptSig=)
2015-03-08 20:27:22 dseep - Asking source node for missing entry CTxIn(COutPoint(d7fe6294825bc3dee5193f282b748fec64480c6fb37571edd3198c5474bde22e, 1), scriptSig=)
2015-03-08 20:27:23 dseep - Asking source node for missing entry CTxIn(COutPoint(140cce837d46e3cffd7c702fb9d81ca23739117f6aa54995c1f91311641d03c9, 1), scriptSig=)
2015-03-08 20:27:23 dseep - Asking source node for missing entry CTxIn(COutPoint(be92dd717a12b251d273ae3ca5c9c43575f32c7fea86244f12109fa841a59b50, 0), scriptSig=)
2015-03-08 20:27:23 dseep - Asking source node for missing entry CTxIn(COutPoint(fcc1859380f5cf92097d7bf15183d900f2da738a34f0cbba31796019ea7a1908, 1), scriptSig=)
2015-03-08 20:27:23 dseep - Asking source node for missing entry CTxIn(COutPoint(522249632aa582c11fd0ca4514e25ade307bf7054550b213428cced8225cba2d, 0), scriptSig=)
2015-03-08 20:27:24 dseep - Asking source node for missing entry CTxIn(COutPoint(d38c26c46d94d70645919bfb8bac7e9058e909dc6d0d96dad22211de4d8167b9, 0), scriptSig=)
2015-03-08 20:27:24 mnw - winner out of range CTxIn(COutPoint(0ebe82f1d21e67f69e8efcea148cd7d921cc1d34620d5423b7778d54e91c2341, 1), scriptSig=) Height 232256 bestHeight 220802
2015-03-08 20:27:25 dseep - Asking source node for missing entry CTxIn(COutPoint(e0b1bfd6d19781ede5a346b7ae134226af18525bc6d5b0ce3d8c27bba90df9dc, 0), scriptSig=)
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 Successfully synced, asking for Masternode list and payment list
2015-03-08 20:27:25 dseep - Asking source node for missing entry CTxIn(COutPoint(c82a539470ed6b103e9ed7f67c2fcb046665dae0354e2c0205e96f331aec8b58, 1), scriptSig=)
2015-03-08 20:27:25 dsee - Got mismatched pubkey and vin
2015-03-08 20:27:25 Misbehaving: 155.94.167.223:9999 (0 -> 100) BAN THRESHOLD EXCEEDEDEdit: Now it's doing something different, seems to be processing some blocks but also getting message "Chain state database corruption likely.". I'll let it go for awhile and see what happens
Edit2: It still isn't working right. Wondering if it's the openssl version I have? OpenSSL 1.0.2 22 Jan 2015
There aren't any other versions of openssl available for Arch Linux (no compat version available), and if I manually compile another version and install it I just ended up breaking half of my system including pacman, and had to manually download, extract, and copy the official 1.0.2 back into place. Wondering if Arch Linux isn't the best idea for this? I dont even know if openssl is the problem though.
Last edited by a moderator:
Here's a video how to install DRK wallet in Linux:
Also, to help your wallet sync faster, you can get the bootstrap from here:
https://github.com/UdjinM6/darkcoin-bootstrap
Ok, I've just downloaded Dash wallet (so it should be the latest version) but my wallet doesn't sync up - it stays at 11 hour(s) behind. Since most responses in this topic are for Linux users, can anyone tell me (windows 7, 64bit user) what to do?
Try to restart it once, we have no forks now afaik so it should "heal" itself in most cases without any additional effort from you.
If that doesn't help: got to Tools -> Show Automatic Backups - > (explorer should open a folder for you) -> go one folder up. Now close your wallet, remove peers.dat from that folder and start wallet again.
These are the most common ways to solve "stuck" problem (when network has no forks). Feel free to ask for more help if you still have issues after that.
Smart way to show him how to find his Dash folder, Udjin, instead of telling him how to find the 'roaming' path...
Kudos to crowning for a great ToolSmart way to show him how to find his Dash folder, Udjin, instead of telling him how to find the 'roaming' path...
Thank you for your help. After I removed peers.dat file, my wallet crashes right after I turn it on and when a message "Warning: Please check that your computer's date and time are correct! If your clock is wrong Dash will not work properly." appears. I tried restarting the PC and even tried placing the peers.dat file back to its original place - the program keeps crashing after the mentioned message.
That's weird :what:Thank you for your help. After I removed peers.dat file, my wallet crashes right after I turn it on and when a message "Warning: Please check that your computer's date and time are correct! If your clock is wrong Dash will not work properly." appears. I tried restarting the PC and even tried placing the peers.dat file back to its original place - the program keeps crashing after the mentioned message.
Well, make sure your date/time is set correctly actually (check your windows settings). If it is ok and you still have this issue - grab debug.log from the same folder, zip it and send it to me pls, I'll have a look [email protected]
Hmm, seems like time was actually the problem here. Since I don't like PC automatically messing up my clock when the daylight saving happens twice a year, I always turn off this option. So I had to turn this option on and let it update the time. Now the wallet is up to date. Thank you for your prompt response and help
Hi
My wallet doesn't sync anymore (it is 8 weeks late). I run Ubuntu 15.04 and a fresh compiled qt wallet (neither 0.12.0.0 nor 0.11.2.23 release works).
It says there are some active connections to dash network, but even after a few hours doesn't sync. I've tried to delete ~/.config/Dash/ and ~/.dash/peers.dat but the problem's still here.
What can I do, please ?
My wallet doesn't sync anymore (it is 8 weeks late). I run Ubuntu 15.04 and a fresh compiled qt wallet (neither 0.12.0.0 nor 0.11.2.23 release works).
It says there are some active connections to dash network, but even after a few hours doesn't sync. I've tried to delete ~/.config/Dash/ and ~/.dash/peers.dat but the problem's still here.
What can I do, please ?
I'm having a problem with my QT wallet synchronizing after the superblock yesterday.
When I checked it this morning, there were no error messages, but it was stuck on block 448631 (the one right before the superblock). So first I just restarted the wallet - no luck, just stuck on that block still and says "Synchronizing with network..." Next I upgraded to the latest version because I realized my version was a bit old. Still stuck. Then I downloaded today's bootstrap.dat. When it started up, it gave the message of importing from disk, renamed bootstrap.dat to bootstrap.dat.old, then switched to "Synchronizing with network..." but it is still stuck on block 448631!
The debug.log has this at the end of the bootstrap.dat import:
Does anyone have any ideas of what is going on?
When I checked it this morning, there were no error messages, but it was stuck on block 448631 (the one right before the superblock). So first I just restarted the wallet - no luck, just stuck on that block still and says "Synchronizing with network..." Next I upgraded to the latest version because I realized my version was a bit old. Still stuck. Then I downloaded today's bootstrap.dat. When it started up, it gave the message of importing from disk, renamed bootstrap.dat to bootstrap.dat.old, then switched to "Synchronizing with network..." but it is still stuck on block 448631!
The debug.log has this at the end of the bootstrap.dat import:
And at the bottom of debug.log is a bunch of repeated messages like this:
which appears to be the head for the superblock.
Does anyone have any ideas of what is going on?
try "reconsiderblock 0000000000122ce86bf9b563507a22e828746e2d70f19e3703518526a42c258f"