[Box Backup] Windows Boxbackup path configuration and eventlogs
Mon, 3 Nov 2008 17:23:08 -0800
> -----Original Message-----
> From: email@example.com
> On Behalf Of Chris Wilson
> Sent: Monday, November 03, 2008 5:02 PM
> To: firstname.lastname@example.org
> Subject: RE: [Box Backup] Windows Boxbackup path configuration and
> Hi Brendon,
> On Mon, 3 Nov 2008, Brendon Baumgartner wrote:
> > > > I'm using win32 build 1857, which I believe is the latest.
> > >
> > > It is the latest precompiled release for Windows, but the LogFile
> > > feature that I mentioned has been added since. I'm afraid I
> > > released a new Windows build with this feature.
> > Anytime soon? I'm not sure I want to get into compiling binaries for
> > windows.
> I've uploaded a new Windows binary build for the latest monthly
> which you can find here:
WOW! Thanks for this... looks like a release was due.
> > > > ERROR: Exception caught (Connection Protocol_UnexpectedReply
> > > > probably reported an error.) 7/47), reset state and waiting to
> > > > retry...
> > >
> > > This is bad, it probably means that something is wrong on the
> > > Did you get any error messages in the server log around this time?
> > I couldn't find that error in the eventlogs. I didn't note the time
> > before. Here are a bunch of errors listed on the server.
> > http://pastebin.com/mc816912
> On second thoughts I think this may have been caused by the account
> locked after the connection was killed due to a timeout.
> > > > ERROR: Exception caught (Connection TLSWriteFailed (Probably a
> > > > network issue between client and server.) 7/33), reset state and
> > > > waiting to retry...
> > >
> > > This may mean that the connection to the server timed out after 15
> > > minutes of inactivity. What is your MaximumDiffingTime and
> > > KeepAliveTime set to on the client?
> > MaximumDiffingTime is commented out
> > KeepAliveTime is commented out
> Please could you try enabling both of these?
> Set MaximumDiffingTime to 300 (seconds) for a start, and KeepAliveTime
> 60 (seconds).
> Using the new build, you should be able to log to a file with the
> setting in the configuration, and set the level used for this logging
> LogFileLevel (e.g. =3D debug).
Okay. I'll give all of this a try and report back soon!