Quote from: defxor on August 06, 2011, 09:51:06 AM

In my case I have two identical clients where one cannot send while the other can. I've even copied the blockchain between them so I know it's not corrupt.

So, just for fun, I redid the exact same transaction I couldn't do with one client with the other one instead. Again, the only real difference is that one is port mapped and has >100 connections, the other is behind NAT with 8. They use the same block chain files, they're up to date and all that.

Both clients seem to write 1MB/s constantly to disk (can someone else on Mac please check this? edit: And are you using Filevault) but the well-connected one runs off an SSD which means I've never noticed it before.

NAT client: "0/unconfirmed", "0/offline?" - sends are never announced. Tried multiple times to send 2 BTC (old coins), no fee.

Mapped client: Sent 1 BTC (old coins), no fee. The announce was instantly visible on bitcoincharts/bitcoin and after a few minutes it could be seen in blockexplorer and had 1 confirm.

I guess one explanation lies in how many peers they have, but the NATed client is never even able to make the announce to the network even though it gets block updates just fine. If that's the general state for NAT clients then that needs to be rethought. Else I'm leaning towards an OS X specific problem in .24 that might or might not be related to the weird disk writes.