AWS Thinkbox Discussion Forums

Reports/Jobs subfolders being deleted

Deprecated Deadline 6 Beta Discussion
#1

I was going to post this as a bug report, but I’m pretty sure it was happening here before we came onto the beta.
Every now and then, I’ll notice that the log files aren’t being written out any more, because all of the subfolders in the Reports/Jobs folder have disappeared.
It’s simple to fix, I’ve got a backup copy of the subfolders that I simply copy over to the empty folder.

Since installing Beta 10, this has got much worse. Today alone the subfolders have disappeared 5 times already.
Also since installing Beta 10, we are getting a lot of error mesaages from the slaves, and because the subfolders keep disappearing, there is no way for me to check exactly what is going wrong every time.

From the few error messages that have been logged, they all seem to point to a problem with lightning.dlx:

Error in StartJob: ExecuteScript: Timed out waiting for the lightning 3dsmax plugin to acknowledge the ExecuteScript command.

I’ve done a search through the forums, and haven’t found anyone else having a problem with the subfolders disappearing, so is this something wrong with our setup here?

Cheers,

Dave

#2

Since writing the first post, this has happened two more times.
I’m not going to bother fixing it any more, I’ll just go without logging until I can find out why it’s happening.

Dave

#3

This problem happens if you have a Deadline 5.x client application (Slave or Pulse) still connecting to your Deadline 6 repository. Are you aware of any machines in your network that are still running version 5? One way to check is to look for a “slaves” or “pulse” folder in the repository root. If you see either, delete it. The next time a v5 slave or pulse connects, it should recreate one of those folders, and create an entry in the folder with its name. You can use that to track down which machine(s) is still running an old version.

#4

Thanks Ryan, I’ve just deleted a ‘slaves’ folder from the repository root, as soon as it pops up again I’ll track the bugger down :smiling_imp:

Cheers,

Dave

#5

We found the troublemaker, and things are now working as they should!

Thanks again Ryan,

Dave

#6

Awesome!

Privacy | Site terms | Cookie preferences