#11162 fix backups of db-datanommer02
Closed: Fixed with Explanation 2 years ago by kevin. Opened 2 years ago by kevin.

db-datanommer02 (timescaledb) is not being backed up currently.

The backup script fails with:

Mar 04 00:00:02 db-datanommer02.iad2.fedoraproject.org crond[3682654]: pam_sss(crond:account): system info: [The user account is locked on the server]
Mar 04 00:00:02 db-datanommer02.iad2.fedoraproject.org crond[3682654]: pam_sss(crond:account): Access denied for user postgres: 6 (Permission denied)
Mar 04 00:00:02 db-datanommer02.iad2.fedoraproject.org crond[3682654]: (postgres) PAM ERROR (Permission denied)
Mar 04 00:00:02 db-datanommer02.iad2.fedoraproject.org crond[3682654]: (postgres) FAILED to authorize user with PAM (Permission denied)

This is due to it using the ipa postgres user instead of a local one.

We need to fix this so it makes daily backups again, then add it to backups group.


Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

ok. This is now fixed.

I made a local user there and chowned all the files, then modified backups to pull from 02 instead of 01. ;)

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

2 years ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog