Re: [BackupPC-users] A Perl error?
No, that is different path. It is really just in the configuration folder, not with the backup data. Jan On 04.09.2023 14:57, Mike Flannigan wrote: Does that jive with these notes from the config.pl file? I think maybe No. # Configuration settings can also be specified on a per-PC basis. # Simply put the relevant settings in a config.pl file in the # PC's backup directory (ie: in __TOPDIR__/pc/hostName). # All configuration settings in the second, third and fourth # groups can be overridden by the per-PC config.pl file. It seems like config.pl should be in a hostName directory. Mike On 9/3/23 07:42, backuppc-users-requ...@lists.sourceforge.net wrote: Hi, so I finally cracked it. I have no idea, how I happend to be in the original state at the first place... The problem was, that the host configuration files were not in "pc" folder next to the config.pl Cheers, Jan ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi, so I finally cracked it. I have no idea, how I happend to be in the original state at the first place... The problem was, that the host configuration files were not in "pc" folder next to the config.pl Cheers, Jan On 31.08.2023 18:07, Jan Stransky wrote: Hi, sorry for slow responses. My attention is all over the place lately... And rather worryingly, backups are not high on the list :-D Quickly on docker: My primary reason is to reduce mess in the OS, especially since NAS is supposed to run also other things. And it makes moving between different HW easier, which I actually successfully employed even with BackupPC. "I started to notice" was a bit lyrical expression, sorry about that :-), I started noticing it while I was trying to figure out why BPC does not run out of sudden. Also, I saw the same error associated with other files, like when I got BPC half-way running with the host configuration files. Googling lead me to mentioning to similar error in other projects, from which I concluded, that it might be an issue with Perl version or something. I did read the scripts within the repository. The configure.pl is run from with in files/entrypoint.sh, line 58. From what I can see it basically set paths to stuff. As far as I can tell, the configure.pl is stock from BPC repository. I have now some hints, that there are problems outside BPC. I will let you know if I find something interesting... Jan On 13. 08. 23 21:13, Kenneth Porter wrote: On 8/13/2023 8:34 AM, G.W. Haywood via BackupPC-users wrote: First off I've never run BackupPC on anything except bare metal. As far as I can remember I haven't even tried to run it in a VM let alone using Docker. You're using somebody else's docker installation and I can imagine that things could go wrong which have nothing to do with BackupPC itself. By using this form of installation you might be making it easy to install BackupPC if it works, but I don't think it's necessarily going to make it easy to troubleshoot things if it doesn't. Looking at 'Dockerfile' in .../adferrand/docker-backuppc.git makes me ask more questions than it answers for me. I concur with the rest of your analysis and questions. But I can see the value of a Docker image. It's no worse than running on some unusual Linux distro. Containers and VMs let an app isolate itself from the package choices of the host OS, relying solely on the kernel. It's why Snap is making inroads against traditional RPM and dpkg packaging systems. The older systems are fine for keeping the underlying system stable, but not so good for apps that use bleeding-edge libraries. The new container-based packaging helps separate responsibilities between OS libraries and app libraries. Of course, the end-user/administrator then has to figure out where to send problem reports: To the distro/container maintainer or the app developer. This does look like a packaging issue and not an issue with the app. So I'd recommend opening an issue on GitHub against the container project. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi, sorry for slow responses. My attention is all over the place lately... And rather worryingly, backups are not high on the list :-D Quickly on docker: My primary reason is to reduce mess in the OS, especially since NAS is supposed to run also other things. And it makes moving between different HW easier, which I actually successfully employed even with BackupPC. "I started to notice" was a bit lyrical expression, sorry about that :-), I started noticing it while I was trying to figure out why BPC does not run out of sudden. Also, I saw the same error associated with other files, like when I got BPC half-way running with the host configuration files. Googling lead me to mentioning to similar error in other projects, from which I concluded, that it might be an issue with Perl version or something. I did read the scripts within the repository. The configure.pl is run from with in files/entrypoint.sh, line 58. From what I can see it basically set paths to stuff. As far as I can tell, the configure.pl is stock from BPC repository. I have now some hints, that there are problems outside BPC. I will let you know if I find something interesting... Jan On 13. 08. 23 21:13, Kenneth Porter wrote: On 8/13/2023 8:34 AM, G.W. Haywood via BackupPC-users wrote: First off I've never run BackupPC on anything except bare metal. As far as I can remember I haven't even tried to run it in a VM let alone using Docker. You're using somebody else's docker installation and I can imagine that things could go wrong which have nothing to do with BackupPC itself. By using this form of installation you might be making it easy to install BackupPC if it works, but I don't think it's necessarily going to make it easy to troubleshoot things if it doesn't. Looking at 'Dockerfile' in .../adferrand/docker-backuppc.git makes me ask more questions than it answers for me. I concur with the rest of your analysis and questions. But I can see the value of a Docker image. It's no worse than running on some unusual Linux distro. Containers and VMs let an app isolate itself from the package choices of the host OS, relying solely on the kernel. It's why Snap is making inroads against traditional RPM and dpkg packaging systems. The older systems are fine for keeping the underlying system stable, but not so good for apps that use bleeding-edge libraries. The new container-based packaging helps separate responsibilities between OS libraries and app libraries. Of course, the end-user/administrator then has to figure out where to send problem reports: To the distro/container maintainer or the app developer. This does look like a packaging issue and not an issue with the app. So I'd recommend opening an issue on GitHub against the container project. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/ ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
On 8/13/2023 8:34 AM, G.W. Haywood via BackupPC-users wrote: First off I've never run BackupPC on anything except bare metal. As far as I can remember I haven't even tried to run it in a VM let alone using Docker. You're using somebody else's docker installation and I can imagine that things could go wrong which have nothing to do with BackupPC itself. By using this form of installation you might be making it easy to install BackupPC if it works, but I don't think it's necessarily going to make it easy to troubleshoot things if it doesn't. Looking at 'Dockerfile' in .../adferrand/docker-backuppc.git makes me ask more questions than it answers for me. I concur with the rest of your analysis and questions. But I can see the value of a Docker image. It's no worse than running on some unusual Linux distro. Containers and VMs let an app isolate itself from the package choices of the host OS, relying solely on the kernel. It's why Snap is making inroads against traditional RPM and dpkg packaging systems. The older systems are fine for keeping the underlying system stable, but not so good for apps that use bleeding-edge libraries. The new container-based packaging helps separate responsibilities between OS libraries and app libraries. Of course, the end-user/administrator then has to figure out where to send problem reports: To the distro/container maintainer or the app developer. This does look like a packaging issue and not an issue with the app. So I'd recommend opening an issue on GitHub against the container project. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi there,
On Sun, 13 Aug 2023, Jan Stransky wrote:
On Sun, 23 Jul 2023, G.W. Haywood via BackupPC-users wrote:
On Sun, 23 Jul 2023, Jan Stransky wrote:
I started to notice following error. Does any one have any ideas? It
seems to be more related to configure.pl genrerator, rather than the
actual configuration.
Can't use string ("1") as a HASH ref while "strict refs" in use at
configure.pl line 742.
...
What version of BackupPC are you using, and was it installed from a
package or did you install it manually for example from some tarball?
If the latter, please tell us what it was and where it came from.
I am actually not aware of doing any modifications. I run the BackupPC
in as a docker image, and the only thing I did was rebuild the image so
the underlaying system was updated. The BPC was running just fine by
that point. Of course, I cannot exclude a file corruption.
I am using this, but up-to-date Alpine (3.18):
https://github.com/adferrand/docker-backuppc.git
BackupPC is 4.4.0, BackupPC_XS 0.62 and Rsunc_bpc is 3.1.3.0
First off I've never run BackupPC on anything except bare metal. As
far as I can remember I haven't even tried to run it in a VM let alone
using Docker. You're using somebody else's docker installation and I
can imagine that things could go wrong which have nothing to do with
BackupPC itself. By using this form of installation you might be
making it easy to install BackupPC if it works, but I don't think it's
necessarily going to make it easy to troubleshoot things if it doesn't.
Looking at 'Dockerfile' in .../adferrand/docker-backuppc.git makes me
ask more questions than it answers for me.
You said "I started to notice" which says to me you've been using some
procedure on at least a semi-regular basis which did *not* produce the
error, and then, from some point onward, it did. If that's the case
please can you explain this procedure for us?
The configure.pl script is usually run only to install BackupPC, and I
wouldn't expect that anyone would run it routinely. For example it
doesn't even exist on my BackupPC server, as it's my usual practice to
deleted the source trees after running an installation. The script is
able to recognize some command-line arguments; presumably in your case
the script is being run by something from the github package which you
mentioned. Do you know how and with what arguments configure.pl ran?
Have you read the script's 'man' page and/or tried to run it yourself?
Did the script leave you with a log file? If so, it might help if we
can see it.
Please also show us the few lines around line 742 in your configure.pl
script. I'm not sure we can know what's there without duplicating
your setup, and that would be prohibitively time-consuming - unless
someone on the list happens to be using the same docker image and OS.
Did you check that BackupPC was not running before configure.pl ran?
--
73,
Ged.
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi,
I am actually not aware of doing any modifications. I run the BackupPC
in as a docker image, and the only thing I did was rebuild the image so
the underlaying system was updated. The BPC was running just fine by
that point. Of course, I cannot exclude a file corruption.
I am using this, but up-to-date Alpine (3.18):
https://github.com/adferrand/docker-backuppc.git
BackupPC is 4.4.0, BackupPC_XS 0.62 and Rsunc_bpc is 3.1.3.0
Thanks,
Jan
On 7/23/23 19:15, G.W. Haywood via BackupPC-users wrote:
Hi there,
On Sun, 23 Jul 2023, Jan Stransky wrote:
I started to notice following error. Does any one have any ideas? It
seems to be more related to configure.pl genrerator, rather than the
actual configuration.
Cheers,
Jan
Can't use string ("1") as a HASH ref while "strict refs" in use at
configure.pl line 742.
Let's try that again :)
What version of BackupPC are you using, and was it installed from a
package or did you install it manually for example from some tarball?
If the latter, please tell us what it was and where it came from.
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi,
I don't usually wade in to discussions like these, but as I understand
perl fairly well, I feel the need to point out that you are on the
wrong track G.W.Haywood.The error message does not refer to line 742 of
config.pl, but to that of configure.pl, presumably the script which
reads config.pl.Unless Jan has modified configure.pl, the actual error
is still likely to be in config.pl.Jan please give more information -
you said 'I started to notice following error.' - following what?Did
you make a configuration change just before you noticed the error?Have
you had BPC working, or are you still tuning the configuration?Are you
using the web interface to do the configuration, or are you editing
config.pl by hand?Which version of BPC are you using?Without further
information, it's unlikely that other people are going to be able to
help you.
Kind regards,Peter Major
On Sun, 2023-07-23 at 13:59 +0100, G.W. Haywood via BackupPC-users
wrote:
> Hi there,
> On Sun, 23 Jul 2023, Jan Stransky wrote:
> > I started to notice following errorCan't use string ("1") as a
> > HASH ref while "strict refs" in use at configure.pl line 742
>
> Looks like you broke it.
> Please let us see what you have around line 742 of configure.pl.
> In the vanilla configure.pl that would be somewhere around the
> partwhich sets up things to be backed up and/or ignored, but if
> yourversion of config.pl has been heavily modified it could be
> anything.This is from a current config.pl here:
> 8<---
> ---$ cat -n /etc/BackupPC/config.pl | head -n 770 | tail -n
> 45726 # Examples:727 #$Conf{BackupFilesExclude} =
> '/temp';728 #$Conf{BackupFilesExclude} = ['/temp']; #
> same as first example729 #$Conf{BackupFilesExclude} =
> ['/temp', '/winnt/tmp'];730 #$Conf{BackupFilesExclude} =
> {731 # 'c' => ['/temp', '/winnt/tmp'], # these are
> for 'c' share732 # 'd' => ['/junk', '/dont_back_this_up'],
> # these are for 'd'
> share733 #};734 #$Conf{BackupFilesExclude} =
> {735 # 'c' => ['/temp', '/winnt/tmp'], # these are
> for 'c' share736 # '*' => ['/junk', '/dont_back_this_up'],
> # these are for other
> shares737 #};738 #739 $Conf{BackupFilesExclude} =
> undef;740741 #742 # PCs that are always or often on the
> network can be backed up after743 # hours, to reduce PC, network
> and server load during working hours. For744 # each PC a count
> of consecutive good pings is maintained. Once a PC has745 # at
> least $Conf{BlackoutGoodCnt} consecutive good pings it is
> subject746 # to "blackout" and not backed up during hours and
> days specified by747 #
> $Conf{BlackoutPeriods}.748 #749 # To allow for periodic
> rebooting of a PC or other brief periods when a750 # PC is not
> on the network, a number of consecutive bad pings is
> allowed751 # before the good ping count is reset. This parameter
> is752 # $Conf{BlackoutBadPingLimit}.753 #754 # Note
> that bad and good pings don't occur with the same interval. If
> a755 # machine is always on the network, it will only be pinged
> roughly once756 # every $Conf{IncrPeriod} (eg: once per day). So
> a setting for757 # $Conf{BlackoutGoodCnt} of 7 means it will
> take around 7 days for a758 # machine to be subject to blackout.
> On the other hand, if a ping is759 # failed, it will be retried
> roughly every time BackupPC wakes up, eg,760 # every one or two
> hours. So a setting for $Conf{BlackoutBadPingLimit} of761 # 3
> means that the PC will lose its blackout status after 3-6 hours
> of762 # unavailability.763 #764 # To disable the
> blackout feature set $Conf{BlackoutGoodCnt} to a negative765 #
> value. A value of 0 will make all machines subject to
> blackout. But766 # if you don't want to do any backups during
> the day it would be easier767 # to just set
> $Conf{WakeupSchedule} to a restricted
> schedule.768 #769 $Conf{BlackoutBadPingLimit} =
> 3;770 $Conf{BlackoutGoodCnt} = 7;8<--
>
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi there,
On Sun, 23 Jul 2023, Jan Stransky wrote:
I started to notice following error. Does any one have any ideas? It
seems to be more related to configure.pl genrerator, rather than the
actual configuration.
Cheers,
Jan
Can't use string ("1") as a HASH ref while "strict refs" in use at
configure.pl line 742.
Let's try that again :)
What version of BackupPC are you using, and was it installed from a
package or did you install it manually for example from some tarball?
If the latter, please tell us what it was and where it came from.
--
73,
Ged.
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi there, On Sun, 23 Jul 2023, Peter Major wrote: I don't usually wade in to discussions like these, but as I understand perl fairly well, I feel the need to point out that you are on the wrong track G.W.Haywood.The error message does not refer to line 742 of config.pl, but to that of configure.pl, presumably the script which reads config.pl. Ah, yes, you're quite right. Apologies for my inexcusable carelessness. -- 73, Ged. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
Re: [BackupPC-users] A Perl error?
Hi there,
On Sun, 23 Jul 2023, Jan Stransky wrote:
I started to notice following error.
...
Can't use string ("1") as a HASH ref while "strict refs" in use at configure.pl
line 742.
...
Looks like you broke it.
Please let us see what you have around line 742 of configure.pl.
In the vanilla configure.pl that would be somewhere around the part
which sets up things to be backed up and/or ignored, but if your
version of config.pl has been heavily modified it could be anything.
This is from a current config.pl here:
8<--
$ cat -n /etc/BackupPC/config.pl | head -n 770 | tail -n 45
726 # Examples:
727 #$Conf{BackupFilesExclude} = '/temp';
728 #$Conf{BackupFilesExclude} = ['/temp']; # same as first example
729 #$Conf{BackupFilesExclude} = ['/temp', '/winnt/tmp'];
730 #$Conf{BackupFilesExclude} = {
731 # 'c' => ['/temp', '/winnt/tmp'], # these are for 'c'
share
732 # 'd' => ['/junk', '/dont_back_this_up'], # these are for 'd'
share
733 #};
734 #$Conf{BackupFilesExclude} = {
735 # 'c' => ['/temp', '/winnt/tmp'], # these are for 'c'
share
736 # '*' => ['/junk', '/dont_back_this_up'], # these are for other
shares
737 #};
738 #
739 $Conf{BackupFilesExclude} = undef;
740
741 #
742 # PCs that are always or often on the network can be backed up after
743 # hours, to reduce PC, network and server load during working hours. For
744 # each PC a count of consecutive good pings is maintained. Once a PC has
745 # at least $Conf{BlackoutGoodCnt} consecutive good pings it is subject
746 # to "blackout" and not backed up during hours and days specified by
747 # $Conf{BlackoutPeriods}.
748 #
749 # To allow for periodic rebooting of a PC or other brief periods when a
750 # PC is not on the network, a number of consecutive bad pings is allowed
751 # before the good ping count is reset. This parameter is
752 # $Conf{BlackoutBadPingLimit}.
753 #
754 # Note that bad and good pings don't occur with the same interval. If a
755 # machine is always on the network, it will only be pinged roughly once
756 # every $Conf{IncrPeriod} (eg: once per day). So a setting for
757 # $Conf{BlackoutGoodCnt} of 7 means it will take around 7 days for a
758 # machine to be subject to blackout. On the other hand, if a ping is
759 # failed, it will be retried roughly every time BackupPC wakes up, eg,
760 # every one or two hours. So a setting for $Conf{BlackoutBadPingLimit}
of
761 # 3 means that the PC will lose its blackout status after 3-6 hours of
762 # unavailability.
763 #
764 # To disable the blackout feature set $Conf{BlackoutGoodCnt} to a
negative
765 # value. A value of 0 will make all machines subject to blackout. But
766 # if you don't want to do any backups during the day it would be easier
767 # to just set $Conf{WakeupSchedule} to a restricted schedule.
768 #
769 $Conf{BlackoutBadPingLimit} = 3;
770 $Conf{BlackoutGoodCnt} = 7;
8<--
--
73,
Ged.
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
