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

Redis has stopped populating any data and queries from osctrl Admin UI are failing. #378

Closed
vinayakdb opened this issue Dec 15, 2023 · 1 comment
Assignees
Labels
backend Backend related issues 🐛 bug Something isn't working cache Cache related issues

Comments

@vinayakdb
Copy link

My test setups are using osctrl docker containers.
redis:6.2.6-alpine3.15 docker image is in use.
Redis is working fine in 'setup1' but in the 'setup2', the redis has stopped populating any data.
In the setup2, I did delete the docker volume of redis and also deleted container and then restarted it.
I noticed the redis issue when the queries executed in setup1 were fetching results successfully and the queries in setup2 were failing since a month or so.
On fresh installations, the docker images work fine.

I am not using any custom redis conf.
Permissions look fine, disk space is available.
Any suggestions to troubleshoot?

working setup shows
ubuntu@test1:~$ docker exec -it osctrl-redis redis-cli
127.0.0.1:6379> keys *

  1. "status:48AE68E0-9DA9-4FDC-8D3A-1B07F0E49815:fish-ABc8De:1702622413655"
  2. "status:DB6A2142-15E9-3CF9-F19A-6FA819A5EB51:fish-tDkerl:1702647942547"
  3. "status:181A3A42-8B6A-9E81-52E3-F2120BBA2461:fish-9opp42:1702573113878"
    ....
  4. "status:4AFF7684-FE54-11EB-810C-7C8AE195578F:fish-ABc8De:1702623240974"
  5. "status:EB143A42-5CBE-85DF-977A-140D25894780:fish-9opp42:1702632303470"
  6. "status:37303550-3135-4753-4833-32364C4C505A:fish-678feD:1702629763444"
  7. "status:181A3A42-8B6A-9E81-52E3-F2120BBA2461:fish-9opp42:1702576114632"
    127.0.0.1:6379>

non-working setup shows
ubuntu@test2:~$ docker exec -it osctrl-redis redis-cli
127.0.0.1:6379> keys *
(empty array)
127.0.0.1:6379>

@javuto javuto added 🐛 bug Something isn't working backend Backend related issues cache Cache related issues labels Jan 1, 2024
@javuto javuto self-assigned this Jan 1, 2024
@javuto
Copy link
Collaborator

javuto commented Apr 12, 2024

Logs will stop going to the cache, once #435 lands, since it was compromising the integrity of the redis service. Also redis was not expiring keys properly so I may need to look into that. Thanks!

@javuto javuto closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related issues 🐛 bug Something isn't working cache Cache related issues
Projects
None yet
Development

No branches or pull requests

2 participants