moin moin,
BackupPC's error reporting really, really sucks. It's almost as bad as the
old mac numbered bombs and oracle errors, except at least they give you
error numbers that don't mean anything.
So, when trying to debug why BackupPC is failing just safe yourself time
and aggravation by trying to run the backup by hand.
BackupPC_dump appears to be the work horse. Ah, but no manpage :(. And -h
and --help don't help. Oooh, it's a perl script and the top of it explains
usage.
Via web searching I started using -v for verbosity and -f for a full dump
in my testing.
sudo -u backuppc /usr/share/backuppc/bin/BackupPC_dump -v -f
somehost 2>&1 | tee /var/tmp/backuppc.somehost.2008Jan20.out
Did that for a host just now and it turns out the host's config file had
an error. Funny since the log files have been indicating it's an SSH
problem starting a GTK program. Why is a daemon doing anything that could
fall back to an interactive GUI application?
For the hosts for which BackupPC has been working it's been working quite
well. For the hosts for which it isn't working...
ciao,
der.hans
--
# https://www.LuftHans.com/ http://www.CiscoLearning.org/
# HERE LIES LESTER MOORE
# SHOT 4 TIMES WITH A .44
# NO LES
# NO MOORE
# -- tombstone, in Tombstone, AZ
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)