Stubborn slaves that won't delete

Discussion and Support of Deadline, the Render Management System
reform
Posts: 7
Joined: Wed May 21, 2008 4:02 am

Stubborn slaves that won't delete

Postby reform » Tue May 16, 2017 7:42 am

I'm trying to delete old slaves from my monitor, but they keep on coming back.
Can someone explain what I need to do to premenantly remove slaves from the monitor?
I've stopped them, then disabled them, then deleted them, but they always eventually pop back in to existance.
Any ideas?
Thanks
p.

kwatts
Posts: 51
Joined: Tue Mar 01, 2016 10:34 am

Re: Stubborn slaves that won't delete

Postby kwatts » Tue May 16, 2017 9:41 am

Hi,

Occasionally what happens is when you remove the slaves from the monitor it doesnt clean up the files on the slave that define the extra instances.
Manually removing them will fix the problem.

So will need to delete the ini files on the slave that define the old slave definition.
For example on windows the path to the ini files is:
C:/ProgramData/Thinkbox/Deadline7/slaves

there will be more then one .ini file here.

Delete all except the ".ini" , which is the main slave definition.

Hope this helps.
Cheers
Kym

*edit added some more info

eamsler
Posts: 1827
Joined: Thu Dec 16, 2010 1:02 pm
Location: Winnipeg, MB, Canada

Re: Stubborn slaves that won't delete

Postby eamsler » Tue May 16, 2017 1:42 pm

I'd delete the Slave executable from those old machines if you absolutely never want to see them again. Any time the Slave starts, it'll re-register itself into the database.

The only way to stop it would be to remove the Slave from the machine altogether.
Edwin Amsler
Head of Support
Thinkbox Software Inc
+1-866-419-0283 ext 804

Winnipeg

reform
Posts: 7
Joined: Wed May 21, 2008 4:02 am

Re: Stubborn slaves that won't delete

Postby reform » Wed May 24, 2017 4:51 am

Thanks for your replies.
I tried deleting the ini file, but the slaves kept on reappearing.

I can't remove the excecutable as I do want 1 slave to remain, I just want to delete the additional instances I created.
Is there not a more robust method for removing slaves, or is this just some kind of known bug?
Thanks
Patrick

eamsler
Posts: 1827
Joined: Thu Dec 16, 2010 1:02 pm
Location: Winnipeg, MB, Canada

Re: Stubborn slaves that won't delete

Postby eamsler » Wed May 24, 2017 9:17 am

I wonder if someone wrote some script that re-creates or re-starts multiple Slaves.

The main driver is supposed to be the Launcher which reads the names of the ini files and starts each slave using the "-name [prefix]" flag. That prefix is decided based on the file names ending with "ini" in that folder. Here's mine for example:

Code: Select all

/Users/Shared/Thinkbox/Deadline9/slaves
Mobile-029:slaves edwin.amsler$ ls -la
total 16
drwxrwxrwx  4 edwin.amsler  wheel  136 17 May 09:58 .
drwxrwxrwx  9 root          wheel  306 12 Apr 15:32 ..
-rw-r--r--  1 edwin.amsler  wheel  119 17 May 11:18 .ini
-rwxrwxrwx  1 edwin.amsler  wheel  119 17 May 09:58 1.ini


And my launcher log:

Code: Select all

Mobile-029:Deadline9 edwin.amsler$ cat deadlinelauncher-Mobile-029-2017-05-24-0001.log
2017-05-24 09:13:41:  BEGIN - Mobile-029.local\edwin.amsler
2017-05-24 09:13:41:  Operating System: Mac OS X 10.12.4
2017-05-24 09:13:41:  CPU Architecture: x86_64
2017-05-24 09:13:41:  CPUs: 8
2017-05-24 09:13:41:  Video Card: Intel Iris Pro
2017-05-24 09:13:41:  Deadline Launcher 9.0 [v9.0.2.0 Release (89e276a72)]
2017-05-24 09:13:41:  Launcher Thread - Launcher thread initializing...
2017-05-24 09:13:41:  creating listening socket on port: 53026
2017-05-24 09:13:41:  writing listening socket to launcher file: 53026
2017-05-24 09:13:41:  Launcher Thread - Launcher thread listening on port 17090
2017-05-24 09:13:41:  WARNING: Authentication is specified as required in Database Connection Settings file, but no credentials were found.
2017-05-24 09:13:42:  Launching Slave:
2017-05-24 09:13:42:  Launching Slave: 1
2017-05-24 09:13:42:  WARNING: Authentication is specified as required in Database Connection Settings file, but no credentials were found.
2017-05-24 09:13:43:  Auto Configuration: Picking configuration based on: Mobile-029.local / 192.168.5.114
2017-05-24 09:13:43:  Auto Configuration: No auto configuration could be detected, using local configuration
2017-05-24 09:13:43:  WARNING: Authentication is specified as required in Database Connection Settings file, but no credentials were found.
2017-05-24 09:13:44:  Launcher Thread - Remote Administration is now disabled
2017-05-24 09:13:44:  Launcher Thread - Automatic Updates is now disabled


The running Slaves:

Code: Select all

Mobile-029:Deadline9 edwin.amsler$ ps aux | grep slave
edwin.amsler      7111  56.5  1.0  2918052 164968   ??  S     9:13am   0:10.00 DeadlineSlave9 --runtime=v4.0 --config /Applications/Thinkbox/Deadline9/Resources/deadline_mono_config /Applications/Thinkbox/Deadline9/Resources/deadlineslave.exe -name 1
edwin.amsler      7110  16.6  0.9  2911340 159240   ??  S     9:13am   0:07.57 DeadlineSlave9 --runtime=v4.0 --config /Applications/Thinkbox/Deadline9/Resources/deadline_mono_config /Applications/Thinkbox/Deadline9/Resources/deadlineslave.exe


Now, if the Slaves *are* started with the "-name" flag, they will re-create those files. That means if there's some script that was written or a remote command being sent those files will be created.


Actually, maybe power management has a list of those duplicate Slaves and is purposely re-creating them? Can you take a look at "Tools", then "Power Managment" and see if you're using "Machine Startup"? If so, make sure those other Slaves aren't listed in your active PM groups.
Edwin Amsler
Head of Support
Thinkbox Software Inc
+1-866-419-0283 ext 804

Winnipeg


Return to “Thinkbox Software - Deadline”

Who is online

Users browsing this forum: No registered users and 1 guest