After upgrading to beta7, all slaves are showing an unknown status (and some props are missing, like there is no version, machine name etc).
Hmm that shouldn’t happen. Running the slaves should clear that problem up, but we will look into it.
Doesnt seem to. My machine is lapro3067 that you see there, and despite running the latest slave it still shows that info
That’s interesting. Is the slave connected to the repository correctly? Can you provide the slave log from when it was launched?
Sure:
2016-02-10 14:39:08: BEGIN - LAPRO3067\laszlo.sebo
2016-02-10 14:39:08: Deadline Slave 8.0 [v8.0.0.50 Beta (dd3a9e577)]
2016-02-10 14:39:12: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2016-02-10 14:39:13: Info Thread - Created.
2016-02-10 14:39:14: The license file being used will expire in 23 days.
2016-02-10 14:39:16: Enabling render stat mail
2016-02-10 14:39:16: Installing site customize in OnSlaveStarted callback
2016-02-10 14:39:17: Calling runasadmin via: //s2.scanlinevfxla.com/exchange/software/managed/pythonScripts/sitecustomize/install.bat
2016-02-10 14:39:17: PsExec v1.94 - Execute processes remotely
2016-02-10 14:39:17: Copyright (C) 2001-2008 Mark Russinovich
2016-02-10 14:39:17: Sysinternals - www.sysinternals.com
2016-02-10 14:39:17: c:\users\laszlo~1.seb\appdata\local\temp\NoConsole.exe exited with error code 0.
2016-02-10 14:39:18: Auto Configuration: Picking configuration based on: lapro3067 / 172.18.8.91
2016-02-10 14:39:18: Auto Configuration: No auto configuration could be detected, using local configuration
2016-02-10 14:39:18: Scheduler Thread - Slave initialization complete.
2016-02-10 14:39:18: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Weighted, Balanced
2016-02-10 14:39:18: Scheduler - Using enhanced scheduler balancing
2016-02-10 14:39:18: Scheduler - Job chooser found no jobs.
2016-02-10 14:39:18: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Weighted, Balanced
2016-02-10 14:39:18: Scheduler - Using enhanced scheduler balancing
2016-02-10 14:39:18: Scheduler - Job chooser found no jobs.
2016-02-10 14:39:19: Scheduler Thread - Seconds before next job scan: 43The weird thing is, the data seems to be in the db…:
deadlineRS0:PRIMARY> use deadline8db_StatusInfo
deadlineRS0:PRIMARY> db.SlaveInfo.find( {"Name":"lapro3067"} )
{ "_id" : "lapro3067",
...
"Ver" : "v8.0.0.50 Beta (dd3a9e577)",
}Maybe its something with the monitor?
it shows the pool & group info correctly in the monitor, but pretty much nothing else…
Seems like its a problem with the monitor, thanks for the updates! We’re currently looking into this.
We are uncertain how to go forward, this build was rolled out on ~500 machines. Should we hold off with further installations till a fix is available?
Yeah you should hold off on this build. We are working on getting a new build together to address this issue along with a few other critical issues.
Awesome thanks!