@m.vlamings
Perhaps some information on the environment. Is it an express installation? (it appears to be)
How was the FME Flow Software installed? Did they run it with a command line and passing arguments? Or was this via the Installer? I have seen this sort of behaviour but only when a silent install was used and COREHOSTNAME or NODENAME was not supplied.
Express Installs using the Installer wizard will lay down the engines with ‘localhost’ as the hostname. So that’s got me thinking this might have been a silent installer or as you shared, someone tweaked the processMonitorConfigEngines.txt.
Could you stop the engine service (just the FME Flow Engines). Visit the Web UI and remove the host - it will likely through a REST API error after a few seconds on that page. This typically removes the metadata about the engines. Now try starting the FME Flow Engine service. What do you see in the WebUI now? Has it corrected itself? Can you change the engine count? If so you are done.
If not, then likely we need to consider reloading the Engine Templates. This feels like a new support ticket if you get here.
If someone has manually tweaked processMonitorConfigEngines.txt, then it will be evident if you look at the modified dates in the C:\Program Files\FMEFlow\Server\ location and comparing to the other config files.
Regardless if the file has been changed please review the config file C:\Program Files\FMEFlow\Server\processMonitorConfigEngines.txt
What do you see? Can you share what I am sharing below from that file?
As an example:
TEMPLATE_START_ENGINE="C:/Program Files/FMEFlow/Server/fme/FMEEngine.exe" REGISTER_FME_ENGINE localhost 7070 DEFAULT "C:/Program Files/FMEFlow/Server/fmeEngineConfig.txt" -ENGINE_HOST_NAME localhost
In the example above the engine hostname will appear as localhost (and this example is from an Express Install).
If this file has been tweaked, it will only load back into the system if you set NODE_OVERWRITE=true.
Again, if you get here, probably file a support ticket with us.
Hello Steve,
Thank you for your reply. It is an Express install that was started using the windows Installer. So no silent install via commandline or other arguments.
At the moment during daytime our development team is using the server, so I will have to stop the engines after office hours and see what happens if I delete the host and restart. I could try that tonight, but I think the problem is in the processMonitorConfigEngines.txt file, now that I looked at it.
As for the processMonitorConfigEngines.txt file. We installed on the E:\ drive so in our environment it is actually in E:\Program Files\FMEFlow\Server\
As adviced in the support article I mentioned before I made a change myself to this file at the bottom of the file, it said:
# Start FME Engine 1
START_ENGINE_localhost_Engine1=!TEMPLATE_START_ENGINE! -ENGINE_TYPE STANDARD
and I changed this to:
# Start FME Engine 1
START_ENGINE_myhostname_Engine1=!TEMPLATE_START_ENGINE! -ENGINE_TYPE STANDARD
(Where I typed myhostname is my actual hostname, but for privacy I changed it here)
I had overlooked the template settings in this file, I think the cause is there, because it says:
# ENGINE process configuration template
TEMPLATE_START_ENGINE="E:/Program Files/FMEFlow/Server/fme/FMEEngine.exe" REGISTER_FME_ENGINE localhost 7070 DEFAULT "E:/Program Files/FMEFlow/Server/fmeEngineConfig.txt" -ENGINE_HOST_NAME localhost
So I guess if I change it to:
# ENGINE process configuration template
TEMPLATE_START_ENGINE="E:/Program Files/FMEFlow/Server/fme/FMEEngine.exe" REGISTER_FME_ENGINE myhostname 7070 DEFAULT "E:/Program Files/FMEFlow/Server/fmeEngineConfig.txt" -ENGINE_HOST_NAME myhostname
and set NODE_OVERWRITE=true
this would most likely fix it I guess?
Do I need to change anything to this:
# Start FME Engine 1
START_ENGINE_myhostname_Engine1=!TEMPLATE_START_ENGINE! -ENGINE_TYPE STANDARD
because I have 2 engines, can I also add:
START_ENGINE_myhostname_Engine2=!TEMPLATE_START_ENGINE! -ENGINE_TYPE STANDARD
Or is this not adviced? Please let me know if my assumptions are correct, then I will try this tonight after working hours. First to only modify the processMonitorConfigEngines.txt file, my guess would be I only have to restart the engines after that and the server does not need to be deleted in the WebUI. I will only do that if I cannot assign the engines to the server.
Thanks,
Martijn
Hi Steve,
I changed:
# ENGINE process configuration template
TEMPLATE_START_ENGINE="E:/Program Files/FMEFlow/Server/fme/FMEEngine.exe" REGISTER_FME_ENGINE myhostname 7070 DEFAULT "E:/Program Files/FMEFlow/Server/fmeEngineConfig.txt" -ENGINE_HOST_NAME myhostname
and set NODE_OVERWRITE=true
I also added:
# Start FME Engine 1 & 2
START_ENGINE_myhostname_Engine1=!TEMPLATE_START_ENGINE! -ENGINE_TYPE STANDARD
START_ENGINE_myhostname_Engine2=!TEMPLATE_START_ENGINE! -ENGINE_TYPE STANDARD
I used restartFMEFlowWindowsService.bat to restart everything, and when I logged in to the WebUI as admin, everything looked great and works. And both engines are already assigned correctly to the server and running.
Now that everything is working I commented out #NODE_OVERWRITE=true So that it does not get unnecessary overwritten in the database with every restart.
thanks a lot, I'm new to FME but now I feel confident enough to upgrade our production environment :-)
