0 confirmations after over a month, WTF? - page 2.

defxor

hero member

Activity: 530

Merit: 500

Quote from: 2112 on August 05, 2011, 06:11:14 PM

Quote from: defxor on August 05, 2011, 05:10:44 PM

I'm still interested in exactly what the Bitcoin client is doing writing 1MB/s to disk with no actual file getting any larger though.

I think it is updating the database of peer IP addresses in a stupid way. I never got up to 500 peers but I've noticed that the more connections you have the more frequent the updates.

Hmm. The code must be extremely bad if it can reach 1MB/s doing that.

I've actually given up on getting this client installation to perform any send transactions. With the new fixed wallet I again tried sending coins and just like last time they stayed at "0/unconfirmed". I even got to see "0/offline?" - this on a client with 8 peer connections and receiving updates to the block chain without issues.

(I don't consider the title to be misleading - if we ever want to get non-techies to feel comfortable using Bitcoin with the official client)

2112

legendary

Activity: 2128

Merit: 1073

Quote from: defxor on August 05, 2011, 05:10:44 PM

I'm still interested in exactly what the Bitcoin client is doing writing 1MB/s to disk with no actual file getting any larger though.

I think it is updating the database of peer IP addresses in a stupid way. I never got up to 500 peers but I've noticed that the more connections you have the more frequent the updates.

jgarzik

legendary

Activity: 1596

Merit: 1100

Quote from: MemoryDealers on August 05, 2011, 05:13:23 PM

I think you should change the title of your thread from " bitcoin client is eating my bitcoins, WTF?" to bitcoin client is not confirming my transactions, WTF?

+1, the devs monitor for threads like this, and the title is definitely misleading

MemoryDealers

vip

Activity: 1052

Merit: 1155

I think you should change the title of your thread from " bitcoin client is eating my bitcoins, WTF?" to bitcoin client is not confirming my transactions, WTF?

I came to the forums and saw this thread title, and instantly had a horrible fear that there was a major bug with the client.

If you like bitcoins, there is no reason to cause unneeded alarm with sensational message subjects that are not accurate.

defxor

hero member

Activity: 530

Merit: 500

Quote from: proudhon on August 05, 2011, 04:11:29 PM

Moral of the story, make frequent backups people!

Yeah I stopped waiting as well now. I have a new automatic & encrypted backup made whenever the wallet file changes so it was easy to roll back (complete version history available).

I'm still interested in exactly what the Bitcoin client is doing writing 1MB/s to disk with no actual file getting any larger though.

Quote from: jackjack on August 05, 2011, 04:46:24 PM

For those who didn't make any backup, I made a script that cancels those tx's: https://bitcointalksearch.org/topic/guide-cancel-your-0unconfirmed-transactions-31418

Ah I've missed that, although I do use the excellent pywallet script for wallet manipulation

kookiekrak

full member

Activity: 238

Merit: 100

you can use jack's script, or download your own berkeleydb tools and rebuild the db following this guide

https://bitcointalksearch.org/topic/guide-fix-any-unconfirmed-transaction-error-31415

jackjack

legendary

Activity: 1176

Merit: 1280

May Bitcoin be touched by his Noodly Appendage

For those who didn't make any backup, I made a script that cancels those tx's: https://bitcointalksearch.org/topic/guide-cancel-your-0unconfirmed-transactions-31418

OgNasty

donator

Activity: 4760

Merit: 4323

Leading Crypto Sports Betting & Casino Platform

I never pay a fee and have yet to ever see a transaction take longer than 20 minutes to confirm. FWIW.

proudhon

legendary

Activity: 2198

Merit: 1311

Quote from: AtlasONo on August 05, 2011, 03:07:33 PM

Why would he need a fee to send 5 & 7 BTC?!?!?

edit: sent 1 BTC and it has 4 conformations already. Stop spouting shit.

So, thankfully I backup my wallet frequently. I found a backup that I made on 6/24, the day before the first bad transaction on 6/25, and restored that wallet.dat and the bad 0/confirmations transactions were gone and my balance reflected what it should be had I never initiated those transaction. I still don't understand why, even if I didn't include a fee, those transactions essentially never got off the ground. Later I'm going to cross my fingers and try to send a coin or two with a transaction fee and see if everything's back to normal.

Moral of the story, make frequent backups people!

CydeWeys

full member

Activity: 154

Merit: 100

First of all, are you now, or were you ever, running a modified client that messed with the required minimum transaction fees? If so, there's your problem.

If not, then your problem is that you have an unconfirmed transaction that the network no longer sees, and that will thus never be confirmed, tying up your coins in your wallet indefinitely. You need to remove that transaction from your wallet file. I don't specifically know how to accomplish this, but as the wallet file is just unencrypted binary data, and the client that reads and writes the wallet file is entirely open source, it is definitely possible. Somewhere out there should be a wallet munger program that lets you import/export private keys, modify transactions, etc. Obviously make a wallet backup before trying anything like that.

Vod

legendary

Activity: 3668

Merit: 3010

Licking my boob since 1970

Same thing happened to me Wednesday. I had corruption in my block chain.

I shut down Bitcoin
Made a copy of the entire bitcoin directory for safety
Deleted everything in the bitcoin directory
Copied over a wallet.dat from before the corruption started
Restarted Bitcoin
Bitcoin downloaded the block chain and rebuilt my missing transactions.

My corruption was the result of my Bitcoin client crashing. Pay attention to any error messages you see.

AtlasONo

hero member

Activity: 551

Merit: 500

Why would he need a fee to send 5 & 7 BTC?!?!?

edit: sent 1 BTC and it has 4 conformations already. Stop spouting shit.

kwukduck

legendary

Activity: 1937

Merit: 1001

I had the same problem in the past, only way i was able to solve it was to make a copy of the wallet.dat, remove everything, blockchain, database. Put back an old backup of the wallet (one that doesn't contain these transactions yet) and let it redownload the full blockchain.
Today -rescan might just do the trick, but since the transaction is stored in the current wallet.dat i think it still shows the coins missing.

willphase

hero member

Activity: 767

Merit: 500

you could delete your blockchain, then restart the client with -rescan and it'll re download the block chain and those 0/unconfirmed should vanish. It'll take a while to download the chain though.

Will

defxor

hero member

Activity: 530

Merit: 500

Quote from: proudhon on August 05, 2011, 12:41:39 PM

still said "0/unconfirmed" for that transaction, even though I had an updated blockchain.

The address is correct. But, blockexplorer does not show any incoming activity to the address I attempted to send coins to. The coins, however, have been deducted from my balance.

running OS X Snow Leopard. I'm currently running v0.3.24

I'm seeing the same thing with the latest send on one of my computers (tx not announced). On my other (same OS, same version etc) I don't have any problems at all.

On the problematic client Bitcoin is constantly writing 1MB/s data to the disk (edit: And not to any file I can see growing in size!). Thinking it was due to a corrupted blockchain I cleaned it up and copied the blockchain from my other client - but it didn't make a difference.

Slightly weird. I'm leaning towards an OS X specific bug in .24 that doesn't manifest itself on all configurations. The only difference between my two clients is that one is portmapped (>100 connections) and the other isn't (8).

proudhon

legendary

Activity: 2198

Merit: 1311

Yeah, I tried -rescan first thing and it didn't work.

bitplane

sr. member

Activity: 321

Merit: 250

Firstbits: 1gyzhw

Ah, okay...

Idea: copy the wallet and export the private keys using bitcoin-tools, compile the latest experimental client from git and import the keys into a new wallet (the ones that received coins).. the record of the transaction being broadcast to the network will not exist in the new wallet, so you can double-spend them to a different address in your new wallet.

Edit: It's possible to transfer keys between your old wallet and a blank one by using pyWallet.

Xephan

newbie

Activity: 42

Merit: 0

Quote from: bitplane on August 05, 2011, 02:10:09 PM

Won't starting the client with --rescan fix this?

No, that's when you know the transaction's been processed, you can find it in blockexplorer but your wallet isn't showing it

In his case, his wallet knows the transaction but nobody's willing (or succeeded yet) to process it into a block.

bitplane

sr. member

Activity: 321

Merit: 250

Firstbits: 1gyzhw

Won't starting the client with --rescan fix this?

Astrohacker

full member

Activity: 156

Merit: 102

Quote from: proudhon on August 05, 2011, 01:33:24 PM

Quote from: Astrohacker on August 05, 2011, 01:28:54 PM

You can make new transactions with the same coins. i.e., double spend them, but just send them to the same addresses you were going to send them to. It might help to include a bigger fee. If the new transactions are accepted, the old ones will be irrelevant.

How do you make new transactions with the same coins? Also, I know the recommended transaction fee is 0.01, but is that enough to get a transaction in a new block within, say, a day?

Well I don't think the present client supports that, but in principle you just construct a new transaction. Make sure to use up all the coins in those addresses, so if anyone tries to plug the first transaction into a block, it won't be valid. Someone made a client that lets you pick which addresses you send from, you could try that one. You could try removing all the blocks in your block chain since before you sent the coins, that way the client doesn't think it's double spending.

Another thing is to just wait with your client on, because it will rebroadcast the transactions after a random amount of time less than 30 minutes.

Topic: 0 confirmations after over a month, WTF? - page 2. (Read 3482 times)