Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docker] All tasks in bull queue gone after restart #14

Closed
vodkapmp opened this issue Oct 27, 2022 · 3 comments · Fixed by #16
Closed

[Docker] All tasks in bull queue gone after restart #14

vodkapmp opened this issue Oct 27, 2022 · 3 comments · Fixed by #16
Labels
bug Something isn't working

Comments

@vodkapmp
Copy link

After a restart of my docker containers I noticed that everything in Bull Dashboard is gone.
I stop all my dockers 3 times a week to do a quick backup of important docker related data (configs etc) after yesterdays backup cycle I noticed that everything in the bull dashboard is now gone.
image

Is there some mount point for the docker that I should've had that isn't mentioned in the docker-compose file?

Also is there a faster way to get my scheduled tasks back than re-adding every manga one by one?

@oae
Copy link
Owner

oae commented Oct 27, 2022

If you recreated the container it might have been deleted. Mount should be under redis:/data like here. Currently, no way to get the queue back. I will add it in the next version.

@oae oae added the bug Something isn't working label Oct 27, 2022
@vodkapmp
Copy link
Author

Thanks!
I do have redis:/data mounted, but it seems something unrelated to kaizoku went wrong and the data was destroyed.

I assume a way to add the queue back might be part of the changes one would implement with #9

@oae
Copy link
Owner

oae commented Oct 27, 2022

All tasks will be recreated on startup. Also, you can update manga to recreate individual tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants