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

bug: Redis Cache Container does not restart after server reboot #1274

Closed
1 task done
null-ref-0000 opened this issue Jun 2, 2024 · 2 comments · Fixed by #1275
Closed
1 task done

bug: Redis Cache Container does not restart after server reboot #1274

null-ref-0000 opened this issue Jun 2, 2024 · 2 comments · Fixed by #1275
Labels
bug Something isn't working

Comments

@null-ref-0000
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

After restarting a server with rengine installed, the redis cache container does not restart.

Expected Behavior

After restarting a server with rengine installed, the redis cache container restarts.

Steps To Reproduce

  1. Restart server
  2. observe that redis cache is not restarted automatically

Environment

- reNgine: 2.0.6
- OS: Debian 6.1.90-1
- Browser: Chrome

Anything else?

No response

@null-ref-0000 null-ref-0000 added the bug Something isn't working label Jun 2, 2024
Copy link
Contributor

github-actions bot commented Jun 2, 2024

👋 Hi @null-ref-0000,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@yogeshojha
Copy link
Owner

This is fixed in 2.1.0

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