MEGA-"HELP! WALLET NOT SYNCING"-THREAD

Brian

New Member
May 16, 2014
2
0
1
Ive tried all the above option from deleting the darkcoin folder contents except the wallet the wallet.dat file, un-installed it, re-installed it, copying and pasting the above peer.dat file, waited 20 mins for sync to start, looking for other dark wallets...all my other 10 wallets work fine lite,bit...etc... im trying to get into dark before its too late....PLEASE help




This link has latest wallet url.
https://darkcointalk.org/threads/postponing-masternode-payments-till-may-25th.578/



first update, start wallet, wait simply 10mins.

Then if you still have problem.
Replace peers.dat with http://drk.poolhash.org/files/peers.dat
(first stop wallet, then replace)


And check firewall, if outbound port 9999 is blocked.

How to check ?

using browser, open http://portquiz.net:9999/
If you can see following message, it's ok.
Code:
Outgoing port tester

This server listens on all TCP ports, allowing you to test any outbound TCP port.
You have reached this page on port 9999.
Your network allows you to use this port. (Assuming that your network is not doing advanced traffic filtering.)
Network service: unknown
Your outgoing IP: ~~~
 

realart

New Member
May 15, 2014
8
0
1
Wallet doesn't work.... blah blah blah...

I am sick of it.

Downloaded latest windows binary? Check.
Deleted all files in DarkCoin older? Check.
Got active connections? Check.
Waited 10 minutes? Waited 10 hours. Check.
Tried deleting peers.dat? Check. Got 0 connections now.
Downloaded some new peers collection? No? From where?

I have two questions and one suggestion:
1.) How do I get the wallet to sync so I can transfer my coins to MintPal and get rid of them before they cost 0.01 cents a piece?
2.) How is anyone supposed to be able to use Darkcoin wallet if it only (supposedly) works after you do a list of manual file copy-pasting / deleting and other elaborate manual operations that nobody can possibly know about unless reading the forum, and some can't and won't be bothered to do at all? What exactly do you have to do to be able to use Darkcoin wallet? Downloading and running the binary clearly isn't enough.
3.) I suggest to remove the sentence "It's fast, secure and easy" from https://www.darkcoin.io/getstarted.html, because it's not fast, not secure (I will be terrified when I'll attempt to send out of my wallet, I ever get it to sync), and it damn sure isn't easy. The word "impossible" comes to mind as a replacement.

:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad:
 

realart

New Member
May 15, 2014
8
0
1
The new peers.dat should come with the new wallet when you download it, there is no reason to download a separate peers.dat file for the hard fork that happened yesterday
Nothing comes with windows wallet. No peers.dat, no config file and no instructions that you need them and how to get them.

End user usability is zero. You download an exe file and it just doesn't work.
 

BostonStrong617

New Member
May 20, 2014
32
4
8
My wallet has been out of sync for days and the hours behind only seems to get longer.

I've never closed the dark wallet. It's always running/on.

Also, I haven't received any Drk Coins from my pool, ever. I seems to reset back to zero coins on my transaction page and then I have to start over again, but I'm never sent a coin.

Any ideas?
 

Attachments

karloz34

New Member
May 24, 2014
28
1
3
It seems like the total DRK are below of the minimum payout for most pools.

You could try re-indexing your DRK wallet, just make a .bat file containing "darkcoin-qt -reindex", without the quotes.
 

BostonStrong617

New Member
May 20, 2014
32
4
8
It seems like the total DRK are below of the minimum payout for most pools.

You could try re-indexing your DRK wallet, just make a .bat file containing "darkcoin-qt -reindex", without the quotes.
Thanks. I re-indexed and now the sync is stuck at 24 hours behind.

Also, my total dark has went all the way up to 1 DRK several times since I started that pool then it goes back to zero.
I have the pool set to cash me out after every 1 DRK but I'm not receiving the coins, even though I set my receive address.
 

realart

