Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New instances are failing with "multi-user-redis"

See original GitHub issue

This used to work fine but now I am seeing this issue. Any ideas?

Events:
  Type     Reason     Age                From                   Message
  ----     ------     ----               ----                   -------
  Normal   Scheduled  36s                default-scheduler      Successfully assigned default/t-val-juiceshop-79b6488494-bftsr to s0025abl5905
  Normal   Pulled     35s                kubelet, s0025abl5905  Container image "bkimminich/juice-shop:latest" already present on machine
  Normal   Created    35s                kubelet, s0025abl5905  Created container juice-shop
  Normal   Started    34s                kubelet, s0025abl5905  Started container juice-shop
  Normal   Pulling    15s (x3 over 34s)  kubelet, s0025abl5905  Pulling image "iteratec/juice-progress-watchdog"
  Normal   Pulled     12s (x3 over 31s)  kubelet, s0025abl5905  Successfully pulled image "iteratec/juice-progress-watchdog"
  Warning  Failed     12s (x3 over 31s)  kubelet, s0025abl5905  Error: secret "multi-juicer-redis" not found
  Warning  Unhealthy  9s (x11 over 29s)  kubelet, s0025abl5905  Readiness probe failed: Get http://10.244.1.121:3000/rest/admin/application-version: dial tcp 10.244.1.121:3000: connect: connection refused

[chandv3_adm@sdcnjc ~]$ curl http://10.244.1.121:3000/rest/admin/application-version
{"version":"9.3.1"}

Issue Analytics

State:
Created 4 years ago
Comments:14 (7 by maintainers)

Top GitHub Comments

1reaction

blazergunscommented, Jan 14, 2020

You wont believe it, I uninstalled and reinstalled with latest release knowing that the fix wont solve redis problem, but it did. I seem to have gone away. I was able to create atleast 5 instances and seem to be working. I even brought restarted minikube cluster and everything seem to work. The only thing that needs to be tested is imagePullPolicy for progress-watchdog. I will test this out today.

0reactions

J12934commented, Jan 22, 2020

I’ll close this issue as this seems to be resolved.

Top Results From Across the Web

Troubleshoot connecting to an ElastiCache for Redis cluster

Verify network-level connectivity between the cluster and the client resource · 1. Select the cluster name from the Redis clusters menu, and then ......

Scaling with Redis Cluster

To remain available when a subset of master nodes are failing or are not able to communicate with the majority of nodes, Redis...

How configure multiple Redis instances on Debian

The end of the redis-server unit file would say: [Install] WantedBy=multi-user.target Alias=redis.service. Either remove that Alias, ...

Redis Anti-Patterns Every Developer Should Avoid

By default, each Redis instance you create will in turn create its own connection pool. You can override this behavior and use an...

High availability for Azure Cache for Redis - Microsoft Learn

The primary node usually is responsible for servicing write and read requests from clients. On a write operation, it commits a new key...