[Box Backup] Need to reload bbackupd conf to avoid timeouts?
Tobias Balle-Petersen
boxbackup@fluffy.co.uk
Thu, 02 Nov 2006 12:24:28 +0100
Hello.
Just to let you know, I have tried to delete the contents of /var/bbackupd
I have had this problem for a while.
Here is an older log from the client showing the error:
Aug 24 11:11:27 yoiko bbackupd[11514]: TRACE: Reallocating EncodingBuffer from 2601 to 4777\n
Aug 24 11:11:27 yoiko bbackupd[11514]: TRACE: Reallocating EncodingBuffer from 1068 to 2606\n
...................
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Reallocating EncodingBuffer from 1068 to 3244\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Reallocating EncodingBuffer from 3244 to 5413\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Novo Nordisk/Recruitment/recruitment_ms\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Novo Nordisk/Recruitment/recruitment_tos\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Novo Nordisk/Recruitment/recruitment2_ms\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Novo Nordisk/Recruitment/re.kmo\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Novo Nordisk/Recruitment/recruitment transport fredag\n
Aug 24 11:16:19 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Novo Nordisk/Recruitment/re.transp.mandag\n
Aug 24 11:20:28 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/Medicon\n
Aug 24 11:20:28 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/clients/MOUNT\n
Aug 24 11:20:44 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/guests/Bergen Bybane\n
Aug 24 11:20:44 yoiko bbackupd[11514]: TRACE: Deleted directory record for
/Volumes/raidA/files/guests/Library1\n
Aug 24 11:41:58 yoiko bbackupd[11514]: TRACE: Exception thrown:
ConnectionException(Conn_TLSReadFailed) at SocketStreamTLS.cpp(361)\n
Aug 24 11:41:58 yoiko bbackupd[11514]: TRACE: Exception thrown:
ConnectionException(Conn_TLSWriteFailed) at SocketStreamTLS.cpp(426)\n
Aug 24 11:41:59 yoiko bbackupd[11514]: Exception caught (Connection TLSReadFailed 7/34), reset state
and waiting to retry...
Aug 24 11:42:09 yoiko bbackupd[11514]: File statistics: total file size uploaded 13410118455, bytes
already on server 341406646, encoded size 9996343505
Aug 24 11:42:09 yoiko bbackupd[11514]: TRACE: Wait on command socket, delay = 1024000000\n
Aug 24 11:59:13 yoiko bbackupd[11514]: TRACE: Wait on command socket, delay = 1024000000\n
Tobias
Ben Summers wrote:
>
> Please turn on ExtendedLogging = yes on client and server, and we'll see
> what it's doing at the time of the exception.
>
> Ben
>
>
>
>
> On 2 Nov 2006, at 11:09, Tobias Balle-Petersen wrote:
>
>> Hello again.
>>
>> Would changing the KeepAliveTime parameter ,as a fix for my problem,
>> make sense considering the backup run ALWAYS completes on the first
>> run since a reload of the bbackupd.conf file ? The point being that
>> the first run completes with the KeepAliveTime = 10.
>>
>> Tobias
>>
>>
>> Ben Summers wrote:
>>> Try using KeepAliveTime in bbackupd.conf, if you're not already doing
>>> so.
>>> Ben
>>> On 2 Nov 2006, at 10:51, Tobias Balle-Petersen wrote:
>>>> Hello.
>>>>
>>>> I'm running box 0.10 client on a OS X machine and the 0.10 store on
>>>> a debian machine.
>>>> I'm, backing up more than 1TB of data. bbackupd will complete if run
>>>> for the first time since a reload of the .conf file. If the .conf is
>>>> not reloaded prior to every backup run, it wil fail with the error
>>>> below. If I use the StoreObjectInfoFile feature and reload the .conf
>>>> prior to every run, the backup still fails with the error below.
>>>>
>>>> The error:
>>>> Exception caught (Connection Protocol_Timeout (Probably a network issue
>>>> between client and server.) 7/41), reset state and waiting to retry...
>>>>
>>>>
>>>> The conjobs that avoids the errors:
>>>> 20 10 * * * /usr/local/bin/bbackupctl -c
>>>> /etc/box_minimoni/bbackupd.conf reload
>>>> 25 10 * * * /usr/local/bin/bbackupctl -c
>>>> /etc/box_minimoni/bbackupd.conf sync
>>>>
>>>>
>>>> Any ideas?
>>>>
>>>> Thanks,
>>>> Tobias
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> boxbackup mailing list
>>>> boxbackup@fluffy.co.uk
>>>> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
>>> _______________________________________________
>>> boxbackup mailing list
>>> boxbackup@fluffy.co.uk
>>> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
>>
>> _______________________________________________
>> boxbackup mailing list
>> boxbackup@fluffy.co.uk
>> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
>
> _______________________________________________
> boxbackup mailing list
> boxbackup@fluffy.co.uk
> http://lists.warhead.org.uk/mailman/listinfo/boxbackup
>