I noticed a slave hanging on a job for 17 hours this morning (all other frames finished in about an hour or two). Deadline monitor reported that its active & rendering.
So i remoted into the box to see whats happening, and saw that deadline slave is in the taskbar minimized. I clicked on it, but it did not get maximized, instead a couple of seconds later it disappeared and started to self update itself (we rolled out beta 12 yesterday morning).
After this the job is still reporting that this slave is rendering it (17h:46:14 and counting), even though the slave is not even running.
After a while, the launcher reappeared on the box, but the slave did not start up.
The machine still says that “last status update” was 18s ago, the value it has been displaying for about 10 minutes (no change). When i try to manually start the slave from the launcher, nothing happens.
So at this point I manually shut down the launcher, restarted it. It took about 4-5 minutes to start up. The slave did not launch automatically, even though the checkbox to start slave at startup is turned on. Manually clicking on Launch Slave from the launcher, the slave starts, but again taking about 4-5 minutes.
cheers,
laszlo
