Bitcoin Forum
May 04, 2024, 04:07:48 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Core not showing new incoming transactions after restoring wallet.dat  (Read 656 times)
b52e7705 (OP)
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
September 09, 2017, 01:09:43 AM
 #1

I am having problems getting new transactions to show up in a Bitcoin Core wallet I just restored.

A few days ago I reinstalled the OS on a machine I run with a full 0.14.2 node (which I compiled from source). I made a backup of my wallet.dat file, reinstalled the OS, and then restored my backup of the blockchain + wallet.dat file. So far so good. I then generated a new address using "bitcoin-cli getnewaddress" and made a withdrawal from an exchange to that address. The withdrawal has been confirmed in more than 10,000 blocks now, but the balance is not showing up when I run "bitcoin-cli getbalance", and the transaction is not showing up when I run "bitcoin-cli listtransactions".

More details, and things that look correct:
  • The transaction was part of block 0000000000000000018e18a6ad7d3c271fb426c77a50793c76ea37f4bbca679b, which has more than 10,000 confirmations now
  • When I run "bitcoin-cli validateaddress theaddress" it shows "ismine" as true, and gives me the hdkeypath and so forth
  • When I run "bitcoin-cli getaddressesbyaccount """ it lists the address I used
  • blockchain.info confirms the tx went through, and confirms that the address has the expected balance

Things that are incorrect:
  • "bitcoin-cli getbalance" does not reflect the expected balance
  • "bitcoin-cli listtransactions" does not show the transaction
  • "bitcoin-cli getreceivedbyaddress theaddress" shows 0.00000000

All of these things make me think that the bitcoin is secure and not lost, but perhaps somehow I misconfigured Bitcoin Core when I installed it and restored my wallet.dat file. I looked through my debug.log and didn't see anything that looked too suspicious. Can someone give me a recommendation on how to proceed from here?
1714795668
Hero Member
*
Offline Offline

Posts: 1714795668

View Profile Personal Message (Offline)

Ignore
1714795668
Reply with quote  #2

1714795668
Report to moderator
1714795668
Hero Member
*
Offline Offline

Posts: 1714795668

View Profile Personal Message (Offline)

Ignore
1714795668
Reply with quote  #2

1714795668
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714795668
Hero Member
*
Offline Offline

Posts: 1714795668

View Profile Personal Message (Offline)

Ignore
1714795668
Reply with quote  #2

1714795668
Report to moderator
1714795668
Hero Member
*
Offline Offline

Posts: 1714795668

View Profile Personal Message (Offline)

Ignore
1714795668
Reply with quote  #2

1714795668
Report to moderator
1714795668
Hero Member
*
Offline Offline

Posts: 1714795668

View Profile Personal Message (Offline)

Ignore
1714795668
Reply with quote  #2

1714795668
Report to moderator
ranochigo
Legendary
*
Offline Offline

Activity: 2954
Merit: 4165


View Profile
September 09, 2017, 02:17:37 AM
 #2

Is your client synchronized? Run bitcoin-cli getinfo, if the blocks says 484281, you are good.

Though it is not exactly necessary, you can run the client with rescan flag for the client to scan the Blockchain for any transactions that were not included.

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
boink
Newbie
*
Offline Offline

Activity: 30
Merit: 0


View Profile
September 09, 2017, 02:22:19 PM
 #3

Try to start the Bitcoin client with -rescan
If your client is fully synced then your balance should shows up after the rescan is done.
Spendulus
Legendary
*
Offline Offline

Activity: 2898
Merit: 1386



View Profile
September 13, 2017, 12:34:10 AM
 #4

I am having problems getting new transactions to show up in a Bitcoin Core wallet I just restored.

A few days ago I reinstalled the OS on a machine I run with a full 0.14.2 node (which I compiled from source). I made a backup of my wallet.dat file, reinstalled the OS, and then restored my backup of the blockchain + wallet.dat file. So far so good. I then generated a new address using "bitcoin-cli getnewaddress" and made a withdrawal from an exchange to that address. The withdrawal has been confirmed in more than 10,000 blocks now, but the balance is not showing up when I run "bitcoin-cli getbalance", and the transaction is not showing up when I run "bitcoin-cli listtransactions".

More details, and things that look correct:
  • The transaction was part of block 0000000000000000018e18a6ad7d3c271fb426c77a50793c76ea37f4bbca679b, which has more than 10,000 confirmations now
  • When I run "bitcoin-cli validateaddress theaddress" it shows "ismine" as true, and gives me the hdkeypath and so forth
  • When I run "bitcoin-cli getaddressesbyaccount """ it lists the address I used
  • blockchain.info confirms the tx went through, and confirms that the address has the expected balance

Things that are incorrect:
  • "bitcoin-cli getbalance" does not reflect the expected balance
  • "bitcoin-cli listtransactions" does not show the transaction
  • "bitcoin-cli getreceivedbyaddress theaddress" shows 0.00000000

All of these things make me think that the bitcoin is secure and not lost, but perhaps somehow I misconfigured Bitcoin Core when I installed it and restored my wallet.dat file. I looked through my debug.log and didn't see anything that looked too suspicious. Can someone give me a recommendation on how to proceed from here?

Presuming that the rescan does not fix it -

It would be interesting to run a test with a 0.14.2 that was not compiled from source, just the standard download....
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!