The only change to my service file was to uncomment the group; both user and
group had been properly configured as backuppc. I had reloaded the daemon.
The service reads as follows:
[Unit]
Description=BackupPC server
After=syslog.target local-fs.target
[Service]
Type=simple
User=backuppc
Group=backuppc
ExecStart=/usr/local/BackupPC/bin/BackupPC
ExecReload=/bin/kill -HUP $MAINPID
RuntimeDirectory=BackupPC
PIDFile=/var/run/BackupPC/BackupPC.pid
KillSignal=SIGTERM
Restart=always
RestartSec=1
[Install]
WantedBy=multi-user.target
the current status is:
● backuppc.service - BackupPC server
Loaded: loaded (/etc/systemd/system/backuppc.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2022-11-05 12:15:29 PDT; 5h 56min ago
Main PID: 598214 (BackupPC)
Tasks: 1 (limit: 37524)
Memory: 8.6M
CPU: 84ms
CGroup: /system.slice/backuppc.service
└─598214 /usr/bin/perl /usr/local/BackupPC/bin/BackupPC
Nov 05 12:15:29 eagle systemd[1]: Started BackupPC server.
Thanx for the suggestions. Any idea where to look to see why the system wants
to run it as ID 33?
________________________________
From: Rob Sheldon <r...@robsheldon.com>
Sent: Saturday, November 5, 2022 17:35
To: backuppc-users@lists.sourceforge.net <backuppc-users@lists.sourceforge.net>
Subject: Re: [BackupPC-users] Setuid problem
On Fri, Nov 4, 2022, at 11:54 AM, Dave Bachmann wrote:
>
> I am running into the setuid problem, eg. when running it I receive the
> following message: "Error: Wrong user: my userid is 33, instead of
> 117(backuppc)" where userid 33 = www-data.
>
> /etc/systemd/system/backuppc.service has both user and group set to backuppc.
> BackupPC_Admin has the following attributes:
> -r-sr-xr-x 1 backuppc backuppc 3971 2022-11-03 10:38 BackupPC_Admin.
Just to verify: you mean that you changed the "User=" and "Group=" lines in the
"[Service]" section in your service file?
Did you "sudo systemctl daemon-reload" after changing these?
What does "sudo service backuppc status" say?
This really smells like a systemd execution problem to me. The only thing I see
BackupPC doing to verify its uid is checking the value of '$>' during startup;
if it thinks its process uid is 33, that's gotta be because systemd is invoking
it as that user.
_</email>_
Rob Sheldon
_______________________________________________
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/
