08-20-2024, 11:48 AM
I have many users who run tyFlow on their farm with zero issues, and who have never run those machines in UI mode.
This seems more like a configuration issue on your farm that was resolved when Max entered UI mode, for some reason. The fact that tyFlow wasn’t even loaded in headless mode seems to demonstrate that it’s not a tyFlow issue (tyFlow can’t control Max behavior if it’s not even loaded).
One final thing you can check is the max.log file that Max always generates during startup, that contains a more verbose log than what Deadline generates. You’ll have to search your machines for that file…I can’t remember the default location. But it may contain further details about the issue.
This seems more like a configuration issue on your farm that was resolved when Max entered UI mode, for some reason. The fact that tyFlow wasn’t even loaded in headless mode seems to demonstrate that it’s not a tyFlow issue (tyFlow can’t control Max behavior if it’s not even loaded).
One final thing you can check is the max.log file that Max always generates during startup, that contains a more verbose log than what Deadline generates. You’ll have to search your machines for that file…I can’t remember the default location. But it may contain further details about the issue.