How can you make it connect to some specific node? Thats exactly what I need right now 
there is a command line option
type bitcoin -? for help
I believe it's -connect=xxx.xxx.xxx.xxx
Topic: wallet glitched - page 2. (Read 4240 times)
there is a command line option
type bitcoin -? for help
I believe it's -connect=xxx.xxx.xxx.xxx
I think it's a rescan bug.
How can you make it connect to some specific node? Thats exactly what I need right now
I had the same thing, I recovered by deleting the databases (but not wallet.dat) and then running bitcoin, telling it to connect to another node on my network running bitcoin, so it could redownload the whole block chain without sapping my internet connection.
I fixed this by restoring a copy of wallet.dat from before I made the tx in question, then running -rescan. I would still like to know if there's a reason for the behavior I saw. It seems from the warning at http://sourceforge.net/projects/bitcoin/files/Bitcoin/blockchain/ (from the README.txt), that wallets with unprocessed transactions have known issues.
Or you could check if the transaction made it into the blockchain on blockexplorer.com..
Pretty soon someone knowledgeable is going to come along and say:
"Run bitcoin -debug, double click the transaction, and paste the contents of the Transaction Details window."
"Run bitcoin -debug, double click the transaction, and paste the contents of the Transaction Details window."
I have a tx showing 0/unconfirmed, which won't change even if I use -rescan.
Here's what I did:
1. send tx
2. immediately quit bitcoin
3. move wallet.dat aside, replace with a different one
4. run bitcoin. The tx doesn't appear, as expected
5. wait for a new block- tx appears with 1 confirmation (since this wallet is the recipient)
6. quit bitcoin
7. put original wallet.dat back.
8. tx still stuck at 0/unconfirmed. all other tx have confirmations increasing. -rescan has no effect.
This seems to be a bug, since rescan should work.
Here's what I did:
1. send tx
2. immediately quit bitcoin
3. move wallet.dat aside, replace with a different one
4. run bitcoin. The tx doesn't appear, as expected
5. wait for a new block- tx appears with 1 confirmation (since this wallet is the recipient)
6. quit bitcoin
7. put original wallet.dat back.
8. tx still stuck at 0/unconfirmed. all other tx have confirmations increasing. -rescan has no effect.
This seems to be a bug, since rescan should work.
Jump to: