Let me preface this with i know next to nothing about how Mac’s work, every other system i’ve set up on deadline is windows based. So we are trying to get the one mac in our studio up and running, we have installed the correct version number, I have got it to connect to the repository on the windows system. I know this cause the mac shows up in the slave list on the monitor.
Now the problem we are having is that since installing the program and connecting to the repository the one time at set up we have yet to get Deadline to actually run. When we try to launch the monitor, slave, or launcher the icon will appear in the task bar momentarily and then immediately disappear.
has anyone had an issue similar to this? and what might i try or where might i look to troubleshoot this.
Cheers,
A couple questions:
- Which version of OS X?
- Which version of Mono?
- Is X11 installed on the machine?
Also, can you try opening a terminal and running the following command:
deadlinemonitor
If an error occurs, maybe it will be printed to the console and you can send it to us.
Cheers,
OSX 10.5.7
mono 2.4_7
X11 2.0
and we got this from the terminal
A SocketException occurred while checking if the port number 5162 is in use. Check to make sure that this machine is getting its host name from your DNS server correctly.
Deadline Monitor 3.1: No such host is known (System.Net.Sockets.SocketException)
at System.Net.Dns.hostent_to_IPHostEntry (System.String h_name, System.String[] h_aliases, System.String[] h_addrlist) [0x00000]
at System.Net.Dns.GetHostByName (System.String hostName) [0x00000]
at System.Net.Dns.GetHostEntry (System.String hostNameOrAddress) [0x00000]
at FranticX.Net.NetUtils.GetIPAddress (System.String machineNameOrIpAddress) [0x00000]
at FranticX.Net.NetUtils.GetIPAddress () [0x00000]
at FranticX.Net.SocketUtils.IsSocketInUse (Int32 port) [0x00000]
at Deadline.Applications.MonitorApplication.RunMonitor (System.String[] args) [0x00000]
Looks like it has something to do with our DNS server, no?
Thanks for the help
Yeah, that’s what it looks like. If you can get the machine to pull its name from the DNS server correctly, that should fix the problem.
Cheers,
okay we got our tech guy in Atlanta to square up the DNS server name issue (props to him). Now when we execute the deadlinemonitor command from the terminal it simply pops up a second command prompt for a split second, goes away, and then prompts the to the next command line in the terminal. It doesn’t display any errors or any text of any kind. would we need to re-install deadline for any reason after making changes to the DNS??
Also another strange clue to this. If we unplug the network cable from the system and open up deadline, it will work, it won’t do anything but ask what happen to the repository but the program runs and functions…if we take that a step further and quickly plug in the ethernet, connect to the repository, hold your left pinkie up and hit connect, Deadline will connect and show up the deadline monitor on the host system and then it closes itself and goes back to being stubborn. I don’t know if that tells you anything but thought it was odd.
Ok, now that the Monitor is running, hopefully it is writing to its logs. The logs can be found in /Applications/Deadline/Resources/logs. If the Monitor is writing to a log, please post it and we’ll take a look.
Thanks,
There were no logs from today’s activities, we had to do the “unplug ethernet, start deadline and plug back in” deal…after that we got these two seperate logs…again after we connect the cable back up it stays up just long enough for us to connect the server to the repository and launch the slave, then it goes poof.
[code]LOG 1
2009-06-16 10:12:38: BEGIN - jma-m-010.local\kwitherspoon
2009-06-16 10:12:38: Start-up
2009-06-16 10:12:38: 2009-06-16 10:12:38
2009-06-16 10:12:38: Deadline Launcher 3.1 [v3.1.0.35390 R]
2009-06-16 10:12:38: Launcher Thread - Launcher thread initializing…
2009-06-16 10:12:38: Perfoming remote admin check
2009-06-16 10:12:38: Launcher Thread - Remote administration is disabled
2009-06-16 10:12:38: Launcher Thread - Launcher thread listing on port 5042
2009-06-16 10:13:38: Perfoming remote admin check
2009-06-16 10:14:56: Enqueing: Launch Monitor
2009-06-16 10:14:56: Dequeued: Launch Monitor
2009-06-16 10:15:05: Enqueing: Launch Monitor
2009-06-16 10:15:05: Dequeued: Launch Monitor
2009-06-16 10:15:36: Enqueing: Launch Slave
2009-06-16 10:15:36: Dequeued: Launch Slave
2009-06-16 10:15:38: Perfoming remote admin check
LOG 2
2009-06-16 10:12:22: BEGIN - jma-m-010.local\kwitherspoon
2009-06-16 10:12:22: Start-up
2009-06-16 10:12:22: Deadline Monitor 3.1 [v3.1.0.35390 R]
2009-06-16 10:12:22: 2009-06-16 10:12:22
2009-06-16 10:15:02: Monitor.MainWindow_FormClosing
2009-06-16 10:15:02: Listener Thread - OnConnect: Listener Socket has been closed.
2009-06-16 10:15:02: Monitor.MainWindow_FormClosed
[/code]
Weird… have you tried restarting the machine to see if that helps?
restarted after almost every step hoping it would fix it, unfortunately that old stand by failed us.
Do any of the other applications start, like the Slave or Pulse? If so, maybe post their logs as well.
The Launcher seems to be running fine, according to the log. Are you seeing the Launcher application? If not, use the Activity Monitor to kill any running Deadline applications, and then from a terminal, run ‘deadlinelauncher’. Let us know if the launcher pops up. If it does, try launching the slave and monitor applications from it to see if you get any different results.
Cheers,
Nope, none of the programs start up properly from command . When I run launcher from command it tells me there is another launcher and that port 5042 is already in use and it’s exiting the program cause a version of launcher is already running. I checked the activity monitor and there is no “deadlinelauncher” running.
I just tried re-installing and installing with different port numbers, neither seemed to do anything different.
Anything else I can try to verify there is a copy of deadlinelauncher running and it’s using the ports properly ?
Boo problems…hurray BEER!
Is there a “mono” application running? If so, that may actually be the launcher, so try killing that as well.
So after doing extensive network troubleshooting with IT, we’ve determined that this is may not be network related. What we have discovered is that going into the system startup of a MAC (Click on the Apple>>System Preferences>>Accounts>>Select a profile>>Select Login and changing the DeadlineLauncher and the DeadlineLauncher.exe drastically changes the behavior of the software (even though items are selected to run at login). If i replace DeadlineLauncher.exe with DeadlineSlave.exe, I no longer get the “port already in use…application is already running” error. Could there be a different, working configuration including DeadlineLauncher and DeadlineLauncher.exe here or in my resources directory?
Hey there,
Could you clarify what you’re changing in the Login Items that gets this to work? From the sounds of it, you are switching the startup item to run the Slave on startup instead of the Launcher? It also sounds like the entries were pointing to the .exe’s in the bin directory… They should be pointing to the .app’s in the main Deadline folder for them to launch properly. Please correct me if I interpreted any of that wrong 
Either way, it sounds like you’ve got it working properly if you don’t have the Launcher in the Startup Items? Maybe try clearing out the Deadline entries in the Login Items and create a new entry pointing to the DeadlineLauncher app in /Applications/Deadline, and restart to see if that launches the Launcher properly on startup now. If not, try running “deadlinelauncher -shutdown” from the command line, followed by the “deadlinelauncher” command to see if that gets anywhere.
Cheers,
Ok, here are screen shots that show the results from varying combinations.
this combination didn’t yield any monitor results.
Hey there,
Try only having the DealineLauncher Application in there (ie, the one with the icon), and delete the second entry. The .exe’s giving you all that jarbled text makes sense, since they aren’t native and need to be run through Mono to work properly; which is basically what the Mac application does. The Unix Executable versions should work fine as well (since it’s basically just a script that launches the Mac App), and this is probably why you’re getting the ‘launcher already running’ errors when both the Application and the Unix Executable are in there – it’s trying to run the launcher twice on startup.
Though even with this error, you should still be getting the GUI popping up from the first Launcher starting up… Maybe try deleting the App entry, and only having the Unix Executable (ie, deadlinelauncher) in there if it’s still not giving you a GUI with only one entry.
If you’re still not getting a GUI coming up for the launcher after that, try running the “deadlinelauncher -shutdown” command, followed by “deadlinelauncher -slave”.
Cheers,
OK. With the single Deadline file in startup, the application tries to start (bounces in the dock), but closes within seconds. I am now getting the same reaction out of two different Macs (i just downloaded Mono and Deadline onto another Mac). Is there anything i should be checking @ the repository settings?
Thanks,
Check the most recent Launcher logs in /Applications/Deadline/Resources/logs. Hopefully the Launcher is printing out some information that will explain the problem. Feel free to post a log for us to take a look at.
Cheers,
before doing so, an idea hit me that prompted two questions
- would i need software installed @ the repository to allow afp sharing for mac access? check out -> grouplogic.com/products/extremez-ip/
- is the correct syntax from my mac is smb://servername/deadlinerespository or \servername\deadlinerepository?
thanks,
polymangler’s IT
