Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
You can install the perl module Module::Path to find the path for a module.
After installing, do this:
perl -e 'use Module::Path "module_path";
print(module_path("BackupPC::XS")."\n");'
Example output:
/usr/local/lib/x86_64-linux-gnu/perl/5.26.1/BackupPC/XS.pm
Now try as root and the BackupPC user to see the difference. Does the
BackupPC user have permission to access the version root uses?
You can also print the module search path with:
perl -e 'print join("\n", @INC),"\n"'
Does that differ between root and the BackupPC user?
Craig
On Thu, Jun 25, 2020 at 9:48 AM Les Mikesell wrote:
> > The system got itself into this state from a standard yum update.
>
> That's why you want to stick to all packaged modules whenever
> possible. Over time, dependencies can change and the packaged
> versions will update together. You can probably update a cpan module
> to the correct version manually but you need to track all the version
> dependencies yourself. There are some different approaches to
> removing modules: https://www.perlmonks.org/?node_id=1134981
>
>
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] FEATURE REQUEST: More robust error reporting/emailing
- Le 25 Juin 20, à 15:42, backu...@kosowsky.org a écrit :
>
> Helpful configurable options would include:
> - *Days* since last successful backup - *per host* configurable - as you
> may want to be more paranoid about certain hosts versus others while
> others you may not care if it gets backed up regularly and you want
> to avoid the "nag" emails
>
> - *Number* of errors in last backup - *per host/per share*
> configurable - Idea being that some hosts may naturally have more
> errors due to locked files or fleeting files while other shares may
> be rock stable. (Potentially, one could even trigger on types of errors
> or you could exclude certain types of errors from the count)
>
> - *Percent* of files changed/added/deleted in last backup relative to
> prior backup - *per host/per share* configurable - idea here being
> that you want to be alerted if something unexpected has changed on
> the host which could even be dramatic if a share has been damaged or
> deleted or not mounted etc.
>
> Just a thought starter... I'm sure others may have other ideas to add...
>
I do all of this with Zabbix and some custom scripts :
https://git.fws.fr/fws/zabbix-agent-addons/src/branch/master/zabbix_scripts
* Alert if no backup since $Conf{EMailNotifyOldBackupDays}
* Alert if Xfer error > threshold
* Alert if new file size seems abnormal (too small or too big)
* Graph some data about space consumption/compression efficiency
Maybe it can help ;-)
++
--
[ https://www.firewall-services.com/ ]
Daniel Berteaud
FIREWALL-SERVICES SAS, La sécurité des réseaux
Société de Services en Logiciels Libres
Tél : +33.5 56 64 15 32
Matrix: @dani:fws.fr
[ https://www.firewall-services.com/ | https://www.firewall-services.com ]
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
> The system got itself into this state from a standard yum update. That's why you want to stick to all packaged modules whenever possible. Over time, dependencies can change and the packaged versions will update together. You can probably update a cpan module to the correct version manually but you need to track all the version dependencies yourself. There are some different approaches to removing modules: https://www.perlmonks.org/?node_id=1134981 ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
The system got itself into this state from a standard yum update. I only intervened once the BackupPC service failed to start after a reboot. >From what I found it looked like updating to .62 was the right direction. And >now I learned that there is no way to cleanly uninstall a cpan module. Ugh. So am I looking at a purge and a reinstall? If so, is there a guide on how to do that? Thanks for any tips! From: Richard Shaw Sent: Thursday, June 25, 2020 10:08 AM To: General list for user discussion, questions and support Subject: Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released On Thu, Jun 25, 2020 at 10:02 AM Mike Hughes mailto:m...@visionary.com>> wrote: Certainly a mismatch. Here's my output. Hopefully it formats cleanly. How can I fix this while waiting for the patch to roll out? Well, I'm not sure how to clean up the mess, but the problem is simple. You don't want to mix manual cpan installs with packages. There's no reason to use cpan at all if you're using my packages. My guess is the cpan installs are going into /usr/local which is overriding the package installs. Thanks, Richard ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] FEATURE REQUEST: More robust error reporting/emailing
Daily report: https://github.com/moisseev/BackupPC_report From: backu...@kosowsky.org Sent: Thursday, June 25, 2020 8:42 AM To: General list for user discussion Subject: [BackupPC-users] FEATURE REQUEST: More robust error reporting/emailing It would be great if there could be a way to have a host/share configurable way to trigger emails based on certain types of errors or changes. The goal being to avoid the "complacency" of backups continuing to run but not being aware of either continuing backup errors or unexpected changes to the underlying system. Otherwise, one must rely on regular and pretty detailed review of logs and stats. Helpful configurable options would include: - *Days* since last successful backup - *per host* configurable - as you may want to be more paranoid about certain hosts versus others while others you may not care if it gets backed up regularly and you want to avoid the "nag" emails - *Number* of errors in last backup - *per host/per share* configurable - Idea being that some hosts may naturally have more errors due to locked files or fleeting files while other shares may be rock stable. (Potentially, one could even trigger on types of errors or you could exclude certain types of errors from the count) - *Percent* of files changed/added/deleted in last backup relative to prior backup - *per host/per share* configurable - idea here being that you want to be alerted if something unexpected has changed on the host which could even be dramatic if a share has been damaged or deleted or not mounted etc. Just a thought starter... I'm sure others may have other ideas to add... ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
On Thu, Jun 25, 2020 at 10:02 AM Mike Hughes wrote: > Certainly a mismatch. Here's my output. Hopefully it formats cleanly. How > can I fix this while waiting for the patch to roll out? > Well, I'm not sure how to clean up the mess, but the problem is simple. You don't want to mix manual cpan installs with packages. There's no reason to use cpan at all if you're using my packages. My guess is the cpan installs are going into /usr/local which is overriding the package installs. Thanks, Richard ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
Certainly a mismatch. Here's my output. Hopefully it formats cleanly. How can I
fix this while waiting for the patch to roll out?
# head /usr/share/BackupPC/bin/BackupPC -n1
#!/usr/bin/perl
# grep "use\ lib" /usr/share/BackupPC/bin/BackupPC
use lib "/usr/share/BackupPC/lib";
# which cpan
/bin/cpan
# /usr/bin/perl -e 'use BackupPC::XS; print("$BackupPC::XS::VERSION\n")'
0.57
# cpan install BackupPC::XS
...
# /usr/bin/perl -e 'use BackupPC::XS; print("$BackupPC::XS::VERSION\n")'
0.62
# su backuppc -
$ /usr/bin/perl -e 'use BackupPC::XS; print("$BackupPC::XS::VERSION\n")'
0.57
$ cpan install BackupPC::XS
...
ERROR: Can't create '/root/perl5/lib/perl5/x86_64-linux-thread-multi/BackupPC'
$ /usr/bin/perl -e 'use BackupPC::XS; print("$BackupPC::XS::VERSION\n")'
0.57
From: Richard Shaw
Sent: Wednesday, June 24, 2020 12:42 PM
To: General list for user discussion, questions and support
Cc: Craig Barratt
Subject: Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
On Wed, Jun 24, 2020 at 12:19 PM Craig Barratt via BackupPC-users
mailto:backuppc-users@lists.sourceforge.net>>
wrote:
Mike,
It's possible you have two different versions of perl installed, or for some
reason the BackupPC user is seeing an old version of BackupPC::XS.
Try some of the suggestions here:
https://github.com/backuppc/backuppc/issues/351.
Yes, I just did a fresh install and didn't have any issues (with BackupPC-XS).
I DID find that /var/run/BackupPC is not created by the package and cannot be
created automatically since BackupPC is run as the backuppc user. Looking into
that now.
Thanks,
Richard
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
[BackupPC-users] FEATURE REQUEST: More robust error reporting/emailing
It would be great if there could be a way to have a host/share configurable way to trigger emails based on certain types of errors or changes. The goal being to avoid the "complacency" of backups continuing to run but not being aware of either continuing backup errors or unexpected changes to the underlying system. Otherwise, one must rely on regular and pretty detailed review of logs and stats. Helpful configurable options would include: - *Days* since last successful backup - *per host* configurable - as you may want to be more paranoid about certain hosts versus others while others you may not care if it gets backed up regularly and you want to avoid the "nag" emails - *Number* of errors in last backup - *per host/per share* configurable - Idea being that some hosts may naturally have more errors due to locked files or fleeting files while other shares may be rock stable. (Potentially, one could even trigger on types of errors or you could exclude certain types of errors from the count) - *Percent* of files changed/added/deleted in last backup relative to prior backup - *per host/per share* configurable - idea here being that you want to be alerted if something unexpected has changed on the host which could even be dramatic if a share has been damaged or deleted or not mounted etc. Just a thought starter... I'm sure others may have other ideas to add... ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
