My current FME Server setup includes a CORE/2 Engines set up on one machine with another Engine-Only Host running remotely on another machine.
Recently, I noticed jobs on the remote machine queuing up and never processing. Restarting the FME Server Engines Windows service temporarily fixed the problem. But only for a few hours.
I don't see any errors in logs. But I've just switched to debug level logging for more info and hope to capture some. What I do notice is that in FME Server web console, under licensing & engines, the remote engine just won't show up. Once I restart the service, I see it under both the Engines tab and the Deployment Status tab, until it disappears again.
Unlikely this is service account related (as other similar post/solutions suggest) since I can restart service and then it runs for a bit. I did make a change regarding domain controller/Active Directory recently but rolled that back and it didn't solve the issue. I am not aware of any other environmental changes on the remote Host, except potentially OS upgrades/patches that I am not responsible for.
Pending further insights from logs, what other prerequisites or dependencies should I be checking ?
Running FME Server 2020.2. Planning to upgrade to 2022 when it is released.
Thanks!