AWS Thinkbox Discussion Forums

can't launch deadline with new user account - mono/permissio

Hi,

I just set up a new user on my osx machine and when I try to launch any dealidne application (slave, monitor, launcher…) it just fails to open without an error.
When I try to launch deadline from the terminal it fails to start and instead prints usage information for mono, asif the DeadlineMonitor (or other deadline apps) were calling Mono incorrectly. A bit of a red herring…
I know it must be a permission problem as I can lunch and use deadline just fine with my account but I have no idea how to debug this. Mono and Deadline installations are all default and I did not change any permissions. UPon investigation the mono and deadlind eppas all seem to have the correct read/executable permissions so UI’m a bit stuck.

EDIT:
I just noticed that launching DeadlineMonitor in the terminal under my own accoutn still prints the Mono usage text, yet launching it via the regular icons works fine. So Mono may not be the culpriot after all.
I checked the repository permissions and they are all set to rwx for all.

Any ideas?

Cheers,
frank

UPDATE:

Turns out I was launching:
/Applications/Thinkbox/Deadline6/DeadlineMonitor.app/DeadlineMonitor
when I should have launched:
/Applications/Thinkbox/Deadline6/DeadlineMonitor.app/Contents/MacOS/DeadlineMonitor

When I run that one, I get a python error which is a bit more helpful:

[code]bash-3.2$ /Applications/Thinkbox/Deadline6/DeadlineMonitor.app/Contents/MacOS/DeadlineMonitor
‘import site’ failed; use -v for traceback
Python.Runtime.PythonException: ImportError : No module named warnings

Python.Runtime.PythonException: ImportError : No module named warnings

Exception on Startup: ImportError : No module named warnings (Python.Runtime.PythonException)

Deadline Monitor will now exit.
Shutting down finalizer thread timed out.
[/code]

Is this a bug? Shouldn’t a new user account just work with an already installed Deadline? This is still build 19 btw, I haven’t had time to install rc1 but will do so now.

Cheers,
frank

UPDATE:

After installing rc1 the problem went away so I’m all good now, but still curious as to what happened.

Cheers,
frank

Hey Frank,

This was one of the bugs that was fixed in the RC1 client installer. Glad to hear it fixed your problem!

Cheers,

  • Ryan

great, thanks.
I don’t like when problems just go away unexplained, but that reassures me now :slight_smile:.

Cheesr,
frank

Privacy | Site terms | Cookie preferences