Hi,
With beta 3 clients installed, I’m unable to launch any DL5 applications by double clicking them (or using Apple-O). I can launch them from the terminal, although there’s an error output that says :
./DeadlineMonitor: line 1: #!/bin/sh: No such file or directory
I’ve since installed beta 4 to the repository and had hoped to test the autoupgrade of nodes. I thought one option would be to set the ‘restart slave after task completion’ setting, but in each case this results in a ‘connection refused’ notification dialog coming up (even for the same machine, i.e. the one holding the repository is also working as a slave). I’ve never trusted autoupdate before, but it would be nice to know how this is intended to work and what I need to do to get it working. I’ve set the autograde setting to ‘true’ in the repository options, but guess that this doesn’t apply until each slave is restarted.
Sounds like you might have a borked OSX install. What happens if you enter
/bin/sh
and hit enter in the terminal? You should see your prompt change to ‘sh’. If that errors out, you may actually be missing sh on your machine (you shouldn’t, as sh is part of the OSX base install.)
/bin/sh itself works fine :
sierra:~ phil$ /bin/sh
sh-3.2$
sierra:Deadline phil$ open DeadlineMonitor.app
LSOpenURLsWithRole() failed with error -10810 for the file /Applications/Deadline/DeadlineMonitor.app.
I can launch Monitor directly by firing up DeadlineMonitor.app/Contents/MacOS/DeadlineMonitor
Hmm, a couple of separate things to try:
-
Run
sudo chmod -R 777 /Applications/Deadline
Then try opening Deadline Monitor.
-
Quit all apparent running Deadline programs. Run
ps aux
. Look for any lines that list any still running Deadline processes (they’ll have mono running too. Take note of their process id (the process id is the number right after the user (columns are also listed at the top of the output). Then run
sudo kill -9 X
where X is the process id (PID). You can also try
sudo killall mono
. If any Deadline processes are still running after that, they’re zombies and you’ll have to restart your machine to clear them out.
-
Check your Console for any error messages relating to LaunchServices, and/or corservicesd.
I’m able to use the .app packages to launch the Deadline applications on our test machines. Is this problem happening on all of your Macs, or just the one that you had this install problem with?
viewtopic.php?f=86&t=4591&start=20
Cheers,
Sorry, forgot the other half of your problem. Do you have Remote Administration enabled under the Launcher Settings in the Repository Options? If not, that could explain why you’re getting the “connection refused” error. If you do have this option enabled, check to make sure the Launcher is running on your nodes, since it acts as the hub of remote communication for each node.
Cheers,