|
wr104 (OP)
|
 |
June 24, 2015, 03:22:11 AM |
|
Yes,it's me.But I haven't received my coins.What should I do next? Thanks. On the destination wallet, confirm that the receiving address is K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 Then, check that the current block is at least 89848 My address is K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. My latest block is #89852. Ok, open the debug.log and search for height=89815 2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526 Do you see any AddToWallet message before or after that line? |
|
|
|
|
cryptoVIP
Member
 Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 03:25:51 AM |
|
Yes,it's me.But I haven't received my coins.What should I do next? Thanks. On the destination wallet, confirm that the receiving address is K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 Then, check that the current block is at least 89848 My address is K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. My latest block is #89852. Ok, open the debug.log and search for height=89815 2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526 Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. |
|
|
|
|
wr104 (OP)
|
|
June 24, 2015, 03:34:17 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. |
|
|
|
|
|
wr104 (OP)
|
|
June 24, 2015, 03:55:12 AM |
|
Are you still there? It's been 30 mins since your last reply.
|
|
|
|
|
cryptoVIP
Member
Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 03:58:19 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. Yes K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. # Wallet hexdump created by Kryptohash v0.5.1.0-g0-beta (Wed, 18 Mar 2015 12:59:59 +0000) # * Created on 2015-06-24T03:54:59Z # * Best block at time of backup was 89862 (0000000A520A9827BA0E0142BFFEE3A0B1D9D65536A5EDAF834809D24C1DBEB49B540E1D2979BD2  , # mined on 2015-06-24T03:50:33Z addr=aa pubkey=bb privkey=xxx time=2015-04-10T02:33:07Z label=SUM1 addr=K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 pubkey=bb2 privkey=xxx2 time=2015-04-10T02:33:07Z label=SUM2 |
|
|
|
|
wr104 (OP)
|
|
June 24, 2015, 04:05:11 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. Yes K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. # Wallet hexdump created by Kryptohash v0.5.1.0-g0-beta (Wed, 18 Mar 2015 12:59:59 +0000) # * Created on 2015-06-24T03:54:59Z # * Best block at time of backup was 89862 (0000000A520A9827BA0E0142BFFEE3A0B1D9D65536A5EDAF834809D24C1DBEB49B540E1D2979BD2 , # mined on 2015-06-24T03:50:33Z addr=aa pubkey=bb privkey=xxx time=2015-04-10T02:33:07Z label=SUM1 addr=K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 pubkey=bb2 privkey=xxx2 time=2015-04-10T02:33:07Z label=SUM2 Ok, this is great news. As long as you keep that Private Key secure, you can recover these coins. You could first try re-indexing the Destination Wallet and see what happens. Close the destination wallet, open Command Prompt, navigate to the folder where kryptohash-qt.exe is located and then type: kryptohash-qt.exe --reindex This is going to take a while. |
|
|
|
|
cryptoVIP
Member
Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 04:08:34 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. Yes K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. # Wallet hexdump created by Kryptohash v0.5.1.0-g0-beta (Wed, 18 Mar 2015 12:59:59 +0000) # * Created on 2015-06-24T03:54:59Z # * Best block at time of backup was 89862 (0000000A520A9827BA0E0142BFFEE3A0B1D9D65536A5EDAF834809D24C1DBEB49B540E1D2979BD2 , # mined on 2015-06-24T03:50:33Z addr=aa pubkey=bb privkey=xxx time=2015-04-10T02:33:07Z label=SUM1 addr=K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 pubkey=bb2 privkey=xxx2 time=2015-04-10T02:33:07Z label=SUM2 Ok, this is great news. As long as you keep that Private Key secure, you can recover these coins. You could first try re-indexing the Destination Wallet and see what happens. Close the destination wallet, open Command Prompt, navigate to the folder where kryptohash-qt.exe is located and then type: kryptohash-qt.exe --reindex This is going to take a while. Thank you very much for you time. reindexing ...  |
|
|
|
|
wr104 (OP)
|
|
June 24, 2015, 04:14:35 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. Yes K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. # Wallet hexdump created by Kryptohash v0.5.1.0-g0-beta (Wed, 18 Mar 2015 12:59:59 +0000) # * Created on 2015-06-24T03:54:59Z # * Best block at time of backup was 89862 (0000000A520A9827BA0E0142BFFEE3A0B1D9D65536A5EDAF834809D24C1DBEB49B540E1D2979BD2 , # mined on 2015-06-24T03:50:33Z addr=aa pubkey=bb privkey=xxx time=2015-04-10T02:33:07Z label=SUM1 addr=K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 pubkey=bb2 privkey=xxx2 time=2015-04-10T02:33:07Z label=SUM2 Ok, this is great news. As long as you keep that Private Key secure, you can recover these coins. You could first try re-indexing the Destination Wallet and see what happens. Close the destination wallet, open Command Prompt, navigate to the folder where kryptohash-qt.exe is located and then type: kryptohash-qt.exe --reindex This is going to take a while. Thank you very much for you time. reindexing ... No problem. The re-indexing should take care of the problem. But If for some reason it doesn't fix it, close the wallet, rename the region0 folder to region0.bak then, start a fresh wallet. Once the blockchain is downloaded, import the private key using the importprivkeyhex command. importprivkeyhex "privatekeyhexdata" "label" rescan And don't forget to upgrade the wallet to version 0.6.1 |
|
|
|
|
cryptoVIP
Member
Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 04:15:42 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. Yes K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. # Wallet hexdump created by Kryptohash v0.5.1.0-g0-beta (Wed, 18 Mar 2015 12:59:59 +0000) # * Created on 2015-06-24T03:54:59Z # * Best block at time of backup was 89862 (0000000A520A9827BA0E0142BFFEE3A0B1D9D65536A5EDAF834809D24C1DBEB49B540E1D2979BD2 , # mined on 2015-06-24T03:50:33Z addr=aa pubkey=bb privkey=xxx time=2015-04-10T02:33:07Z label=SUM1 addr=K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 pubkey=bb2 privkey=xxx2 time=2015-04-10T02:33:07Z label=SUM2 Ok, this is great news. As long as you keep that Private Key secure, you can recover these coins. You could first try re-indexing the Destination Wallet and see what happens. Close the destination wallet, open Command Prompt, navigate to the folder where kryptohash-qt.exe is located and then type: kryptohash-qt.exe --reindex This is going to take a while. Thank you very much for you time. reindexing ... No problem. The re-indexing should take care of the problem. But If for some reason it doesn't fix it, close the wallet, rename the region0 folder to region0.bak then, start a fresh wallet. Once the blockchain is downloaded, import the private key using the importprivkeyhex command. importprivkeyhex "privatekeyhexdata" "label" rescan Thanks,If reindex failed,I'll try the new wallet. |
|
|
|
cryptoVIP
Member
Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 05:46:59 AM |
|
2015-06-24 01:33:37 UpdateTip: new best=00000001214153CAD5BE1445A7C5D61E6935AE9B4D522F166B9226F94A65C1E869E76EE6EEBF2890 height=89815 log2_work=46.837256 tx=239291 TxTime=2015-06-24 01:24:20 nTime=421641 progress=0.999526
Do you see any AddToWallet message before or after that line? No,I closed the source wallet after I sent coins , then opend the destination wallet,no message was seen. I assume you're looking inside the debug.log on the destination wallet, right? Everytime you get coins, you should see AddToWallet entries. Now, on the destination wallet, go to Help menu, select "Debug Window" and then select Console tab. type: dumpwallethex "c:\{destination folder}\wallet.txt" Open the wallet.txt and search for the address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5. Your private key should be there too. JUST DON'T POST YOUR PRIV KEY HERE. I just want to know if your address K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. Yes K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 has a corresponding Priv Key. # Wallet hexdump created by Kryptohash v0.5.1.0-g0-beta (Wed, 18 Mar 2015 12:59:59 +0000) # * Created on 2015-06-24T03:54:59Z # * Best block at time of backup was 89862 (0000000A520A9827BA0E0142BFFEE3A0B1D9D65536A5EDAF834809D24C1DBEB49B540E1D2979BD2 , # mined on 2015-06-24T03:50:33Z addr=aa pubkey=bb privkey=xxx time=2015-04-10T02:33:07Z label=SUM1 addr=K9rAbsZgBg9pkcCTrszMNzUyk2oW2ejjE5 pubkey=bb2 privkey=xxx2 time=2015-04-10T02:33:07Z label=SUM2 Ok, this is great news. As long as you keep that Private Key secure, you can recover these coins. You could first try re-indexing the Destination Wallet and see what happens. Close the destination wallet, open Command Prompt, navigate to the folder where kryptohash-qt.exe is located and then type: kryptohash-qt.exe --reindex This is going to take a while. Thank you very much for you time. reindexing ... No problem. The re-indexing should take care of the problem. But If for some reason it doesn't fix it, close the wallet, rename the region0 folder to region0.bak then, start a fresh wallet. Once the blockchain is downloaded, import the private key using the importprivkeyhex command. importprivkeyhex "privatekeyhexdata" "label" rescan Thanks,If reindex failed,I'll try the new wallet. After the wallet was reindexed,I got my money  |
|
|
|
|
cvaky
|
|
June 24, 2015, 06:04:22 AM |
|
Looking nice, but it would be best to have filter for address and rich list. |
|
|
|
|
cryptoVIP
Member
Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 06:37:29 AM |
|
Looking nice, but it would be best to have filter for address and rich list. Yeah,quite agree! |
|
|
|
|
Riseman
|
|
June 24, 2015, 08:12:50 AM |
|
During the last 2 weeks I'm having an issue with mining. After I start the miner it works for about half an hour (sometimes even finds a block) but then it stops with a 'waiting for work' status. And stays like that for hours until I restart it. At the same time the wallet keeps receiving new blocks from the network.
When I press Q to stop the miner it sometimes restarts by itself and stops responding for any input.
I have tried to redownload the blockchain, generate a new wallet and upgrade to the latest version but it didn't help. Now I can't think of any particular reason to it because my PC configuration didn't change in any way since before the issue appeared. So I suppose it's somehow related to the network.
Maybe transactions became too rare and the miner just stops functioning if waiting for work for too long? But the diff stays around 18 which means someone is still mining.
|
|
|
|
|
cryptoVIP
Member
Offline
Activity: 79
Merit: 10
|
|
June 24, 2015, 09:33:07 AM |
|
During the last 2 weeks I'm having an issue with mining. After I start the miner it works for about half an hour (sometimes even finds a block) but then it stops with a 'waiting for work' status. And stays like that for hours until I restart it. At the same time the wallet keeps receiving new blocks from the network.
When I press Q to stop the miner it sometimes restarts by itself and stops responding for any input.
I have tried to redownload the blockchain, generate a new wallet and upgrade to the latest version but it didn't help. Now I can't think of any particular reason to it because my PC configuration didn't change in any way since before the issue appeared. So I suppose it's somehow related to the network.
Maybe transactions became too rare and the miner just stops functioning if waiting for work for too long? But the diff stays around 18 which means someone is still mining.
I've encountered the same problem while solo mining. |
|
|
|
|
wr104 (OP)
|
|
June 24, 2015, 12:25:46 PM |
|
During the last 2 weeks I'm having an issue with mining. After I start the miner it works for about half an hour (sometimes even finds a block) but then it stops with a 'waiting for work' status. And stays like that for hours until I restart it. At the same time the wallet keeps receiving new blocks from the network.
When I press Q to stop the miner it sometimes restarts by itself and stops responding for any input.
I have tried to redownload the blockchain, generate a new wallet and upgrade to the latest version but it didn't help. Now I can't think of any particular reason to it because my PC configuration didn't change in any way since before the issue appeared. So I suppose it's somehow related to the network.
Maybe transactions became too rare and the miner just stops functioning if waiting for work for too long? But the diff stays around 18 which means someone is still mining.
It could be an issue with cgminer not seeing new work or stopping to grab new work. To confirm this, next time it happens, open the debug console on the wallet and type getwork. If you see a non-zero response then, there is work but cgminer isn't seeing it. Also, tell me what OS you're running. If it is Windows, I just released a new cgminer-khc 3.7.8b with new DLLs for CURL and OpenSSL. Also, Is cgminer connecting to the Wallet on the same localhost or, it's connecting to one on a remote PC? Are you using SSL for RPC calls? A couple a days ago, I wrote a Perl script that checks if there is work on the network every 2 seconds. If there isn't work, the script immediately sends 2 cents to one of my wallets. This will keep miners busy. |
|
|
|
|
|
Riseman
|
|
June 26, 2015, 06:26:32 PM |
|
It could be an issue with cgminer not seeing new work or stopping to grab new work. To confirm this, next time it happens, open the debug console on the wallet and type getwork. If you see a non-zero response then, there is work but cgminer isn't seeing it.
Also, tell me what OS you're running. If it is Windows, I just released a new cgminer-khc 3.7.8b with new DLLs for CURL and OpenSSL. Also, Is cgminer connecting to the Wallet on the same localhost or, it's connecting to one on a remote PC? Are you using SSL for RPC calls?
A couple a days ago, I wrote a Perl script that checks if there is work on the network every 2 seconds. If there isn't work, the script immediately sends 2 cents to one of my wallets. This will keep miners busy.
I finally checked this. Getwork sometimes returns all zeros and sometimes valid data when the miner is stuck. I think it makes sense. I am running Windows 7 x64 with the latest wallet and miner now. All on my local PC. Actually the problem appears on previous versions as well. I didn't configure SSL explicitly so I suppose I'm not using it. |
|
|
|
|
|
wr104 (OP)
|
|
June 26, 2015, 08:05:46 PM |
|
It could be an issue with cgminer not seeing new work or stopping to grab new work. To confirm this, next time it happens, open the debug console on the wallet and type getwork. If you see a non-zero response then, there is work but cgminer isn't seeing it.
Also, tell me what OS you're running. If it is Windows, I just released a new cgminer-khc 3.7.8b with new DLLs for CURL and OpenSSL. Also, Is cgminer connecting to the Wallet on the same localhost or, it's connecting to one on a remote PC? Are you using SSL for RPC calls?
A couple a days ago, I wrote a Perl script that checks if there is work on the network every 2 seconds. If there isn't work, the script immediately sends 2 cents to one of my wallets. This will keep miners busy.
I finally checked this. Getwork sometimes returns all zeros and sometimes valid data when the miner is stuck. I think it makes sense. I am running Windows 7 x64 with the latest wallet and miner now. All on my local PC. Actually the problem appears on previous versions as well. I didn't configure SSL explicitly so I suppose I'm not using it. If it is all running on your local PC then, you don't need to enable SSL for RPC calls. Let me know if the issue still happens with the latest CURL DLL. To me this sounds like a resource leak in cgminer (or CURL) that surfaces when it is in that loop waiting for new work. |
|
|
|
|
|
Riseman
|
|
June 26, 2015, 10:34:08 PM |
|
If you mean the dll's included with the latest cgminer-khc-v3.7.8b then yes, it happens.
|
|
|
|
|
|
|
berbip
Member
Offline
Activity: 143
Merit: 10
|
|
June 29, 2015, 07:39:49 AM |
|
I've setup a new 64-bit wallet on a new machine, is there a way to transfer my funds from my old 32 bit machine to the new one without transfer cost ?
I have a lot of small transactions in my 32bit wallet and it takes a long time to start up, would that be better in a 64 bit wallet with only a couple of transactions ?
|
|
|
|
|
|
