The deadline monitor doesn’t refresh correctly on some of the pcs, when someone add a new job or change the priority etc…
We usually have to close the monitor and reopen it again for it do display the corrected changes.
Deadline 6 beta 6: 6.0.0.49200
Windows 7 for client, windows server 2003 sp2 for repository
Maya 2013
The next time this happens, can you send us the Monitor log from the machine that isn’t able to see the updates? You can find the Monitor log by selecting Help -> Explore Log Folder.
We can’t seem to reproduce this here, but maybe there might be an error occurring that shows up in the log.
Thanks!
Ok Just to clarify things,
The deadline monitor was already opened on PC04.
I’ve changed the priority of a job on the deadline monitor on PC02 from 54 to 55.
Got back to see if it changed on PC04, but the priority was still 54, we had to close the monitor and reopen it again to see the changes.
I’ve attached the logs files:Deadline monitor Log files.zip (1.51 KB)
We also have another issue in the deadline monitor on one of the pcs:
The interface UI always revert back to default, we had to save the UI changes and load it each time we opened the monitor
Ok, got something new,
Once i got back to check the PC04 again i noticed that the priority changed after a lot of time.
In fact what really happened is that it does not refresh automatically unless something occurs: Like for example a new slave added to the job, or maybe a task completed or closing a slave(that seems to trigger the refresh of the jobs). Same thing goes to pool or group.
Ah, thanks for that! We were able to reproduce. This should be fixed in beta 7.
I’m guessing there is an issue with the currently saved settings. Can you send us the monitor logs from this PC?
Ok, I’ve attached the monitor log of the pc, and the saved layout we load each time.
Deadline Monitor Logs.zip (11.2 KB)
Thanks! There doesn’t appear to be any errors, so that’s at least a good thing.
Just to confirm, is the problem that your panels aren’t maintained, or that the splitter locations between them aren’t maintained? In my tests with your layout, the panels were maintained, but the splitters were in different locations. After some more testing, it appeared that the splitter problem only occurs if the Monitor is maximized on close, and actually doesn’t seem to be related to the loading and saving of the layout files.
Does this sound like the behavior you’re seeing?
Yes, it’s actually the behavior we are getting.
Thanks for confirming! We’ve logged it as a bug.
I don’t know if it was supposed to be already fixed in beta7 but its still doing the same problem.
Which problem: the refresh issue or the splitter locations?
The refresh issue should have been fixed in beta 7. The splitter location issue will be fixed in beta 8.
Cheers,