Hi, I’ve tried Deadline with two workstations without issue. I was trying it for the first time on a server, running as as service. When I look at the configuration view, the server shows up as the launcher is running, but when I look at the Monitor window, the slave doesn’t show up - Even when viewing from the server itself. Surely the slave should be showing up in the monitor, even when running as a service, correct?
Khye
Hi Khye,
The launcher service and the slave are actually separate applications. If you launch the Monitor on the same machine, you should be able to test launching the slave from the command line by running this:
deadlinelauncher.exe -slaveThen check the Task Manager to see if deadlineslave.exe shows up. If it doesn’t, open the Monitor on the machine and select Help -> Explore Log Folder. Send us the most recent Launcher log and Slave log (if there is one) and we’ll take a look.
Cheers,
From the logs it appears everything is fine, but there is no deadlineslave.exe showing up in processes or services.
Launcher:
2010-11-12 17:41:41: BEGIN - RSERVER01\SYSTEM
2010-11-12 17:41:41: Start-up
2010-11-12 17:41:41: 2010-11-12 17:41:41
2010-11-12 17:41:41: Deadline Launcher 4.1 [v4.1.0.43205 R]
2010-11-12 17:41:49: Launcher Thread - Launcher thread initializing...
2010-11-12 17:41:50: Perfoming remote admin check
2010-11-12 17:41:50: Remote Administration is now enabled
2010-11-12 17:41:55: Launcher Thread - Remote administration is enabled
2010-11-12 17:41:55: Launcher Thread - Launcher thread listing on port 5042
2010-11-12 17:42:55: Perfoming remote admin check
2010-11-12 17:44:59: Perfoming remote admin check
2010-11-12 17:48:02: Perfoming remote admin check
2010-11-12 17:52:06: Perfoming remote admin check
2010-11-12 17:56:53: fe80::89dc:1b3:e9c8:ec96%11 has connected
2010-11-12 17:56:53: Launcher Thread - Received command: LaunchSlavePromptForUpgrade
2010-11-12 17:56:53: Launcher Thread - Responded with: Success|
2010-11-12 17:57:18: Perfoming remote admin check
2010-11-12 17:59:51: fe80::89dc:1b3:e9c8:ec96%11 has connected
2010-11-12 17:59:51: Launcher Thread - Received command: LaunchSlavePromptForUpgrade
2010-11-12 17:59:51: Launcher Thread - Responded with: Success|
Slave
2010-11-12 17:59:51: BEGIN - RSERVER01\SYSTEM
2010-11-12 17:59:51: Start-up
2010-11-12 17:59:51: 2010-11-12 17:59:51
2010-11-12 17:59:51: Deadline Slave 4.1 [v4.1.0.43205 R]
2010-11-12 17:59:53: slave initialization beginning.
2010-11-12 17:59:53: Info Thread - Created.
Ryan, I figured it out - I was in the trial mode and the repository had already used two windows 7 PCs, and when the servers tried to connect it would hang trying to find the license. I assumed that the limit to two machines meant two active slaves, not two registered computers. Deleting the two PCs from the Repository/Slaves allowed the servers to finish launching the slave process.
Although I’m not a paying customer (yet) If I was and had typed the IP incorrectly for the license server, the GUI version gives you the notification, but I suppose the service keeps that silenced. I’m surprised it didn’t show up in the log.
Thanks,
Khye
Hi Khye,
Glad to hear you figured out the problem, and you’re right, the slave should write out licensing issues to the log. We should be able to address this issue for the next release.
Cheers,