Package: backupninja
Version: 1.0.1-2
Severity: normal
Dear Maintainer,
I have been using backupninja for a long time and it is really helpful.
After upgrading to Debian 9 I started seing a lot of errors such as
these in my syslog:
2017-10-23T01:00:15.795982+02:00 fer systemd[1]: user@500.service: Start
request repeated too quickly.
2017-10-23T01:00:15.796132+02:00 fer systemd[1]: Failed to start User
Manager for UID 500.
2017-10-23T01:00:15.796271+02:00 fer systemd[1]: user@500.service: Unit
entered failed state.
2017-10-23T01:00:15.796409+02:00 fer systemd[1]: user@500.service: Failed
with result 'start-limit-hit'.
2017-10-23T01:00:15.796702+02:00 fer su[11455]: pam_systemd(su:session):
Failed to create session: Start job for unit user@500.service failed with
'failed'
2017-10-23T01:00:21.594947+02:00 fer systemd[1]: user@500.service: Start
request repeated too quickly.
2017-10-23T01:00:21.595070+02:00 fer systemd[1]: Failed to start User
Manager for UID 500.
2017-10-23T01:00:21.595212+02:00 fer systemd[1]: user@500.service: Failed
with result 'start-limit-hit'.
2017-10-23T01:00:21.596172+02:00 fer su[11486]: pam_systemd(su:session):
Failed to create session: Start job for unit user@500.service failed with
'failed'
A bit of investigation with help from the IRC lead to the conclusion
that this is caused by backupninja's postgresql jobs. Backupninja
includes ninjahelper - a tool that makes it easier to create backup jobs
for backupninja. Including dump jobs for various RDBMS.
The above errors seem to be caused by the PG dump job running via cron.
Backupninja seems to be running via cron every hours. And when it
notices that some backup job is to be run, it starts the appropriate
backup job. Something seems to go wrong when it does this for the PG
dump job. Maybe it is due to the way it uses su/sudo - I am not sure.
But it does give a lot of noise in the syslog.
I have tried deleting the PG dump jobs I had that was created in Debian
8 and then create a new one using ninjahelper. The hope was that maybe
there were some old stuff in the debian 8 version that did not work in
debian 9. However, the newly created job produces the same errors.
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_DK:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages backupninja depends on:
ii bash 4.4-5
ii dialog 1.3-20160828-2
ii gawk 1:4.1.4+dfsg-1
ii mailutils [mailx] 1:3.1.1-1
ii mawk 1.3.3-17+b3
backupninja recommends no packages.
Versions of packages backupninja suggests:
ii bzip2 1.0.6-8.1
ii debconf-utils 1.5.61
ii duplicity 0.7.11-1
pn genisoimage <none>
ii hwinfo 21.38-1
ii mdadm 3.4-4+b1
ii rdiff-backup 1.2.8-7
ii rsync 3.1.2-1
ii subversion 1.9.5-1+deb9u1
ii trickle 1.07-10+b1
pn wodim <none>
-- Configuration Files:
/etc/backupninja.conf [Errno 13] Permission denied: '/etc/backupninja.conf'
-- no debconf information
