I work in a studio with 10+ work stations which are supposed to start a deadline worker when they are idle. I have and issue where Deadline launcher keeps triggering idle detection (and starting a worker) on our work station, while we are working. It is supposed to trigger if we take a break for 15 minutes or when the day is over. Any ideas why this is happening? I have tried any solutions I can think of.
Hello @Simonlp
Thanks for reaching out. I need some data to look into this issue whenever you get a chance:
- Worker scheduling and Idle detection settings: Deadline Monitor> Tools> Worker Scheduling> Select the group on the left side> Then take a screenshot and share
- Share the screenshot of Idle detection settings of the Workers: Deadline Monitor> Tools> Idle Shutdown and Machine Startup
- Launcher is responsible for starting up and shutting down the Worker so I need Launcher logs from the machine in question. The Launcher logs live locally on the machine in question in application logs.
- What is the value of
LaunchSlaveAtStartup=in Deadline Client configuration file from the machine in question, please check the value in both global and per user client configuration file
For#4 if the value is set to 1 or True, then every time when you startup the Launcher the Worker starts up automatically. You will need to set it to False if you are restarting Launcher manually or via a script. Launcher logs will tell more.
Hello,
Sorry for long response time.
I have shared idle shutdown, machine startup and worker scheduling screenshots.
I don’t know how many logs you need, but my machine has saved alot of different logs, so I will just send you the ones generated today.
The value of LaunchSlaveAtStartup is 1. I don’t think this is an issue since the launcher is always running and so should never start/restart.
logs.7z (72.6 KB)
Also, worker keeps opening multiple instances if I don’t shut them down manually…
