[Box Backup] Odd Box Issue

Matt Brown boxbackup@fluffy.co.uk
Tue, 27 May 2008 17:38:58 +0100


>
> This appears to be fine, and running bbackup -VTD shows a lot of  
> verbose output and show the time for the file eta as 0s after a  
> while a timeout occurs advising:
>
> caught exception: Connection Protocol_Timeout (Probably a network  
> issue between client and server.) (7/41)
>
> All clients are using the same version and all work except this site  
> which stopped a few days ago ....
>
> Any pointers where I can go from here ?

Here is the output from bbackupd -VTD

17:31:04 Receive Success(0x1e55f)
17:31:04 /etc/clamav/clamd.conf: will not upload (no reason to upload,  
mod time is 1204898784000000 versus sync period 0 to 1242664240014206)
17:31:04 Synchronised file: /etc/clamav/clamd.conf
17:31:04 /etc/clamav/clamav-base.init: will not upload (no reason to  
upload, mod time is 1168075219000000 versus sync period 0 to  
1242664240014206)
17:31:04 Synchronised file: /etc/clamav/clamav-base.init
17:31:04 /etc/clamav/freshclam.conf: will not upload (no reason to  
upload, mod time is 1211196585000000 versus sync period 0 to  
1242664240014206)
17:31:04 Synchronised file: /etc/clamav/freshclam.conf
17:31:04 Scanning directory: /etc/clamav/onupdateexecute.d
17:31:04 Send ListDirectory(0x1e563,0xffff,0xc,true)
17:31:04 Receive Success(0x1e563)
17:31:04 Scanning directory: /etc/clamav/onerrorexecute.d
17:31:04 Send ListDirectory(0x1e564,0xffff,0xc,true)
17:31:04 Receive Success(0x1e564)
17:31:04 Scanning directory: /etc/clamav/virusevent.d
17:31:04 Send ListDirectory(0x56bb7,0xffff,0xc,true)
17:31:04 Receive Success(0x56bb7)
17:31:04 Scanning directory: /etc/box
17:31:04 Send ListDirectory(0x1e565,0xffff,0xc,true)
17:31:04 Receive Success(0x1e565)
17:31:04 /etc/box/bbackupd.conf: will upload (modified since last sync)
17:31:04 Uploading complete file: /etc/box/bbackupd.conf
17:31:04 Send StoreFile(0x1e565,0x44e38cea68fc0,0x8dbf71bc59981ca, 
0,bbackupd.conf)
17:31:04 Read 4096 bytes at 4096, 1515 remain, eta 0s
17:31:04 Read 1515 bytes at 5611, 0 remain, eta 0s

This is where everything grinds to a halt, however it has over time  
got past this file and moved on - but as I only changed this file  
today this is where it now stops.....

All I did to bbackupd.conf was add KeepAliveTime = 60  and comment out  
the backup state file - in case either of these were causing the  
issue ...

On the server side here is what I see ...

May 27 17:28:57 pegasus Box Backup (bbstored)[11289]: WARNING: Message  
from child process 11300: Incoming connection from 79.123.17.250 port  
57982
May 27 17:28:57 pegasus Box Backup (bbstored)[11300]: Client  
certificate CN: BACKUP-7
May 27 17:28:57 pegasus Box Backup (bbstored)[11300]: Send block  
allocation size is 1024
May 27 17:28:57 pegasus Box Backup (bbstored)[11300]: NOTICE: Login  
from Client ID 0x00000007 Read/Write
May 27 17:32:39 pegasus Box Backup (bbstored)[11258]: WARNING:  
Exception thrown: ConnectionException(Conn_Protocol_Timeout) at  
Protocol.cpp(229)
May 27 17:32:41 pegasus Box Backup (bbstored)[11258]: ERROR: Error in  
child process, terminating connection: Connection Protocol_Timeout  
(Probably a network issue between client and server.) (7/41)

:(((

Matt