I have a problem, where one of my Limux machines (CENTOS 6.4) has Deadline running and decides to do some house cleaning; it is placing my slaves in a “stalled slave state”.
My threshhold is set to 2 hours.
The TZ, date and time on my Linux boxes are correct.
When submitting a job or just doing nothing, the offset detected by Deadline is +5 hours. If I submit a job at 13:00 EST -> Deadline indicates the job sumitted at 18:00EST (or 13:00 GMT).
This is a big problem. I am not sure if the problem is in the host or in the way Deadline is interpretting the time and offset sent by the client.
Thank you in advance.
Hello,
Can I have you set the clock on the machine to 13:00 GMT and see if that changes how the submission is appearing as in the repository? The clock should be the same between Deadline and the system clock.
Thanks Dwight.
Unfortunately that did not help either. It is still posting 5 hours ahead in Deadline Monitor as submission time…
Changed timezone, location, etc. It seems to be sending the information as if it were sending the time unformatted as GMT.
Might be more of a CENTOS thing than Deadline… But it is causing me headaches in Deadline.
Hello
Well, I am not sure other than the actual system/BIOS time being off. I am not sure why they are sending as GMT, but being received as EST. That is really bizarre. In looking through some stuff online, it does look like CentOS has had time based problems in the past, but no idea of the status of those numerous different bugs.