Hi
I want to backup some cluster that needs a script to know what
machine is the master. So this mean that i can not use the
ClientNameAlias directly, but i'm using it to define the cluster name
so i can use more freedom for the backup name.
As backuppc uses the netbios if the dns
Ah, I didn't update to 4.1.1, especially since If found the problem I didn't
want to change anything until I had it resolved. LOL
I also saw reference to creating a file in /etc/tmpfiles.d/BackupPC.conf
containing one line:
D /var/run/BackupPC 0775 root backuppc
This supposedly creates the file
Steve,
In 4.1.1 I added this directive to the systemd backuppc.service file:
RuntimeDirectory=BackupPC
which creates the /var/run/BackupPC directory just before it starts
BackupPC.
Craig
On Wed, Apr 12, 2017 at 12:45 PM, Steve Palm wrote:
> Looked at the code, ${RunDir} is the location, and
Looked at the code, ${RunDir} is the location, and its s a directory not a file.
Not sure why it couldn't be created, but I did so manually, changed ownership
to backuppc and it works.
Still don't know why it went wrong...
Steve
> On Apr 12, 2017, at 2:35 PM, Steve Palm wrote:
>
> Hello,
>
Hello,
I had a hard server crash, seems a RAM module went bad. After diagnosing and
getting it back up and running, BackupPC will no longer start. I simply get:
systemd[1]: Starting SYSV: Starts and stops the BackupPC server...
runuser[6605]: pam_unix(runuser:session): session opened for user ba
Here's status. It looks about the same other than that benign log entry
about the PID
# systemctl status backuppc
● backuppc.service - BackupPC server
Loaded: loaded (/etc/systemd/system/backuppc.service; enabled)
Active: active (running) since Wed 2017-04-12 18:13:58 UTC; 7s ago
Process:
Hi,
Sorin Srbu wrote on 2017-04-10 06:14:07 + [Re: [BackupPC-users] Excluding
folders from backup]:
> > From: Holger Parplies [mailto:wb...@parplies.de]
> > [...]
> >
> > Almost. In fact, an exclude for "*" is applied to all shares *which don't
> > have a specific exclude*. So, if you used,
On Wed, Apr 12, 2017 at 1:06 PM, Nicholas Hall wrote:
> Good question!
>
> I have an update: everything works fine when started via systemd when I
> change the unit file to Type=forking. Wondering how reproducible the
> problem is on other platforms...
>
I was going to ask about that but said,
Good question!
I have an update: everything works fine when started via systemd when I
change the unit file to Type=forking. Wondering how reproducible the
problem is on other platforms...
# /etc/systemd/system/backuppc.service
[Unit]
Description=BackupPC server
After=syslog.target local-fs.targ
Hmm... nothing jumping out at me there... I don't use SCGI so I'm not
familiar with it but systemd works fine on my CentOS 7 and Fedora boxes...
Now one thing to consider is that when systemd runs a process it's not in a
shell and doesn't get a standard environment... Are there any environment
var
On Wed, Apr 12, 2017 at 12:15 PM Richard Shaw wrote:
> May not help any but what about:
>
> (after systemd startup)
> # systemctl status backuppc
>
> # systemctl cat backuppc
>
# systemctl status backuppc
● backuppc.service - BackupPC server
Loaded: loaded (/etc/systemd/system/backuppc.servi
May not help any but what about:
(after systemd startup)
# systemctl status backuppc
and
# systemctl cat backuppc
Thanks,
Richard
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, S
Hi,
I provisioned a new backuppc server (built from git tag 4.1.1) on Debian
8. I'm using the systemd unit file for starting the BackupPC daemon.
Problem is the SCGI listener doesn't respond when BackupPC is started via
systemctl. Any thoughts?
Below you will find the failure case via systemd,
13 matches
Mail list logo
