Hi, I can see I’m not the first to experience this but I couldn’t find a clear solution on the forum.
The problem I’m getting is that on certain machines I’m getting two slaves launching when the Launcher starts (the Launcher is set to launch Slaves automatically).
I’ve tried deleting the offending slaves from the Monitor and then also deleting the relevant folder in ~Library/Application Support/Thinkbox/Deadline7/slave but every time I restart or relaunch the Launcher they pop back up.
I should add that we have other set ups on other machines where this doesn’t happen. This machines are no different in the way their network/software is set up.
Sorry for the delay in getting back (I hadn’t set up notification).
I’ve attached a few logs and then here’s a screen shot of what I see in the Launcher.
Screen Shot 2015-04-16 at 10.58.31.png
If I select to launch slave ‘Render 02’ from the Launcher it seems to launch a slave called ‘Render 02-Render’. This is the name of the slave both on the slave and how it appears in the Monitor under ‘Slave name’. if I then try to launch ‘Render 02-Render’ from the Launcher nothing happens (presumably it’s already running’. If I try to launch ‘Render 02’ again it starts to launch and then quits. If I choose ‘Launch 2 slaves’ it will then also launch a second slave called ‘Render 02’.
Launcher is in the User start up items (OSX) and set to Launch Slave(s) at start up. Render 01 and Render 01-Render were launched. I then closed both Slaves down and started Render 01 from the Launcher. Render 01-Render started up instead.
deadlinelauncher-Render 01-2015-04-20-0001.log
I disabled ‘Launch Slave at StartUp’ and quit and restarted the Launcher then started Render 01. Render 01-Render started instead.
Sorry for the delay in getting back to you here. We are going to have to do some internal testing to see if we can reproduce this on our end, but your logs are quite helpful.
So where you would go on the slave Mac machine is to /Users/Shared/Thinkbox/Deadline7/slaves/ and delete all files in this directory. This will delete any excess slaves, and leave just the main slave that is the default.
We’ve also had this problem from time to time. (osx only studio) But we never figured out the reason why it happened.
One theory is that some of the slaves had wi-fi enabled in addition to its ethernet interface and somehow registered as two different slaves over each interface. But we never managed to reproduce this.
Another theory is that we had both afp and smb sharing running on our repository (for a couple of pc using freelancers) and that some of the clients switched protocol after they connected to the repo. And that way registered a new instance for the other protocol.
Just speculations of course but the symptoms went away when we switched of all wi-fi connections and turned of smb. But the symptoms does not automatically return when we turn wi-fi and smb back on
Most of the time when we see this, it’s due to the inability for a Mac to resolve the hostname, and a bug we had where the slave would then end up creating an extra slave of it’s own with the remote machine’s name. We did fix this bug, I believe, before Deadline 7, though.
Thanks all, it seems removing the .ini file in Users/Shared/Thinkbox/slaves might have done it.
If it helps with any bug hunting the machines affected by this are all connecting to an OSX Server afp file share. They are OSX 10.9.5 machines (other machines on same OS were not affected by this problem though).
Via terminal they all resolve to the hostname of that server no problem. i.e. $ host xxx.xxx.x.xx resolves to the hostname of that IP.
All machines only have one ethernet connection (i.e. no wifi etc).
These machines were on Deadline 6 and this problem popped up after installing 7.0 (without any special config).
