As the title says… my monitor becomes non responsive and stops working for about 8 minutes when I want to edit the slave properties of a slave (online/offline state makes no difference).
In the taskmanager it shows running as if there’s nothing wrong, but I can’t select it anymore of bring it to the foreground.
This all happens on win10 pro 64b. tried it on a workstation and the machine running the deadline licenses… same result
edit: it seems to work now… might just have been as it was the first time… but did result in me killing the monitor a few times before I had the patience to wait really long
nope, nothing special to see there…
I might just have to write it off to the first ever time that deadline 9.0.2.0 monitor is opening the new slave’s slave-properties i guess.
I can also not reproduce it anymore… the properties open up fine now.
i’ll keep an on eye on it.
btw… any of you guys going to be at the EUE in the Netherlands this June?
So I’ve got the same issue with monitor hanging up from time to time. I couldn’t find the cause of this until today. It looks like it is related to the samba and files locking.
I’ve mange to find this entries in my /var/log/syslog file when monitor was non-responsive
Jun 2 14:14:26 XXX smbd[24683]: [2017/06/02 14:14:26.798445, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:14:26 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/FontSync/FontSync.param -- replying anyway
Jun 2 14:14:56 XXX smbd[24683]: [2017/06/02 14:14:56.809024, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:14:56 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/FontSync/FontSync.py -- replying anyway
Jun 2 14:15:26 XXX smbd[24683]: [2017/06/02 14:15:26.846944, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:15:26 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/FTrack/FTrack.param -- replying anyway
Jun 2 14:15:56 XXX smbd[24683]: [2017/06/02 14:15:56.859554, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:15:56 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/FTrack/FTrack.py -- replying anyway
Jun 2 14:16:26 XXX smbd[24683]: [2017/06/02 14:16:26.876987, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:16:26 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/NIM/NIM.param -- replying anyway
Jun 2 14:16:56 XXX smbd[24683]: [2017/06/02 14:16:56.892089, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:16:56 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/NIM/NIM.py -- replying anyway
Jun 2 14:17:26 XXX smbd[24683]: [2017/06/02 14:17:26.907070, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:17:26 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/NukeCleanup/NukeCleanup.param -- replying anyway
Jun 2 14:17:56 XXX smbd[24683]: [2017/06/02 14:17:56.927560, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:17:56 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/NukeCleanup/NukeCleanup.py -- replying anyway
Jun 2 14:18:26 XXX smbd[24683]: [2017/06/02 14:18:26.941889, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:18:26 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Puppet/Puppet.param -- replying anyway
Jun 2 14:18:56 XXX smbd[24683]: [2017/06/02 14:18:56.965092, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:18:56 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Puppet/Puppet.py -- replying anyway
Jun 2 14:20:27 XXX smbd[24683]: [2017/06/02 14:20:27.012901, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:20:27 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Salt/Salt.param -- replying anyway
Jun 2 14:20:57 XXX smbd[24683]: [2017/06/02 14:20:57.032835, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:20:57 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Salt/Salt.py -- replying anyway
Jun 2 14:21:27 XXX smbd[24683]: [2017/06/02 14:21:27.053980, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:21:27 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Shotgun/Shotgun.param -- replying anyway
Jun 2 14:21:57 XXX smbd[24683]: [2017/06/02 14:21:57.076908, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:21:57 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Shotgun/Shotgun.py -- replying anyway
Jun 2 14:22:27 XXX smbd[24683]: [2017/06/02 14:22:27.100179, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:22:27 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Spot/Spot.param -- replying anyway
Jun 2 14:22:57 XXX smbd[24683]: [2017/06/02 14:22:57.108193, 0] ../source3/smbd/oplock.c:701(oplock_timeout_handler)
Jun 2 14:22:57 XXX smbd[24683]: Oplock break failed for file DeadlineRepository9/events/Spot/Spot.py -- replying anyway
As soon as the last oplock timeout is off the monitor is back to normal.
Interesting part is that I’ve greped all my syslog files and this problem only applies to Deadline event files.
– edit
I’ve should probably add that I’m running Deadline 9.0.3.0 and repository is served via samba 4.3.11 installed on ubuntu 14.04.4 LTS. All workstations and render nodes have Windows 7, 8.1 or 10
