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