New Member
May 15, 2014
8
0
1
The mystery deepens.
Tried the same 9.4.11 client on my Windows XP machine on the same network, and it works pretty much instantly!

It didn't on my Windows 7 32 and Ubuntu system, also on the same network, with no firewall and DMZ (no filtering) on the router.

I got these errors in debug.log:

Code:
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (52 -> 53)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (53 -> 54)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (54 -> 55)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (55 -> 56)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (56 -> 57)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (57 -> 58)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (58 -> 59)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (59 -> 60)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (60 -> 61)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (61 -> 62)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (62 -> 63)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (63 -> 64)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (64 -> 65)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (65 -> 66)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (66 -> 67)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (67 -> 68)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (68 -> 69)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (69 -> 70)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:40 Misbehaving: 23.23.186.131:9999 (70 -> 71)
2014-05-29 11:36:40 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:45 Misbehaving: 23.23.186.131:9999 (71 -> 72)
2014-05-29 11:36:45 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:45 Misbehaving: 23.23.186.131:9999 (72 -> 73)
2014-05-29 11:36:45 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:45 Misbehaving: 23.23.186.131:9999 (73 -> 74)
2014-05-29 11:36:45 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (74 -> 75)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (75 -> 76)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (76 -> 77)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (77 -> 78)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (78 -> 79)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (79 -> 80)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (80 -> 81)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:46 Misbehaving: 23.23.186.131:9999 (81 -> 82)
2014-05-29 11:36:46 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (82 -> 83)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (83 -> 84)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (84 -> 85)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (85 -> 86)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (86 -> 87)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (87 -> 88)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (88 -> 89)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (89 -> 90)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:47 Misbehaving: 23.23.186.131:9999 (90 -> 91)
2014-05-29 11:36:47 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:50 Misbehaving: 23.23.186.131:9999 (91 -> 92)
2014-05-29 11:36:50 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:51 Misbehaving: 23.23.186.131:9999 (92 -> 93)
2014-05-29 11:36:51 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:51 Misbehaving: 23.23.186.131:9999 (93 -> 94)
2014-05-29 11:36:51 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:51 Misbehaving: 23.23.186.131:9999 (94 -> 95)
2014-05-29 11:36:51 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:56 Misbehaving: 23.23.186.131:9999 (95 -> 96)
2014-05-29 11:36:56 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:56 Misbehaving: 23.23.186.131:9999 (96 -> 97)
2014-05-29 11:36:56 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:57 Misbehaving: 23.23.186.131:9999 (97 -> 98)
2014-05-29 11:36:57 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:57 Misbehaving: 23.23.186.131:9999 (98 -> 99)
2014-05-29 11:36:57 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:36:57 Misbehaving: 23.23.186.131:9999 (99 -> 100) DISCONNECTING
2014-05-29 11:36:57 disconnecting node 23.23.186.131
2014-05-29 11:36:57 ProcessMessage(dsee, 241 bytes) FAILED
2014-05-29 11:39:31 accepted connection 188.194.12.64:39803
2014-05-29 11:39:31 ProcessMessages(version, 103 bytes) : CHECKSUM ERROR nChecksum=e72d7961 hdr.nChecksum=f51e8d93
 

semp

New Member
May 30, 2014
5
0
1
Hello everyone. I started looking into mining about a week ago. I've done plenty of reading but still havent quite cleared up a few things. At first I didnt realise that I'd been using the older version of the wallet. After a day or two it stopped syncing with the network, so I updated. It worked for a bit but now I'm getting the error in the screenshot below.
Any idea's?
 

Attachments

Last edited by a moderator:

semp

