Control: tag -1 + moreinfo Hi,
Thomas D: > 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]: [email protected]: 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]: [email protected]: Unit > entered failed state. > 2017-10-23T01:00:15.796409+02:00 fer systemd[1]: [email protected]: 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 [email protected] failed with > 'failed' > 2017-10-23T01:00:21.594947+02:00 fer systemd[1]: [email protected]: 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]: [email protected]: 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 [email protected] 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. Can you please share the output of `backupninja --now --debug'? (Make sure it does not contain any password :) Cheers, -- intrigeri
