[Box Backup] how to properly use snapshot backups?

Chris Wilson chris at qwirx.com
Fri Apr 18 21:41:51 BST 2014


Hi Brendon,

On Fri, 18 Apr 2014, Brendon Baumgartner wrote:

> Apr 18 10:01:28 hosting bbackupd[12635]: NOTICE: Box Backup Client vtrunk_3341, (c) Ben Summers and contributors 2003-2014
> Apr 18 10:01:28 hosting bbackupd[12637]: NOTICE: Starting daemon, version: trunk_3341
> Apr 18 10:01:28 hosting bbackupd[12637]: NOTICE: Using configuration file: /etc/boxbackup/bbackupd.conf
> Apr 18 10:01:41 hosting bbackupctl[12658]: Using configuration file /etc/boxbackup/bbackupd.conf
> Apr 18 10:01:41 hosting bbackupctl[12658]: NOTICE: state 0 Idle
> Apr 18 10:01:41 hosting bbackupd[12637]: ERROR: Failed to write to socket: Broken pipe (32)
> Apr 18 10:01:41 hosting bbackupd[12637]: WARNING: Exception thrown: ConnectionException(Conn_SocketWriteError) at SocketStream.cpp(313)
> Apr 18 10:01:41 hosting bbackupd[12637]: NOTICE: Failed to write to command socket: Connection SocketWriteError (Probably a network issue between client and server.)

Did this only happen once? It looks a bit like bbackupd tried to write 
something to the connected bbackupctl client, for example notifying it 
about a sync start or finish, just at the same time that the client was 
disconnecting because it already had what it wanted. This could happen 
very occasionally, randomly, and should not be a cause for concern, 
because bbackupd should ignore the error.

If it happened more than once this morning, OR there is no obvious cause 
(e.g. a backup didn't start immediately afterwards), OR the daemon died 
instead of ignoring the SocketWriteError, please let me know.

Cheers, Chris.
-- 
_____ __     _
\  __/ / ,__(_)_  | Chris Wilson <chris+sig at qwirx.com> Cambs UK |
/ (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Ruby/Perl/SQL Developer |
\__/_/_/_//_/___/ | We are GNU : free your mind & your software |



More information about the Boxbackup mailing list