Before backup error #26

Closed
opened 2024-07-22 23:48:57 +02:00 by ProfessionalUwU · 3 comments
Collaborator

When executing update I got this error today:

Trying to lock the pacman db. Please enter your password.
Password: 
mv: cannot stat '/tmp/update/before-backup_2024-07-22T23:45:03+02:00.tar.zst.new': No such file or directory

/tmp/update looks like this:

after-backup_2024-07-22T23:45:03+02:00
before-backup_2024-07-22T23:45:03+02:00

If you need more info let me know!

When executing update I got this error today: ``` Trying to lock the pacman db. Please enter your password. Password: mv: cannot stat '/tmp/update/before-backup_2024-07-22T23:45:03+02:00.tar.zst.new': No such file or directory ``` `/tmp/update` looks like this: ``` after-backup_2024-07-22T23:45:03+02:00 before-backup_2024-07-22T23:45:03+02:00 ``` If you need more info let me know!
ProfessionalUwU added the
bug
label 2024-07-22 23:48:57 +02:00
AustrianToast was assigned by ProfessionalUwU 2024-07-22 23:48:57 +02:00

should work now

should work now
Author
Collaborator

Works on my end now

Works on my end now
Author
Collaborator

Backup failure incident report

Monday 22 July

Summary

At 23:48 GMT+2 an issue was spotted with the backup function of update. This caused backups to stop working. The issue affected everyone that used a secondary backup location. The issue was fully resolved by Tuesday 23 July 19:58 and backups were fully functional again.

Timeline

  • 22.07 23:30 - Issue was first noticed by a user.
  • 22.07 23:48 - An Issue was opened by said user.
  • 23.07 19:00 - First look on the issue by the lead dev.
  • 23.07 19:50 - Issue was determined to be because of a simple error.
  • 23.07 19:58 - Issue was finally fixed.

Root case

A feature request AustrianToast/update#23 was made that added a secondary backup location. The lead dev made some simple error that were not caught in testing with a second user.

# Backup failure incident report Monday 22 July ## Summary At 23:48 GMT+2 an issue was spotted with the backup function of update. This caused backups to stop working. The issue affected everyone that used a secondary backup location. The issue was fully resolved by Tuesday 23 July 19:58 and backups were fully functional again. ## Timeline - 22.07 23:30 - Issue was first noticed by a user. - 22.07 23:48 - An Issue was opened by said user. - 23.07 19:00 - First look on the issue by the lead dev. - 23.07 19:50 - Issue was determined to be because of a simple error. - 23.07 19:58 - Issue was finally fixed. ## Root case A feature request AustrianToast/update#23 was made that added a secondary backup location. The lead dev made some simple error that were not caught in testing with a second user.
Sign in to join this conversation.
No description provided.