Database handlers produce su-related errors in logs
This was initially reported in DEBBUG-879664 against the pgsql handler on the Debian BTS, but I'm also seeing the same problem with the mysql one.
Basically, when backing up multiple smallish databases, su
is called many times in quick succession, leading to messages like this appearing in system logs:
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'