[Box Backup] Troubleshooting "Connection TLSWriteFailed 7/33" on OS X server/client setup
Tue, 8 Aug 2006 10:41:14 +0100
I don't think you've answered my question about whether the Mac OS X
machine running bbackupd ever sleeps. If it does, I think that's your
answer. If it goes to sleep while connected to the server, the
connection will time out. KeepAlive won't help as the CPU is not
running the code.
On 8 Aug 2006, at 10:03, Tobias Balle-Petersen wrote:
> The "Connection TLSReadFailed"only happens from time to time, so I
> would have to log tcpdump and wait for the error to happen. What
> parameters should I use for tcpdump?
> Maybe I should change the KeepAliveTime to 10 for testing purposes?
> Chris Wilson wrote:
>> Hi Tobias,
>>> Yes I have enabled Keep alive on the clients. My config says:
>>> KeepAliveTime = 600
>>> I used to have 60, but changed to 600 to see if it made a
>>> difference. It did not.
>> Can you check that keepalives are actually working? Run tcpdump on
>> one of the machines to watch the traffic between the two, and make
>> sure that there is actually some traffic each way every 60 seconds
>> in the period between "Receiving stream, size uncertain" and
>> "Connection TLSReadFailed". If you're not sure, you can email the
>> tcpdump output to me.
>> Ben and Nick, I was under the impression that keepalives involved
>> a command request by the client, so they should show up in the
>> extended log? I don't see any evidence of that here.
>> Cheers, Chris.
> boxbackup mailing list