[Box Backup] Parse Logfiles
Fri, 23 Mar 2007 22:45:27 +0100
that sounds really good. I get an compilation error:
Guards.h: In constructor 'FileHandleGuard<flags,
mode>::FileHandleGuard(const char*)': Guards.h:37: error: 'errno' was
mode>not declared in this scope
make: *** [../../release/lib/common/IOStream.o] Fehler 1
make: Leaving directory
make: *** [dep_modules] Fehler 2 make: Leaving directory
No time at the moment to search for the error, perhaps tomorrow.
Is it possible to build a patch with your changes for boxbackupp 0.10 ?
I would like to use that in production use.
Am Fri, 23 Mar 2007 00:06:04 +0000 (GMT)
schrieb Chris Wilson <email@example.com>:
> Hi Torsten,
> On Thu, 22 Mar 2007, Torsten Boob wrote:
> > i had the following error:
> > Exception caught (Connection Protocol_UnexpectedReply (Server
> > probably reported an error.) 7/47), reset state and waiting to
> > retry...
> > The error occurred because one backup location in bbackupd.conf was
> > listed twice.
> > My main problem is the following. The boxbackup server did not tell
> > me an error but a successfully login and logout of the client.
> > NotifySysAdmin.sh on the client was not called, too. So i have to
> > look at the logfiles frequently to not overlook an error.
> > How can i reliable get a notification when an error occurs ? Did
> > anybody write a program to filter the logfile ? Is it possible to
> > configure boxbackup, to call NotifySysAdmin.sh on every error ?
> > That would be the best solution for me.
> I think I have fixed this in my merge tree. If you have time and
> inclination, I'd be very grateful if you could test it and let me
> know if it solves your issue. Just checkout
> http://bbdev.fluffy.co.uk/svn/box/chris/merge using Subversion, run
> "./bootstrap" and then configure, make, etc. as normal.
> What I've done is to add a new sysadmin notification, "backup-error",
> which is called whenever a backup fails.
> You might get some false positives, especially if the connection
> between client and server is intermittent. Please let me know if
> this, or anything else, is a problem for you.
> With your help, I hope that this code can be merged into the trunk
> Cheers, Chris.