When I installed FME Server, it is asking me for the name of the server which I specified. But when I register the license and the engines are started, they are listed as localhost_ENGINE1. Is there a way to change it the server name? What if I wanted to specify the engines to run with the server name, how do I do that at install?
Solved
Change engine name from ocalhost_ENGINE1 to _ENGINE1
+23- Enthusiast
- 88 replies
Best answer by laurawatsafe
Hi @tnarladni I've seen this issue as well when installing FME Server 2018 and newer. Looks like the installer doesn't want to use the hostname for the Engines when the Engines and Server Core/application server are on the same machine. We're looking into this, so I'll send an update as soon as we have more information or a fix for this.
In the meantime, you can update the engine names to use the actual hostname by doing the following:
- Open the fmeCommonConfig.txt file and locate the parameters called NODE_NAME and NODE_HOST
- Change those to YourServerHost instead of localhost
- Open the processMonitorConfigEngines.txt file
- Under TEMPLATE_START_ENGINE, go to the end of that line and change the -ENGINE_HOST_NAME to YourServerHost
- Restart FME Server
At this point, you'll probably end up with both localhost and YourServerHost listed under Hosts. You can fix that by doing the following:
- Shut down just the FME Server Engines service (from Services.msc)
- On the Engines & Licensing page, remove localhost from under Hosts
- Start up the Engine Service again
- You may need to restart FME Server one more time here to completely remove localhost from appearing in the engine names
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.
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.
+12- Safer
- 158 replies
- Best Answer
Hi @tnarladni I've seen this issue as well when installing FME Server 2018 and newer. Looks like the installer doesn't want to use the hostname for the Engines when the Engines and Server Core/application server are on the same machine. We're looking into this, so I'll send an update as soon as we have more information or a fix for this.
In the meantime, you can update the engine names to use the actual hostname by doing the following:
- Open the fmeCommonConfig.txt file and locate the parameters called NODE_NAME and NODE_HOST
- Change those to YourServerHost instead of localhost
- Open the processMonitorConfigEngines.txt file
- Under TEMPLATE_START_ENGINE, go to the end of that line and change the -ENGINE_HOST_NAME to YourServerHost
- Restart FME Server
At this point, you'll probably end up with both localhost and YourServerHost listed under Hosts. You can fix that by doing the following:
- Shut down just the FME Server Engines service (from Services.msc)
- On the Engines & Licensing page, remove localhost from under Hosts
- Start up the Engine Service again
- You may need to restart FME Server one more time here to completely remove localhost from appearing in the engine names
Hi Laura,
Thanks for this solution. I have followed the instructions - it changes the Hosts available and names any new engines correctly, but 2 of the engines are left named as localhost_Engine1 and localhost_Engine2.
Is there any way to change these 2 engine names?
Regards
Richard
+12- Safer
- 158 replies
Hi Laura,
Thanks for this solution. I have followed the instructions - it changes the Hosts available and names any new engines correctly, but 2 of the engines are left named as localhost_Engine1 and localhost_Engine2.
Is there any way to change these 2 engine names?
Regards
Richard
Hi @ricstan,
If you check your processMonitorConfigEngines.txt file and look at the very bottom for the lines labelled Start FME Engine 1 and 2, does that still reference localhost in the start engine command. Like this:
START_ENGINE_localhost_Engine1=!TEMPLATE_START_ENGINE!
If so, try replacing localhost there with the proper machine name. Just let me know if that doesn't help and I can help you troubleshoot further.
+12- Safer
- 158 replies
Update on this, we have now fixed this issue where the FME Server Engines and Core were using localhost instead of the correct hostname as specified during installation.
The fix is now available in the newest version of FME Server 2018.1 available on our downloads page and also for FME Server 2019 which is still in beta. This should not be a problem for anyone moving forward.
+12- Safer
- 158 replies
Hi @tnarladni I've seen this issue as well when installing FME Server 2018 and newer. Looks like the installer doesn't want to use the hostname for the Engines when the Engines and Server Core/application server are on the same machine. We're looking into this, so I'll send an update as soon as we have more information or a fix for this.
In the meantime, you can update the engine names to use the actual hostname by doing the following:
- Open the fmeCommonConfig.txt file and locate the parameters called NODE_NAME and NODE_HOST
- Change those to YourServerHost instead of localhost
- Open the processMonitorConfigEngines.txt file
- Under TEMPLATE_START_ENGINE, go to the end of that line and change the -ENGINE_HOST_NAME to YourServerHost
- Restart FME Server
At this point, you'll probably end up with both localhost and YourServerHost listed under Hosts. You can fix that by doing the following:
- Shut down just the FME Server Engines service (from Services.msc)
- On the Engines & Licensing page, remove localhost from under Hosts
- Start up the Engine Service again
- You may need to restart FME Server one more time here to completely remove localhost from appearing in the engine names
Update on this, we have now fixed this issue where the FME Server Engines and Core were using localhost instead of the correct hostname as specified during installation.
The fix is now available in the newest version of FME Server 2018.1 available on our downloads page and also for FME Server 2019 which is still in beta. This should not be a problem for anyone moving forward.
Update on this, we have now fixed this issue where the FME Server Engines and Core were using localhost instead of the correct hostname as specified during installation.
The fix is now available in the newest version of FME Server 2018.1 available on our downloads page and also for FME Server 2019 which is still in beta. This should not be a problem for anyone moving forward.
Thank you. I'll grab a copy.
Hi Laura,
Thanks for this solution. I have followed the instructions - it changes the Hosts available and names any new engines correctly, but 2 of the engines are left named as localhost_Engine1 and localhost_Engine2.
Is there any way to change these 2 engine names?
Regards
Richard
still show localhost_Engine1
in Hosts session: there are two rows: one is named with my machine name and the other row has "localhost".
+12- Safer
- 158 replies
in Hosts session: there are two rows: one is named with my machine name and the other row has "localhost".
Hi @george, The simplest way I've found to clear that is to first, stop the FME Server Engine service on the machine, then go to the Engines & Licensing page, there should now be a Remove button that appears beside the two hostnames, click Remove beside the localhost entry, then start up the engine service again.
+11- Supporter
- 135 replies
Hi @tnarladni I've seen this issue as well when installing FME Server 2018 and newer. Looks like the installer doesn't want to use the hostname for the Engines when the Engines and Server Core/application server are on the same machine. We're looking into this, so I'll send an update as soon as we have more information or a fix for this.
In the meantime, you can update the engine names to use the actual hostname by doing the following:
- Open the fmeCommonConfig.txt file and locate the parameters called NODE_NAME and NODE_HOST
- Change those to YourServerHost instead of localhost
- Open the processMonitorConfigEngines.txt file
- Under TEMPLATE_START_ENGINE, go to the end of that line and change the -ENGINE_HOST_NAME to YourServerHost
- Restart FME Server
At this point, you'll probably end up with both localhost and YourServerHost listed under Hosts. You can fix that by doing the following:
- Shut down just the FME Server Engines service (from Services.msc)
- On the Engines & Licensing page, remove localhost from under Hosts
- Start up the Engine Service again
- You may need to restart FME Server one more time here to completely remove localhost from appearing in the engine names
Hi Laura, I’m running into this issue with FME Flow 2024.2. Is this recommendation still relevant?
- Participant
- 1 reply
Hi @tnarladni I've seen this issue as well when installing FME Server 2018 and newer. Looks like the installer doesn't want to use the hostname for the Engines when the Engines and Server Core/application server are on the same machine. We're looking into this, so I'll send an update as soon as we have more information or a fix for this.
In the meantime, you can update the engine names to use the actual hostname by doing the following:
- Open the fmeCommonConfig.txt file and locate the parameters called NODE_NAME and NODE_HOST
- Change those to YourServerHost instead of localhost
- Open the processMonitorConfigEngines.txt file
- Under TEMPLATE_START_ENGINE, go to the end of that line and change the -ENGINE_HOST_NAME to YourServerHost
- Restart FME Server
At this point, you'll probably end up with both localhost and YourServerHost listed under Hosts. You can fix that by doing the following:
- Shut down just the FME Server Engines service (from Services.msc)
- On the Engines & Licensing page, remove localhost from under Hosts
- Start up the Engine Service again
- You may need to restart FME Server one more time here to completely remove localhost from appearing in the engine names
Hi Laura, I’m running into this issue with FME Flow 2024.2. Is this recommendation still relevant?
I came across the same issue and found your comment when trying to troubleshoot. I believe it is now the default to have engines named as localhost instead of the hostname and they do not recommend changing it. See this article. https://support.safe.com/hc/en-us/articles/35849671886605-Known-Issue-Engine-Name-Change-to-Localhost-Causes-Jobs-to-Queue
+11- Supporter
- 135 replies
Hi @tnarladni I've seen this issue as well when installing FME Server 2018 and newer. Looks like the installer doesn't want to use the hostname for the Engines when the Engines and Server Core/application server are on the same machine. We're looking into this, so I'll send an update as soon as we have more information or a fix for this.
In the meantime, you can update the engine names to use the actual hostname by doing the following:
- Open the fmeCommonConfig.txt file and locate the parameters called NODE_NAME and NODE_HOST
- Change those to YourServerHost instead of localhost
- Open the processMonitorConfigEngines.txt file
- Under TEMPLATE_START_ENGINE, go to the end of that line and change the -ENGINE_HOST_NAME to YourServerHost
- Restart FME Server
At this point, you'll probably end up with both localhost and YourServerHost listed under Hosts. You can fix that by doing the following:
- Shut down just the FME Server Engines service (from Services.msc)
- On the Engines & Licensing page, remove localhost from under Hosts
- Start up the Engine Service again
- You may need to restart FME Server one more time here to completely remove localhost from appearing in the engine names
Hi Laura, I’m running into this issue with FME Flow 2024.2. Is this recommendation still relevant?
I came across the same issue and found your comment when trying to troubleshoot. I believe it is now the default to have engines named as localhost instead of the hostname and they do not recommend changing it. See this article. https://support.safe.com/hc/en-us/articles/35849671886605-Known-Issue-Engine-Name-Change-to-Localhost-Causes-Jobs-to-Queue
yes, thank you. found the same.