starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: Auto/Scheduled Backups may not be executing #1011

New Issue
Closed
opened 2026-04-24 23:29:01 +02:00 by adam · 7 comments
adam commented 2026-04-24 23:29:01 +02:00
Owner
Copy Link
Copy Source

Originally created by @raviwarrier on GitHub (Mar 7, 2023).

Describe the issue

I have set my backups to run every 2 days, but from the image below you can see that the last auto backup happened on 6th Feb, instead of today (7th March on 0:00 hours).

image

The log shows removing a backup of 4th Feb (due to max backups to keep limitation), but none since 6th Feb 2023.

image

I don't know what's causing this issue as the logs don't show any errors in the past month. Let me know if there's any data that I can provide to help you debug this.

Steps to reproduce the issue

  1. NA

Audiobookshelf version

2.2.16

How are you running audiobookshelf?

Docker

Originally created by @raviwarrier on GitHub (Mar 7, 2023). ### Describe the issue I have set my backups to run every 2 days, but from the image below you can see that the last auto backup happened on 6th Feb, instead of today (7th March on 0:00 hours). ![image](https://user-images.githubusercontent.com/42061703/223482094-4a31bca0-3883-414a-99ba-50c37cacd740.png) The log shows removing a backup of 4th Feb (due to max backups to keep limitation), but none since 6th Feb 2023. ![image](https://user-images.githubusercontent.com/42061703/223483047-abd019bb-a3f3-48d1-9307-820351e6f4c6.png) I don't know what's causing this issue as the logs don't show any errors in the past month. Let me know if there's any data that I can provide to help you debug this. ### Steps to reproduce the issue 1. NA ### Audiobookshelf version 2.2.16 ### How are you running audiobookshelf? Docker
adam added the bug label 2026-04-24 23:29:01 +02:00
adam closed this issue 2026-04-24 23:29:02 +02:00
adam commented 2026-04-24 23:29:03 +02:00
Author
Owner
Copy Link
Copy Source

@raviwarrier commented on GitHub (Mar 7, 2023):

I checked the log from a little earlier and found this:

image

This shows that when my RPI booted in the morning (around 4a), it found a bad backup archive. But that is also from 8th Feb 2023 and nothing else since then. Will check to see if the 9th March backup that is scheduled happens or not and report.

@raviwarrier commented on GitHub (Mar 7, 2023): I checked the log from a little earlier and found this: ![image](https://user-images.githubusercontent.com/42061703/223483797-8b325002-a085-4adc-ace4-66b4d4a1441a.png) This shows that when my RPI booted in the morning (around 4a), it found a bad backup archive. But that is also from 8th Feb 2023 and nothing else since then. Will check to see if the 9th March backup that is scheduled happens or not and report.
adam commented 2026-04-24 23:29:03 +02:00
Author
Owner
Copy Link
Copy Source

@raviwarrier commented on GitHub (Mar 7, 2023):

image

Scratch that. It seems to be working... but only, now it seems, that ABS backup page is not displaying the latest backups and is stuck at 6th Feb 2023 backup. Will delete 8th Feb Backup and see if it displays later backups.

Also, why isn't it deleting the old backups as set?
image

@raviwarrier commented on GitHub (Mar 7, 2023): ![image](https://user-images.githubusercontent.com/42061703/223484516-607a2811-c6e8-456c-9b1c-fb598aa4f0fa.png) Scratch that. It seems to be working... but only, now it seems, that ABS backup page is not displaying the latest backups and is stuck at 6th Feb 2023 backup. Will delete 8th Feb Backup and see if it displays later backups. Also, why isn't it deleting the old backups as set? ![image](https://user-images.githubusercontent.com/42061703/223485045-ace64ce2-daac-43da-bc0f-650f1b855b48.png)
adam commented 2026-04-24 23:29:04 +02:00
Author
Owner
Copy Link
Copy Source

@advplyr commented on GitHub (Mar 7, 2023):

I think there was a version that was producing invalid backups and if they fail to load then they aren't counted as backups. Maybe try clearing out those old ones manually and we can see if we can reproduce this with fresh backups.

@advplyr commented on GitHub (Mar 7, 2023): I think there was a version that was producing invalid backups and if they fail to load then they aren't counted as backups. Maybe try clearing out those old ones manually and we can see if we can reproduce this with fresh backups.
adam commented 2026-04-24 23:29:05 +02:00
Author
Owner
Copy Link
Copy Source

@raviwarrier commented on GitHub (Mar 7, 2023):

Yeah... I just deleted all the old backup except the last two. Will check on 9th March and report back.

@raviwarrier commented on GitHub (Mar 7, 2023): Yeah... I just deleted all the old backup except the last two. Will check on 9th March and report back.
adam commented 2026-04-24 23:29:06 +02:00
Author
Owner
Copy Link
Copy Source

@raviwarrier commented on GitHub (Mar 9, 2023):

Looks like everything is working fine. But I think the dates might be off... If you see in the OP, the next backup was scheduled to be at 09-March-2023 0:00, but...

image

It happened at 08-March-2023 0:00. I don't know which one is wrong, but there is definitely a mismatch...

Also, "0 0 */2 * *" means every 2nd day, so, why is it showing the schedule for every 3rd day.

Last backup was on 6th, but it showed next backup on 9th (see image in OP)
This backup was on 8th, but it's showing next backup on 11th.

Should I open another issue for this?

@raviwarrier commented on GitHub (Mar 9, 2023): Looks like everything is working fine. But I think the dates might be off... If you see in the OP, the next backup was scheduled to be at 09-March-2023 0:00, but... ![image](https://user-images.githubusercontent.com/42061703/224002441-bbab91b8-20bb-44a5-a7ac-d3562197f51c.png) It happened at 08-March-2023 0:00. I don't know which one is wrong, but there is definitely a mismatch... Also, "0 0 */2 * *" means every 2nd day, so, why is it showing the schedule for every 3rd day. Last backup was on 6th, but it showed next backup on 9th (see image in OP) This backup was on 8th, but it's showing next backup on 11th. Should I open another issue for this?
adam commented 2026-04-24 23:29:07 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Feb 22, 2025):

Is this still an issue? There has been several updates to the backups since this was opened.

@nichwall commented on GitHub (Feb 22, 2025): Is this still an issue? There has been several updates to the backups since this was opened.
adam commented 2026-04-24 23:29:07 +02:00
Author
Owner
Copy Link
Copy Source

@raviwarrier commented on GitHub (Feb 23, 2025):

No. I don't think so. My backups have been working fine for a while now. You can close this. :)

@raviwarrier commented on GitHub (Feb 23, 2025): No. I don't think so. My backups have been working fine for a while now. You can close this. :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#1011
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?