?
Am I missing something here?
I have found the deadline launcher “launches” but it doesn’t launch the slave. Also, it doesn’t seem that I can do anything with the launcher. I am using the latest version of mono (2.4.7 I believe) and deadline 3.1, OSX 10.5.6. I can’t find anywhere to configure the slave to start on boot.
Is there somewhere to config?
Also, since there is no GUI showing up when the launcher starts, there is no way to quit. I have to force quit it.
The launcher should have a display. It could be that the installer isn’t setting up the auto start properly. I believe you can use the Login Items for your account to launch the Deadline Launcher application instead of the launcher unix executable file. I just tried this out here and it seems to work fine.
We’ll see if we can fix the installer to launch the launcher application instead of the unix executable in the next release.
Cheers,
Here is how my login items is currently configured. With the Deadline 3.1 final, it automatically puts the launcher app in “login items.”
By the way,
I have found this does not happen on an older beta of deadline 3.1.
Or, could it be the latest version of mono causing this?
any word on this?
I am able to replicate it every time by installing the latest version of mono available on the web and deadline 3.1.
Sorry for the delay. Most of us are at NAB this week, so we haven’t had a chance to look into this further. What happens when you run the launcher normally? Does the launcher interface get displayed, or is it still hidden? Also, when the launcher runs on startup, it should write to a log in /Applications/Deadline/Resources/logs, so if an error is resulting in this behavior, it should be printed there. The next time you reproduce this, can you send us the most recent launcher log and so we can take a look?
Thanks,
Even when I launch normally, it is still hidden. The log doesn’t show any errors. I have attached the latest log.
This happens on every machine I have tried it on.
deadlinelauncher(Chi-8c-render-150)-2009-04-22-0000.log (580 Bytes)
That’s really strange. Do the Slave or Monitor applications work if you launch them from /Applications/Deadline? Another thing - do you have X11 installed? Deadline doesn’t run on top of X11, but Mono uses some X11 libraries for the interface code. If X11 isn’t installed, that could explain the problem.
Cheers,
Not sure exactly what it is. I am remoting into these machines, It is possible the launcher is launching somewhere outside the viewable part of the screen.
I just did a new install of OSX on a machine and it seems to be okay there. I will probably use this machine as a new image…
thanks for the help.
Hi there. We’re running into the same issues.
Monitor and Slave look just fine, but the Launcher doesn’t show up.
Log looks exactly like yours.
Also, when trying to shutdown the machine, the Launcher hangs and we have to forcequit it.
Another window-issue is inside the Monitor: when viewing the error reports of a job (Cmd+E), a window of 100x550px pops up, but you cannot resize it! So we have to use a windows machine to check those reports.
Again, I’m not sure if this was still working while we had OSX 10.5.6.
Now we’re on 10.5.7 an no way back…
Client:
OS X 10.5.7
Mono 2.4_7
X11 (XQuartz 2.1.6 (xorg-server 1.4.2-apple33))
We still haven’t been able to reproduce this problem. We’ve tested on an Intel with 10.5.6 and two PPCs with 10.4.11 and 10.5.6. If you can think of anything particular about your setup that might cause this to occur, let us know!
This is an issue with Mono on OSX. Applications running under Mono don’t respond to normal Mac messages, like being told to shudown. We’ve logged this as a bug, and hopefully it is addressed in Mono 2.6 (which is supposed to include an OSX update).
We have successfully reproduced this problem, and will make sure it gets fixed for the next release. Thanks for bringing this to our attention!
Cheers,