If you’ve found this article looking for how to set up idle detection, check out this page in the documentation for details.
Assuming you’ve set up idle detection with those steps, let’s go through the usual reasons it fails and how to resolve them.
1 . Is the Deadline Launcher running on the workstation?
The Launcher’s process will be named deadlinelauncher.
- On Windows you can check for the process in the Task Manager.
- On MacOS use the Activity Monitor
- On Linux, it will depend on the distribution you’re running. From a terminal run
ps aux | grep deadlinelauncher | grep -v grepto see if deadlinelauncher is running.
If deadlinelauncher isn’t running, start it from the Start Menu shortcut or by logging out and back in.
2. Is the Deadline Launcher running as a Windows service or a Linux/MacOS daemon?
Services/daemons do not have permission to inspect activity of users. All operating systems have this limitation. Idle detection will not work when the Launcher is run this way.
2.1 How to tell if the Launcher is running as a service?
On Windows, open the ‘Services’ window and look for ‘Deadline 10 Launcher Service’.
On Linux, run
systemctl status deadline10launcher.service in a terminal to see if the service is present and running.
On MacOS, look for
com.thinkboxsoftware.deadlinelauncher.plist file in
/Library/LaunchDaemons. If it’s present, the Launcher is installed as a service.
How to disable the Launcher service if needed
To stop and uninstall the Launcher, run the following Deadline Command:
This will stop and remove the existing Launcher service.
Troubleshooting Idle Detection
Once you have checked the above items, the next place to look will be in the application logs.
The logs will be on the machine in one of these locations and named deadlinelauncher-[hostname]-[date]-[increment].log:
Mac OS X: /Library/Logs/Thinkbox/Deadline10
From this log look for lines that start with ‘Scheduling Group’ as this should explain why the Worker has or has not been started.
For example, if idle detection hasn’t seen the machine being idle long enough you’ll see something like this:
Scheduling Group "WorkerSchedulingGroup" GroupStartBlocked: "System is not idle long enough. Group requires 180000ms, system has been idle for 5500ms"
If the Launcher log has errors or isn’t clear, please reach out to the support team at awsthinkbox.zendesk.com.