New Member
May 30, 2014
5
0
1
At first I used the default pool that the simple CPU miner program was pointed at. I mined for 48 hours or so with no obvious results (and no yay's) so I pointed it at elitter.net instead. Since then I've seen a few yay's. Does all the mining work add up culmulatively and turn into darkcoin or do only the yay's count?
 

eltito

Active Member
Apr 21, 2014
157
185
103
Hey All
we are a new team at Facebook/Darkcoin !
Please 'like' the page to get our numbers up
and the word out !!
Tx
https://www.facebook.com/Darkcoin
Please note: This is no longer the official Darkcoin Facebook page.

It's a long story - suffice it to say that the person who controls this page has been...less than cooperative.

The official Darkcoin Facebook page is here: https://www.facebook.com/DarkcoinOfficial

I realize that darkcoin.io still points to the old address. We are working on getting that remedied.
 

semp

New Member
May 30, 2014
5
0
1
Thanks to whoever merged my posts into this thread. I updated the peers.dat file and used -reindex and now I'm synced. A bit surprised that there are no (even tiny fractions of) drk in my wallet after around 72 hours solid mining over the last week but Im probably averaging 40 kh/s and after looking around that doesnt seem very much.
 

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
Thanks to whoever merged my posts into this thread. I updated the peers.dat file and used -reindex and now I'm synced. A bit surprised that there are no (even tiny fractions of) drk in my wallet after around 72 hours solid mining over the last week but Im probably averaging 40 kh/s and after looking around that doesnt seem very much.
Your welcome.

Which pool are you mining at? elitter.net looks like a litecoin p2pool node.
And yes, only "yay!" counts.
 
  • Like
Reactions: semp

semp

New Member
May 30, 2014
5
0
1
Thanks. I was tampering with stuff like this yesterday thanks to a post I read by tomfoolery and got interesting results. Generally about 30% lower average kh/s but lots more yay's. The plan was to look into it more today. So thats modifying the difficulty? I have a rough idea of whats going on but not totally clear on the specifics yet :)
 

ElectricSavant

New Member
Jun 3, 2014
3
0
1
Please help!
stuck on 75222 of 75327 with 20 connections(5-days behind). Restarted several times (v0.9.4.11-unk-beta).

ElectricSavant™
 

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
Anyone else is stuck at 81208? A transaction to my wallet hasn't cleared for more than 20 minutes now. It shows in 'unconfirmed' but zero confirmations (0/unconfirmed). Please advise.

EDIT: False alarm! It works just fine now.
 
Last edited by a moderator:

timk225

New Member
May 15, 2014
7
0
1
I had the 10.7.3 wallet and now I have the 10.8.11 version. The damn thing has been running for two days and has even been restarted once or twice but it stays stuck on 11 days to go, and once it got to 5 and stayed there most of the day.

What the hell?
 

Kai

Member
Apr 6, 2014
110
56
78
Of course, there was a hard fork weeks ago. Delete everything in the Darkcoin folder except wallet.dat, then run the wallet.
 
  • Like
Reactions: Light

george9178

New Member
May 22, 2014
15
0
1
This link has latest wallet url.
https://darkcointalk.org/threads/postponing-masternode-payments-till-may-25th.578/



first update, start wallet, wait simply 10mins.

Then if you still have problem.
Replace peers.dat with http://drk.poolhash.org/files/peers.dat
(first stop wallet, then replace)


And check firewall, if outbound port 9999 is blocked.

How to check ?

using browser, open http://portquiz.net:9999/
If you can see following message, it's ok.
Code:
Outgoing port tester

This server listens on all TCP ports, allowing you to test any outbound TCP port.
You have reached this page on port 9999.
Your network allows you to use this port. (Assuming that your network is not doing advanced traffic filtering.)
Network service: unknown
Your outgoing IP: ~~~
I still have a problem with sync.When I open the wallet,it can connect the network,it can download 500 blocks,then stop.But it still connect the network,just can't download the blocks.So I turn it off.When I restart the wallet,it can also download another 500 blocks,then stop again.So what's the problem?
1.I have download the latest wallet.My version is 9.10.0.
2.
I have wait 10 mins.
3.I have replace the new peers.dat
4.my port 9999 is open.
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
I still have a problem with sync.When I open the wallet,it can connect the network,it can download 500 blocks,then stop.But it still connect the network,just can't download the blocks.So I turn it off.When I restart the wallet,it can also download another 500 blocks,then stop again.So what's the problem?
1.I have download the latest wallet.My version is 9.10.0.
2.
I have wait 10 mins.
3.I have replace the new peers.dat
4.my port 9999 is open.
Give your wallet more time.
"it can download 500 blocks" means it connected to networks, but need more peer.
use getinfo to check number of connected peers.
 

george9178

New Member
May 22, 2014
15
0
1
Give your wallet more time.
"it can download 500 blocks" means it connected to networks, but need more peer.
use getinfo to check number of connected peers.
How to use getinfo to check number of connected peers?
I have been wait for 40 mins.
The old wallet don't have this problem.
I updata the wallet to 0.9.10.Then the problem come.
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
How to use getinfo to check number of connected peers?
I have been wait for 40 mins.
The old wallet don't have this problem.
I updata the wallet to 0.9.10.Then the problem come.
What is your os ?
 
Last edited by a moderator:
  • Like
Reactions: george9178

Cointopay.com

New Member
May 31, 2014
21
6
3
Exactly the reason why we started Cointopay, the desktop wallet suck! The protocol and technology behind it is great, but the desktop user experience sucks big time, especially when you have multiple alt coin wallets.
 

DRKLord

Member
Jun 2, 2014
92
94
68
Louisiana
This should be easy enough to fix... it sounds like you didn't update your Darkcoin client and now you've lost sync with the network and can't catch up. You're probably also running on a bad fork of the block chain. This would explain why you never see coins appear in your wallet or receive transactions from your mining pool payouts.

First thing you need to do is ensure you're running the latest version of Darkcoin-qt. You can check which version you're running by going to the top menu-bar in your client window and clicking Help >> About Darkcoin. This will bring up the "About Box" for your Darkcoin-qt client. The very first thing you should see in this window is your client version number. Mine says this:

DarkCoin version v0.10.11.4-unk-beta

If you're running anything other than v0.9.11.5 or v0.10.11.5 then your Darkcoin client is out-of-date and you need to download the new client version from the official Darkcoin website (www.darkcoin.io). You can see my thread here about updating your client and download the correct version directly from my download links.

Once you've made sure you've got the correct client version, let's fix your problem. The problem is most likely, as I said, that your client is running on a "bad fork" of the Darkcoin block chain. This means that your local copy of the block-chain on your PC is probably corrupted/invalid. To fix this, we're going to totally wipe the slate clean and re-sync with the network. Please follow these steps:

1) Navigate to your Darkcoin data directory. By default (for Windows) this directory can be found in your AppData folder in the Roaming directory. On my PC, for example, the path is as follows:
C:\Users\DRKLord\AppData\Roaming\DarkCoin

You can easily find your directory by opening a fresh Windows Explorer window and typing this into the address bar and pressing the Enter key:
%AppData%\Darkcoin
2) Now that you've found your Darkcoin data directory, let's make a back-up copy of it just to be on the safe side. Copy either the entire AppData\Darkcoin folder or copy everything inside of it and paste it to a safe and easily accessible location in your file system. For example, make a new folder on your Desktop named "Darkcoin Data Backup" and paste the copy there for safe-keeping.

NOTE: It's also a good idea, at this point, to make an extra back-up of your wallet file. Copy your wallet.dat file (found in your data directory) onto a spare USB flash drive and save another copy in a safe place on your hard-drive where you can find it in the future if you ever need it.
3) Now that we've got a back-up of our entire data directory and your wallet file, proceed by deleting all of the contents of your AppData\Darkcoin directory except for the wallet.dat file. Yes, everything, except your wallet.

4) After deleting all of the contents of the data directory, leaving only the wallet.dat file, you should now launch your Darkcoin-qt client.

5) Your client should launch, connect to the network and begin the process of downloading the correct version of the blockchain and resynchronizing with the rest of the network. This may take several hours or more, so be patient.

6) Once you've done all of this, report back here and let me know how it went! :)

Good luck!

The DRK Lord