ingestion, API service exit in docker since Mongo fails to to start
denkab opened this issue · 8 comments
Hi!
In my current configuration, docker-compose command results in deficient epirius instance, because API exits.
epirus-free_mongodb_1 exited with code 132
api_1 | Caused by: com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=mongodb:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketException: mongodb}, caused by {java.net.UnknownHostException: mongodb}}]
followed by
epirus-free_api_1 exited with code 1
Changing "mongo:latest" -> "mongo:4" in docker-compose.yml allows Mongo to start and entire contraption starts to function.
@denkab is your issue solved?
If not, we will need to know more logs to dig the issue.
It is solved for me but may appear for others... Is "mongo:latest" a true prerequisite for the product to work correctly?
Can you please share the logs of mongo when you use the latest tag?
We might need to specify the version of mongo as new versions might have breaking changes that we still don't support.
Knowing the reason why latest fails is important to decide.
how do I do that? it doesn't print any logs to the docker console
Change the version back to latest.
Run epirus free then run:
docker-compose logsAnd share the whole output.
mongo:5.0.8 doesn't even start. There are no errors in the log at all. it's kinda weird.
anyway, changing it to mongo:4 allows it to start up just fine.