Right now (04:50 GMT) my node is connecting to yours and getting zombie connections each time. The socket isn’t returning an error, just zombie without notice. If you’re running the linux build right now, it would be interesting to see what the log says on your side.
test3:
I’ve added specific code to detect zombie sockets. It’ll detect if the socket hasn’t sent or received any data within 60 seconds of connecting, and detect if data is queued to send and hasn’t sent for 3 minutes.
I think I may have weakened the reconnect speed in test2. In test3 I’m making it more determined to reconnect quickly.
I added checking to track whether other nodes received your generated blocks. If none did, it’ll warn you in the description: “Generated - Warning: This block was not received by any other nodes and will probably not be accepted!”
The status can go to ”#/offline?” for blocks or transactions you create if they don’t get out to any other nodes.
With all this, it should be impossible not to notice as soon as it screws up. It should hopefully disconnect all the zombie sockets. After that, whether it’s able to make some good connections, or sockets is completely hosed and it stays at 0 connections, I don’t know.
If this doesn’t work, I guess I’ll look at the sourcecode of some other P2P apps like BitTorrent and see how they deal with this stuff. Maybe there’s some magic flag or procedure to bash the sockets system back to life.
File linux-0.1.6-test3.tar.bz2 attached in the next message.
Liberty Standard wrote:
On Wed, Nov 11, 2009 at 8:08 AM, Liberty Standard <newlibertystandard@gmail.com mailto:newlibertystandard@gmail.com> wrote:
My network connection is direct to my computer. My ISP requires that I run VPN to connect to the Internet. I then have a second NIC that shares my Internet with other devices. My IP address while using my computer is my actual IP address, but the devices connected through my second NIC use NAT. When I connect through a virtual machine, that also uses NAT. All this requires very little configuration. NetworkManager in Ubuntu has an option to share my Internet connection through the second NIC and VirtualBox has the option to use NAT. I lost a couple packs of bitcoins again, so that problem is not yet fixed. It's a bit more bearable now that I have an idea of what is going on. I figure for now I'll just restart bitcoin whenever I see a pack of bitcoins starting to mature. I may go back and forth a bit between Linux and Wine, but I'll definitely test every new version that comes out. At the moment I'm still running the Linux build. On Wed, Nov 11, 2009 at 7:49 AM, Satoshi Nakamoto <satoshin@gmx.com <mailto:satoshin@gmx.com>> wrote: Thanks. The log didn't stop on anything special, just simple message passing. Chances are it's UI related. Most of the initial bugs were all UI. What brand/model of firewall do you have? It's possible for BitTorrent to overwhelm the number of connections some models can handle. Most are underpowered and flaky under load. NewLibertyStandard wrote: I have been getting your attachments just fine. I just thought I'd spare Martti the large attachment. I am not able to reproduce the bug. I don't know whether the paste, the blocks finishing, a combination of the two or something else entirely caused the fault. ... But after they started downloading, I took a look a look at my BitTorrent client, and sure enough, I had forgotten about a torrent and my upload was quite high, at the limit I had set for it.
Source: Published by Martti Malmi on GitHub in February 2024 as part of his testimony in the COPA v. Wright trial. The full correspondence archive is available at mmalmi.github.io/satoshi/.