Hi,
Something must have happened to the BackupPC package. I was today finally migrating my "production environment" from ClearOS 6 to ClearOS 7 after about half year testing... A few weeks ago I tested BackupPC and it worked. However now it does not (out of the box/Marketplace). The problem seems that the installer does not create a /var/run/BackupPC directory (with backuppc as owner) at installation time. Therefore the pid cannot be stored and starting BackupPC will fail.
Until this is fixed in the installer, here is a fix for those that ends up with the BackupPC which does not start after installation:
Install BackupPC from the marketplace.
The open a command window (as root) and run the following commands:
BackupPC shall now be up and running and functioning as it should.
/Fred
Something must have happened to the BackupPC package. I was today finally migrating my "production environment" from ClearOS 6 to ClearOS 7 after about half year testing... A few weeks ago I tested BackupPC and it worked. However now it does not (out of the box/Marketplace). The problem seems that the installer does not create a /var/run/BackupPC directory (with backuppc as owner) at installation time. Therefore the pid cannot be stored and starting BackupPC will fail.
Until this is fixed in the installer, here is a fix for those that ends up with the BackupPC which does not start after installation:
Install BackupPC from the marketplace.
The open a command window (as root) and run the following commands:
mkdir /var/run/BackupPC
chown backuppc:backuppc /var/run/BackupPC
systemctl stop backuppc
systemctl start backuppc
BackupPC shall now be up and running and functioning as it should.
/Fred
In BackupPC
Share this post:
Responses (10)
-
Accepted Answer
Hi,
I have now tested the new app-backuppc build from clearos-contribs-testing and it seems to work. The installer does not create the directory at installation time, so a server reboot is neccessary after the upgrade in order to get BackupPC going again. No other intervention is needed.
Peter, from my perspective you can push the new app-backuppc and app-backuppc-core to clearos-contribs !
/Fred -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Very nice catch Fredrik.
That's a bit of an ooops in the EPEL RPM. You should definitely file a bug report with EPEL/Red Hat (or we can do it if you wish). For now, we'll put a /usr/lib/tmpfiles.d/app-backuppc.conf in the app-backuppc package. I just quickly sanity checked that having identical tmpfiles.d configlet files (e.g. /usr/lib/tmpfiles.d/app-backuppc.conf and /usr/lib/tmpfiles.d/BackupPC.conf) is not a problem, so when the fixed BackupPC package comes along in EPEL, we can remove the tmpfiles configlet from app-backuppc package. -
Accepted Answer
Whilst not strictly on-topic, another problem with BackupPC is using rsyncd, get ping error like in:
https://bugzilla.redhat.com/show_bug.cgi?id=1079437
This is a bug in the BackupPC config.pl
This has undef PingPath configuration:
$Conf{PingPath} = undef;
Replacing this with /bin/ping does the trick:
$Conf{PingPath} = '/bin/ping';
Location [ View Larger Map ]
-
Accepted Answer
I was looking at the spec-file for BackupPC and it seems that it has not been adjusted to the fact that RHEL 7 / Centos 7 is now using systemd. However the spec file manually creates /var/run/BackupPC at installation, why it works until the first reboot. Since /var/run/ is temporary, all is gone after the reboot...
Found the below in one of the bugzilla bug reports for BackupPC but it seems that the maintainer did not see it. I guess the best thing is to file a new bug in bugzilla.
It will take me a while before I could test this. Maybe Tim or someone else could modify backuppc.spec and do a test build, and if it works issue a new bugzilla bug-report with a suggestion on how to solve it. I am not sure if ClearOS7/Centos7 is also being identified with "RHEL" in the example below, or if the "if-statement" need to be modified a bit?
Orion Poplawski 2015-08-18 16:09:38 EDT
Note that EL7 is systemd, so you should have:
%if 0%{?fedora} || 0%{?rhel} >= 7
%global _with_tmpfilesd 1
%global _with_systemd 1
%endif
/Fred -
Accepted Answer
Hi,
My version of BackupPC (on a fresh ClearOS 7 community):
BackupPC-3.3.1-1.el7.x86_64
app-backuppc-core-2.0.0-2.v7.noarch
app-backuppc-2.0.0-2.v7.noarch
I agree with Daryl, the server should be able to reboot without supervision. Sorry about that...
I guess the creation of the directory needs to be in the BackupPC startup-script just before creating the PID.
Note: I do have bzip2 installed so did not experience that. But maybe bzip2 was installed by some other package and the dependency in BackupPC is missing...
/Fred -
Accepted Answer
-
Accepted Answer
Hi Fred,
I can confirm your observation.
However, your fix only seems to work until the next reboot.
If your commands are run again, BackupPC will once again run (!).
At this stage, I'm not too fussed, as I rarely need to reboot ClearOS.
However, it is good engineering design a server doesn't need skilled intervention to start it correctly, so this needs to be eventually fixed.
I also found the Main Configuration Editor had errors:
Error: No save due to errors
Error: Bzip2Path must be a valid executable path
The open a command window (as root) and run the following commands:
yum -y install bzip2
Errors go away.
Looks like the installer needs to be fixed and the dependencies updated to include bzip2.
Location [ View Larger Map ]
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »