Conductor issue with redis on kubernetes

i’m deploying orkes conductor community edition on kubernetes, conductor unable to to be up do tue and issue with redis ,

any one can help me on this issue he’s already deploy orkes conductor community on kubernetes

here’s the log:

INFO [main] org.springframework.boot.SpringApplication: No active profile set, falling back to 1 default profile: “default”
2025-01-20 08:42:17,720 INFO [main] org.springframework.data.repository.config.RepositoryConfigurationDelegate: Multiple Spring Data modules found, entering strict repository configuration mode!
2025-01-20 08:42:17,734 INFO [main] org.springframework.data.repository.config.RepositoryConfigurationDelegate: Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2025-01-20 08:42:17,774 INFO [main] org.springframework.data.repository.config.RepositoryConfigurationDelegate: Finished Spring Data repository scanning in 16 ms. Found 0 JPA repository interfaces.
2025-01-20 08:42:19,530 INFO [main] org.springframework.boot.web.embedded.tomcat.TomcatWebServer: Tomcat initialized with port(s): 8080 (http)
2025-01-20 08:42:19,552 INFO [main] org.apache.juli.logging.DirectJDKLog: Initializing ProtocolHandler [“http-nio-8080”]
2025-01-20 08:42:19,553 INFO [main] org.apache.juli.logging.DirectJDKLog: Starting service [Tomcat]
2025-01-20 08:42:19,554 INFO [main] org.apache.juli.logging.DirectJDKLog: Starting Servlet engine: [Apache Tomcat/9.0.75]
2025-01-20 08:42:19,767 INFO [main] org.apache.juli.logging.DirectJDKLog: Initializing Spring embedded WebApplicationContext
2025-01-20 08:42:19,768 INFO [main] org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext: Root WebApplicationContext: initialization completed in 9058 ms
2025-01-20 08:42:20,489 INFO [main] io.orkes.conductor.queue.config.RedisQueueConfiguration: Starting conductor server using redis_standalone - use SSL? false
2025-01-20 08:42:20,493 WARN [main] org.springframework.context.support.AbstractApplicationContext: Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘orkesConductorApplication’: Unsatisfied dependency expressed through field ‘metadataDAO’; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘orkesMetadataDAO’ defined in URL [jar:file:/app/libs/server.jar!/BOOT-INF/lib/orkes-conductor-persistence-0.0.1-SNAPSHOT.jar!/com/netflix/conductor/redis/dao/OrkesMetadataDAO.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘orkesJedisProxy’ defined in URL [jar:file:/app/libs/server.jar!/BOOT-INF/lib/orkes-conductor-persistence-0.0.1-SNAPSHOT.jar!/com/netflix/conductor/redis/jedis/OrkesJedisProxy.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘jedisStandalone’ defined in URL [jar:file:/app/libs/server.jar!/BOOT-INF/lib/orkes-conductor-persistence-0.0.1-SNAPSHOT.jar!/com/netflix/conductor/redis/jedis/JedisStandalone.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘getJedisPoolStandalone’ defined in class path resource [io/orkes/conductor/queue/config/RedisQueueConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [redis.clients.jedis.JedisPool]: Factory method ‘getJedisPoolStandalone’ threw exception; nested exception is java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
2025-01-20 08:42:20,506 INFO [main] org.apache.juli.logging.DirectJDKLog: Stopping service [Tomcat]

1 Like

Hey @alaeddine , thanks for posting :sunglasses:. Out of curiosity, are you running a standalone redis instance outside what comes with Conductor OSS natively?

In general, here’s a few things to check:

  1. Check if Redis is running in your Kube cluster
kubectl get pods -n <namespace>
  1. Check logs to see if Redis started correctly (or not):
kubectl logs <redis-pod-name> -n <namespace>
  1. The stack trace you attached indcates ArrayIndexOutOfBoundsException, which could be due to an improperly formatted or missing Redis connection string. Double check and make sure your environmental variables are set correctly:
kubectl exec -it <conductor-pod-name> -- env | grep CONDUCTOR

Let us know what you find!

Hi Jeff,

Thanks for your replay,

redis is up and running

here’s my deployment config, can you provide me what i should correct

apiVersion: apps/v1
kind: Deployment
metadata:
name: conductor-server
namespace: conductor
spec:
replicas: 1
selector:
matchLabels:
app: conductor-server
template:
metadata:
labels:
app: conductor-server
spec:
containers:
- name: conductor-server
image: orkesio/orkes-conductor-community:latest
ports:
- containerPort: 8080
- containerPort: 5000
env:
- name: spring.datasource.url
value: “jdbc:postgresql://postgres:5432/postgres”
- name: conductor.redis-lock.serverAddress
value: “redis://redis-6b886c566c-j7c5g.redis.conductor.svc.cluster.local:6379”
- name: conductor.redis.hosts
value: “redis:6379”
- name: conductor.queue.type
value: “redis_standalone”