D9,D10 Remote Admin IS enabled but they say its not

Deadline
1

|systemname|LaunchSlave ~|2021/05/10 15:58:47|Failed|Failure: cannot accept a connection because Remote Administration has been disabled under Client Setup in the Repository Options|

Remote Admin is very much enabled in via the suggested route (Configure Repository options)
image

systemctl status deadline9launcher.service
● deadline9launcher.service - LSB: Deadline remote communication.
Loaded: loaded (/etc/init.d/deadline9launcher; generated)
Active: active (exited) since Mon 2021-05-10 17:32:24 UTC; 2h 30min ago
Docs: man:systemd-sysv-generator(8)
Process: 2404 ExecStart=/etc/init.d/deadline9launcher start (code=exited, status=0/SUCCESS)
guy@place:~$ !265
systemctl status deadline10launcher.service
● deadline10launcher.service - LSB: Deadline remote communication.
Loaded: loaded (/etc/init.d/deadline10launcher; generated)
Active: active (exited) since Mon 2021-05-10 17:32:24 UTC; 2h 31min ago
Docs: man:systemd-sysv-generator(8)
Process: 2420 ExecStart=/etc/init.d/deadline10launcher start (code=exited, status=0/SUCCESS)

/opt/Thinkbox is RWXRWXRWX at the moment for torubleshooting.

D9/D10 Launcher listening ports are open:
nmap -Pn -p 17000-17099 SYSTEMNAME
PORT STATE SERVICE
17000/tcp open unknown
17001/tcp closed unknown
17002/tcp closed unknown
17003/tcp closed unknown
17090/tcp open unknown
17091/tcp closed unknown
17092/tcp closed unknown
17093/tcp closed unknown

2

You’ve got enable the whitelist checked and nothing in the list.

Select disable white list and allow all machine, or add some ‘commands’ into the whitelist

EDIT: corrected 'IP’s to ‘commands’ thanks to Bobo’s comment below

1 Like
3

Just to clarify, the list is for the COMMANDS that are allowed, not the IPs of the machines.
If set to no list, all commands would be allowed.

2 Likes
4

:frowning:
Sadly, our D9 repo does have this “Whitelist enabled” but our D10 config doesnt so since both Linux D9s D10s are experiencing same error… its loooks like theres no pattern here.

Do you have any other suggestions??

5

You don’t have the option underneath that shows this :-
’Disable the allow list. Allow ALL remote commands’
?
image

6

Our D9 has enable allow list radio button selected.
Our D10 has disable the allow list radio button selected.

Both give the same error.

Any ideas?

7

HI just to clarify, our Deadline repo config D10 and D9 do have the Remote Control as pictured…
The point is that one is disable allow list
the other is enable allow list
and
they exhibit the same behaviour.

Is this because the Deadlines cant reach a network resource? Is there some way for me to find out exactly?