I have been conversing with Tim from Zonbu support today, looking to resolve my S3 storage issues.
Based on Tim’s assessment of my debug.log file, he says there appears to be a timeout on our end. This may be the case.
We have a fairly complex caching infrastructure in place for HTTP traffic. It is transparent to the end user, but it does have some unusual rules. Once of these configuration nuances may be the culprit.
The Zonbu speaks HTTP to the S3 servers (something I’m not thrilled about but I also don’t know what other options are offered by S3).
I have now exempted the S3 site from the bulk of these unusual local rules to see if the problem clears up. I will keep you posted.
-Mr. Zonbu
PS – Look for a future article on what Zonbu can do to optimize the experience on the “local loop” of the broadband network. File access was something Mossberg complained strongly about, optimizing this is important.
Real life with the Zonbu Mini-PC 
From my understanding of how Zonbu syncs with S3 is that all new writes are initially done to the CF and then later transferred to S3. Isn’t this going to severely limit the life of the CF card? I believe all flash devices have a limited # of writes before they become unreliable. I know that distros made to run off of a USB stick such Puppy Linux have measures designed into it to drastically limit the number of writes that are made during each session. So, if Zonbu goes the route of even more local caching to lessen the lag this is going to make that problem even worse.
An excellent question and on my “To Do” list is a piece on CF lifespan. 🙂
A better model is to work with the broadband operators to have store and forward equipment in their data centers. More to come. 🙂
-Mr. Zonbu