Deadline Slave not starting

Hello,

I have a problem with some machines which were integrated into our windows domain.
Before they just were simple workgroup members and everything worked fine.
Now they are integrated into the domain.
When I login with the admin account into the specific machine the slave starts fine.
After a reboot and login with a specific user the slave won´t start and I don´t even get an error message
It´s possible to create a new slave instance though which starts fine as well

Is there any possibility to share one instance for all accounts on this machine (windows domain accounts)

thanks in advance

That’s strange. Can you check the task manager and show processes for all users to see if the slave is perhaps running in the background? Only one slave with a given name can run on a machine at a time.

If that doesn’t appear to be the case, maybe try going to %PROGRAMDATA%\Thinkbox\Deadline\slaves and then delete everything in this folder. After that, try launching the slave again to see if that helps. This manual process is basically resetting the slave instances on the machine.

Hi Ryan,

there´s no other process running for any other user in the background.
While being logged in as the specific user I deleted the content of the slaves folder.
After that I was able to start the slave on the machine (with the current user account active)

Now I did a logout (not only switching the user) and logged back in as administrator (same machine)
Same problem now slave won´t start, so it looks like the instance of a slave is tied to a specific user? Is that possible?

Ok…
so i created a new slave instance for the admin account (now I have 2 instances in the launcher)
Now he starts the specific slave on each account.

When I rightclick the launcher he says “start 2 slaves”
So is he now always trying to start both instances and it only works cause he´s just able to start one?
I could live with that if it doesn´t generate any other problems.
Altough it´d be nice to have only one slave per machine, not user account.

It sounds like there may be a permission issue with the files in that slaves folder. Try setting the permissions on that slaves folder to give Everyone full control. I think that should fix the problem.

It did :slight_smile:
thanks Ryan!