AWS Thinkbox Discussion Forums

machine repeatedly losing its deadline.ini

Not sure why, but one of our artists reported that this happened to her twice already within a couple of days… His C:\programData\Thinkbox\Deadline6\deadline.ini gets reset, and she becomes unable to connect to the database.

The file only contained the following entries:

[Deadline]
MonitorProcessID=4948
MonitorListeningPort=49217
NetworkRoot=\inferno2\deadline\repository6
NetworkRoot0=\inferno2\deadline\repository6

Missing the license server information

Any ideas what could cause this?

That’s strange. We’re not sure what would cause this. Do you know if the current contents of the file are from after she launched the Monitor? I’m just curious because the information currently in there would have been set by the Monitor at launch. In other words, I’m wondering if the file just contained [Deadline] and nothing else. Regardless, this is a new one to us, and it’s not clear what could cause this behavior…

It just happened to another artist as well. He simply had this in the ini file:

[Deadline]
MonitorProcessID=2008
MonitorListeningPort=1190

We’ve logged this as a bug, although we are still unable to reproduce with some basic tests (ie: repeatedly starting and stopping the slave and monitor on a machine).

Cheers,
Ryan

Is that file ever written to, other then on monitor shutdown?
Maybe a racing condition between the launcher/slave/monitor trying to write to it?

Not sure. I suspect the monitor crashed on both artists’ machines though, as they usually only start it when it disappears, so it might somehow be related to a crash? (which happens every day for me on both of my machines, it vanishes by the morning)

Hey Laszlo,

It does appear to be a race condition that causes this (at least, that’s how I was able to reproduce the problem).

We should be able to address this using a lock file, and get this fixed in RC3.

Cheers,
Ryan

Glorious thanks!

Privacy | Site terms | Cookie preferences