Skip to main content
Solved

FME Server on Docker

  • January 5, 2017
  • 2 replies
  • 37 views
G

All,

I have read and implemented the docker installation of FME server on Docker Engine as published by @GerhardAtSafe.

https://knowledge.safe.com/articles/24815/deployment-of-fme-server-using-docker-toolbox.html

Mostly the installation, licensing and engine management runs fine. However, I am having an issue using the job manager to kill jobs. Any time i try to terminate a job I get error communicating with FME server host (hostid). Connection Refused.

 

I have reason to believe this is to do with the fact that the hostname of the engine and the web/core are different (as they are containerised) do kill requests get sent on a different port address? Is this an issue with the docker configuration or has anybody else had the same issue? Appreciate any insights you may have had.

Regards

Gavin Montgomery

Best answer by gerhardatsafe

Update:

This issue has been resolved. I tested the described scenario in FME Server for Docker build 17725 & 18244.

 

Hi Gavin,

I reproduced the error message (Error communicating with FME server) you are seeing. However, in my tests, the jobs still get canceled. I used the current Docker containers running FME Server 2017 beta (b17200). Can you confirm that the jobs are still canceled although you see the error message, on your side? I filed a report for our developers to investigate why this error message is falsely triggered and will let you know once we have an update. Thank you for testing FME Server for Docker! We appreciate your involvement in helping us make FME even better!

Cheers,

Gerhard

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.

2 replies

G
Forum|alt.badge.img
  • gerhardatsafe
  • 288 replies
  • Best Answer
  • January 5, 2017

Update:

This issue has been resolved. I tested the described scenario in FME Server for Docker build 17725 & 18244.

 

Hi Gavin,

I reproduced the error message (Error communicating with FME server) you are seeing. However, in my tests, the jobs still get canceled. I used the current Docker containers running FME Server 2017 beta (b17200). Can you confirm that the jobs are still canceled although you see the error message, on your side? I filed a report for our developers to investigate why this error message is falsely triggered and will let you know once we have an update. Thank you for testing FME Server for Docker! We appreciate your involvement in helping us make FME even better!

Cheers,

Gerhard

denniswilhelm
Contributor
Forum|alt.badge.img+17
  • denniswilhelmContributor
  • Contributor
  • 26 replies
  • January 9, 2017

I'm getting the same results (build 17200) but I can confirm that the jobs are in fact cancelled even though the error message suggests otherwise.

Community Stats

32,100
Posts
121,895
Replies
39,744
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.