somerset backup is failing

since the reboot of the infrastructure, the somerset's backup is failing with this error:

mkdir: cannot create directory ‘/srv/remote-backups/postgres’: Permission denied

changed milestone to %MRO 2023

added activity::MRO label

assigned to @vsellier

related to %Install new racks in Rocquencourt

added state:wip label

changed the description

That's not actually a backup, "just" postgresql log rotation.

Maybe we should configure filebeat's postgresql module instead https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-postgresql.html

Ah, these are going to saam:/srv/storage/space/postgres-backups, which is on zfs (I thought it was on XFS), so it's probably just the nfs mount that failed (and poking at systemctl / mount -a is probably enough to fix them)

mentioned in commit swh/infra/puppet/puppet-swh-site@5a22c95d

mentioned in merge request swh/infra/puppet/puppet-swh-site!596 (merged)

mentioned in commit swh/infra/puppet/puppet-swh-site@7f5d6a99

The rotation was temporary fixed by adding the missing mountpoint in the fstab with olasd. The mr allows to manage the configuration via puppet.

mentioned in commit swh/infra/puppet/puppet-swh-site@64e23ce8

mentioned in commit swh/infra/puppet/puppet-swh-site@b43596c7

mentioned in commit swh/infra/puppet/puppet-swh-site@a94993e8

No more alert, all the fstab lines looks ok on belvedere and somerset

closed

removed state:wip label

added 1h of time spent at 2023-01-29

added 1h of time spent at 2023-01-30