AustrianToast/update
1
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Before backup error #26

New Issue
Closed
opened 2024-07-22 23:48:57 +02:00 by ProfessionalUwU · 3 comments
ProfessionalUwU commented 2024-07-22 23:48:57 +02:00
Collaborator
Copy Link

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
AustrianToast commented 2024-07-23 19:58:50 +02:00
Owner
Copy Link

should work now

should work now
ProfessionalUwU commented 2024-07-23 20:08:20 +02:00
Author
Collaborator
Copy Link

Works on my end now

Works on my end now
ProfessionalUwU commented 2024-07-23 20:19:59 +02:00
Author
Collaborator
Copy Link

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.
main
Branches Tags
Labels
Clear labels
bug
Something isn't working
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
invalid
This doesn't seem right
question
Further information is requested
wontfix
This will not be worked on
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees AustrianToast
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: AustrianToast/update#26
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?