Author

Topic: 0/unconfirmed; 0/offline? (Read 10375 times)

hero member
Activity: 574
Merit: 507
August 30, 2010, 03:43:49 PM
#3
In case anybody ever experiences an issue similar to mine:

I returned to my computer noticing there were network issues.  I resolved them and in doing so I `/etc/init.d/net.eth0 restart`ed which stopped and restarted my ethernet connection to the Internet.  Bitcoin client was running before and after this time.  Shortly after restarting the connection, I sent Bitcoins to an address.  I noticed after more than two minutes that the transaction showed as 0/offline?  I also noticed that I had only one connection as listed on the status bar.  I presumed it was due to my previous network issues and perhaps especially after specifically stopping and restarting the ethernet device.  I promptly stopped and restarted Bitcoin client.

The transaction then appeared as 0/unconfirmed.  After two confirmations for all my other transactions I noticed that the latest transaction still showed 0/unconfirmed.  I worried a bit, contemplating that perhaps I had lost the Bitcoins.

Quote
When the interface went down it is possible Bitcoin stopped trying to bind to it and didn't look for new interfaces.
Let it sit for a while.  Resend is once every two hours or so.
Would it be okay if I close the bitcoin client, make another backup and then restart the bitcoin client or will that interfere?
Just wait for a ResendWalletTransactions
When the client resends TXes it writes "ResendWalletTransactions" to debug.log
It happens randomly every 30 min avg I think
The code is a bit convoluted, but I think 1 block + 5 - 30 min
ResendWalletTransactions() is in main.cpp

Then a while later (less than an hour) the transaction now shows as 3/unconfirmed.  Teh transaction was eventually resent.
legendary
Activity: 860
Merit: 1021
July 20, 2010, 03:48:04 PM
#2
You don't have forward the port to connect to other nodes.
member
Activity: 94
Merit: 10
July 20, 2010, 01:02:32 PM
#1
I have two machines in my LAN. The first is port-forwarded (8333) and the second connects to nodes magically (even if the first machine powered down). There is 5 first machine payments on the picture. Last payment sent to the second machine. Now is 20.07.2010 20:52 and I have 0 confirmations (and restarted bitcoin). I have two questions:

  • What can cause such delays?
  • How the second PC connects to nodes?
Jump to: