Skip to main content
Question

FME Server on docker cannot connect to MongoDB

  • January 18, 2019
  • 5 replies
  • 34 views
S
Forum|alt.badge.img

I recently installed FME Server to docker using the installation guide. Since yesterday I have been trying to test it using a simple .fmw in order to write some data to a MongoDB instance. I tried in both local MongoDB and in a MongoDB-docker instance. In both cases I am getting the same error:

 

MongoDB writer: Cannot connect: couldn't connect to server <<PORT NUMBER>>, connection attempt failed.

Please note that, I have access to both MongoDB instances from local FME Workbench and I can execute the same .fmw. Find attached the file.

This seems to be an FME docker network issue, but I cannot be sure what. Any ideas?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

paalped
Contributor
Forum|alt.badge.img+5
  • paalpedContributor
  • Contributor
  • January 18, 2019

I just wonder if this works, could you try to run fmeserver from f.ex: 127.0.0.2 to see if it solves the issue? just pop 127.0.0.2 in the browser window. I have no experience with mongoDb so its just a guess if there is some interference between fmeserver and mongodb on ip 127.0.0.1.

S
Forum|alt.badge.img
  • stratos.tso
  • Author
  • January 21, 2019

I just wonder if this works, could you try to run fmeserver from f.ex: 127.0.0.2 to see if it solves the issue? just pop 127.0.0.2 in the browser window. I have no experience with mongoDb so its just a guess if there is some interference between fmeserver and mongodb on  ip 127.0.0.1.

I am not so sure how can I do that, since I have the containers already created. I tried stopping the FME-nginx container &

docker run -h 127.0.0.2 <image> <container-name> 

But it failed to run. I think that in order to do so I have to change the docker-compose.yaml and re-compose. Can I avoid that?

J
Forum|alt.badge.img+2

Hi @stratos.tso

 

When you set up your mongo database connection, have you specified the MongoDB Server as localhost? If your computer that you have MongoDB installed locally on has a hostname can you try to use that instead of localhost?

 

I'm thinking that when it's running on FME Server with localhost it's looking inside the FME Server container (it's own localhost) and correctly not finding MongoDB because it doesn't exist there.
G
Forum|alt.badge.img

Hi @stratos.tso

The easiest option is to use the internal or external IP of your host instead of localhost or 127.0.0.1 as the Mongo DB hostname in the FME Server Web Connection.

 

 

Another option to do this is to join an existing network of the FME Server deployment with your new Mongo DB container. Here is an example of a Mongo DB docker-compose file that joins the web network of an existing FME Server deployment:
# Use root/example as user/password credentials
version: '3.1'

services:

  mongo:
  Â  image: mongo
  Â  restart: always
  Â  environment:
  Â  Â  MONGO_INITDB_ROOT_USERNAME: root
  Â  Â  MONGO_INITDB_ROOT_PASSWORD: example

networks:
  default:
  Â  external:
  Â  Â  name: 2019_web

I chose the web network because the fmeserverengine service needs to be part of the network to successfully connect to the Mongo DB. The prefix will be different for you but you can search for an existing FME Server web network with the docker network ls. In the Database connection on FME Server you can now use mongo  as hostname (default) for your Mongo DB.

The overall important part is that the fmeserverengine service shares a network with your Mongo DB service. Using the existing web container is one way but obviously, you could also create a network specifically for the communication between the Mongo DB & FME Server and add it to the fmeserverengine service in the FME Server compose file.

Here are little more details which might help with this too:

https://docs.docker.com/compose/networking/

cruky
  • cruky
  • December 15, 2020

If anyone face this problem, here is a proposed solution:

Like jlutherthomas said FME Server with Host: localhost or even 127.0.0.1. is looking inside the FME Server container. To make it connect to your local host you can use host.docker.internal, it's documented here.

So when setting up a database connection set a host name (or MongoDB Server in your case) to host.docker.internal.

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.