There is a bug in FME Server 2015 1.3.1. that lets me change the number of engines on the core-server, but not on the attached engine-only server. Default is 2 engines per server, 4 in total. I want 3 engines to run on the core, and 1 on the other server. Is there a way to edit fme-engine config file to force ONLY 1 engine even if there are licenses available?
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.
+23- Supporter
- 30 replies
Hi Till,
just add a line to "<FMEServerHome>\Server\processMonitorConfigEngines.txt":
NODE_OVERWRITE=trueon your engine only host machine. This will allow to config the desired number of engines by the START_ENGINE_* lines.
This is also in the documentation, but perhaps not where expected:
+20- Safer
- 3719 replies
It's possible that the engine machine has not been given access to the database on the core machine. Take a look at the following article: https://knowledge.safe.com/articles/20008/unable-t...
Please let us know if that was the problem.
+25- Supporter
- 956 replies
It's possible that the engine machine has not been given access to the database on the core machine. Take a look at the following article: https://knowledge.safe.com/articles/20008/unable-t...
Please let us know if that was the problem.
Hm, just saw this. I did find an error in the file mentioned and restarted both the core and the engine. It still does not work.
+25- Supporter
- 956 replies
Hi Till,
just add a line to "<FMEServerHome>\Server\processMonitorConfigEngines.txt":
NODE_OVERWRITE=trueon your engine only host machine. This will allow to config the desired number of engines by the START_ENGINE_* lines.
This is also in the documentation, but perhaps not where expected:
Just wondering if this is still the recommended way to do this in FME2019 also? Ie edit the processmonitorconfigengines.txt? It seems that the new web GUI lets you input these parameters directly in the webgui, but it seems not to always "obey" this number in an environment with many engines. Also when restarting the core or engine it sometimes "picks up" the number from the processmonitorconfigengines and not the "database/webgui" ?
+12- Safer
- 158 replies
Just wondering if this is still the recommended way to do this in FME2019 also? Ie edit the processmonitorconfigengines.txt? It seems that the new web GUI lets you input these parameters directly in the webgui, but it seems not to always "obey" this number in an environment with many engines. Also when restarting the core or engine it sometimes "picks up" the number from the processmonitorconfigengines and not the "database/webgui" ?
Hi @sigtill, No, this wouldn't be the recommended way to manage the number of engines to start in 2019. If you're seeing the number of engines as set in the web interface being 'forgotten' when restarting the core or engine services, that sounds like a problem that we'd want to investigate and resolve. Are you seeing that kind of behaviour very frequently? Would you mind reporting that to use through: https://www.safe.com/support/report-a-problem/ ?
+25- Supporter
- 956 replies
Hi @sigtill, No, this wouldn't be the recommended way to manage the number of engines to start in 2019. If you're seeing the number of engines as set in the web interface being 'forgotten' when restarting the core or engine services, that sounds like a problem that we'd want to investigate and resolve. Are you seeing that kind of behaviour very frequently? Would you mind reporting that to use through: https://www.safe.com/support/report-a-problem/ ?
Yes, I`ll try to debug with the client a bit more and then report an issue to figure out if it is a browser issue, load balancer issue, network issue etc. I will file a support-case when I have enough info, thanks @lauraatsafe