-
Notifications
You must be signed in to change notification settings - Fork 2.3k
docker-compose up
throws redis exception at startup
#3536
Comments
docker-compose up
tutorial is now brokendocker-compose up
throws redis exception at startup
I'll add to this. I was able to recreate this as well. I had to remove the health check for RabbitMQ because Docker will not see that it is healthy in the current state because it hangs up in a weird state. Once you remove the health check from
|
I tried running the Conductor locally too and got the same problems: with Redis and with RabbitMQ. Talking about Redis I think there are 2 issues:
Above changes made on a fork: 20eab6d |
Good points @karczewsky - I was able to add On startup
|
Heads Up: I'm pretty new to the Conductor. I see that recently there was a change in docker-compose from elastic |
I am new as well. Yes, this is all from the recent update. Docker works as expected with the previous configuration. I want to get the updated changes because it looks like some items are in pace to make SQS connections easier. |
The elasticsearch image bump to 8.6.2 was in #3503. I was seeing the |
I didn't see anything in the diff between the two that stands out, but this is killing my analysis to use Netflix Conductor at all. |
@bdparrish we are going to take a look. |
I encountered a similar problem:
Is this same to yours? And is this solved now? It really messed me up. |
hello, Any news about this issue and how to fix it ? |
I am having the same issue right off the bat when running docker compose up. I am using WSL 2.0 and getting failure on Rabbitmq. Anyone able to figure it out! dependency failed to start: container for service "rabbitmq" exited (0) |
@Graynder I seem to be facing issue with connecting to postgres, can you help me with what changes you did to connect to postgres? |
@darcyzhc were you able to resolve the issue? |
I'm getting the same issue. Does anyone resolve it? |
no fix discover so I use old version off conductor because I don't want to install a redis for the moment ^^' |
i'm also stuck with the same issue, i tried using postgres and dynomite but both doesn't work. pls suggest old stable version to proceed where postgres and dynomite docker works |
same... stuck on this issue. |
any updates on this? |
I am hitting same issue when trying to execute with postgres yaml. I am struck with this issue. please provide a solution for this. thanks |
Hi @RomanAlberdaSoftserveInc , @Graynder , @srichandar , @JoshCrosby @riemann89 and @missioncoding Can you please share the configuration you are using? Please mask the sensitive fields. |
Hello @manan164 thanks for the response. I didn't make any configuration change apart from adding the conductor.postgres.persistance runtime dependency in the server/build.gradle which solves another issue of MetaDataDao constructor parameter. After which i applied docker compose -f docker-compose.yaml -f docker-compose-postgres.yaml build command followed with up the exceptions traces going infinitely no changes apart from these steps. |
Hi all, |
Folks, Just a note on this, If you are still seeing the issue please run |
Hi @manan164 , from what I can see in the PR, a Redis service is added, but that's precisely the problem. With version 3.13.3 (the version I'm currently using), there's no need for Redis, but with version 3.13.5, I have the impression that a Redis service is required for it to work, and this is a change of breacking from my point of view, which is blocking migration to a higher version. |
Hi @Graynder , Since we are now using orkes-queue, redis is required. Do you see any issue in |
Describe the bug
This is a follow-on to #3534. That specific issue is resolved by #3535, but further problems remain. When conductor-server starts up now with redis, which was added in #3435, it throws an exception:
Details
Conductor version: 3f81d3f (current main)
Persistence implementation: whatever comes with the default
docker-compose up
nowQueue implementation: RabbitMQ I guess
Lock: Redis?
Workflow definition: N/A
Task definition: N/A
Event handler definition: N/A
To Reproduce
Steps to reproduce the behavior:
docker-compose up
tutorial at https://conductor.netflix.com/devguide/running/docker.htmlThe text was updated successfully, but these errors were encountered: