This repository was archived by the owner on Dec 13, 2023. It is now read-only.
Issue with grpc conductor server using docker-compose #2303
Unanswered
chandruibm
asked this question in
Q&A
Replies: 3 comments 3 replies
-
|
Hey @michaelpaliy, Is this something you can help with? @chandruibm Can you also share the start up logs for Conductor server please? It is most likely missing configuration for mysql module. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Please find the server start up logs |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @kishorebanala @chandruibm , There are some wrong configurations in the docker-compose file, for example:
I fixed these issues and opened MR: #2317 |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to use my sql DB for the persistence and used the docker/grpc/docker-compose. It starts the mysql, ES and ui, but the server fails with exit code 1. What do I need to configure inorder for this to work. The documentation doesn't seem to have any reference on how to setup using my sql or other persistence layer other than memory & redis. And it is becoming hard to understand what is expected to set up using mysql and how to resolve the problem
Steps to reproduce:
It starts the following cotainer but not the server, and it logs this in console
Console Logs :
Creating volume "grpc_conductor_mysql" with default driver
Creating grpc_mysql_1 ... done
Creating grpc_elasticsearch_1 ... done
Creating grpc_conductor-server_1 ... done
Creating grpc_conductor-ui_1 ... done
Attaching to grpc_mysql_1, grpc_elasticsearch_1, grpc_conductor-server_1, grpc_conductor-ui_1
...........................
...........................
elasticsearch_1 | [2021-06-10T11:16:40,220][INFO ][o.e.c.m.MetaDataMappingService] [r-4p8ll] [.watches/jZhDBLWhSnWz4ll0T1_07A] update_mapping [watch]
grpc_conductor-server_1 exited with code 1
elasticsearch_1 | [2021-06-10T11:17:40,644][INFO ][o.e.c.m.MetaDataCreateIndexService] [r-4p8ll] [.triggered_watches] creating index, cause [auto(bulk api)], templates [triggered_watches], shards [1]/[1], mappings [triggered_watch]
Active containers shows only these and not the server, since it did exit:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
18a81da963fc conductor:ui "/bin/sh /app/startu…" 13 minutes ago Up 13 minutes 0.0.0.0:5000->5000/tcp, :::5000->5000/tcp grpc_conductor-ui_1
73cfae7c8716 docker.elastic.co/elasticsearch/elasticsearch:5.6.8 "/bin/bash bin/es-do…" 13 minutes ago Up 13 minutes (healthy) 0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 0.0.0.0:9300->9300/tcp, :::9300->9300/tcp grpc_elasticsearch_1
4612bcf8ec36 mysql:5.6 "docker-entrypoint.s…" 13 minutes ago Up 13 minutes (healthy) 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp grpc_mysql_1
Beta Was this translation helpful? Give feedback.
All reactions