Here is a head scratcher, maybe someone else with a DCP2K can report if we are alone in this anomaly.
Our up to date DCP2K4 appears to have applied the Daylight Savings Time correction EARLY (Nov 1st this year). I'm not in the building but can check tomorrow. My co-projectionist reported this. We are suddenly an hour out of real-time and somewhere they were able to see that it is reporting the "Next" time-change to be April 2027.
Our server has never had a TMS or used a local or internet time server for sync other than during intentional corrections. It does drift. We applied a big correction not too long ago and still have correction quota available. But is having a NTP server configured necessary to keep it picking the correct DST change dates too?
Most of this festival is unencrypted. During prep yesterday I noted one tech window KDM that was 15 min after the scheduled hour venue window, but I did NOT catch that it appeared to be due to our server time having bonked itself out by a full hour!! Honestly I was too busy dealing with moving all their festival features and content off the delivered ExFAT drives so that we did not fall behind on ingesting on Day 1.
The logical follow up is does it have the correct DATE! lol. I'll have to investigate tomorrow.
But I think I can rule that out from home. The festival keys were extremely tight, within the day/hour. So they would have been way out in terms of validity window if the server date was wrong too.
Due to some serendipitous tech window schedule shifting by the festival anyway, this issue did not bite us day 1. But it may as we get the outstanding keys. I'm tempted to do the NTP time correction steps first thing in the morning.
Our up to date DCP2K4 appears to have applied the Daylight Savings Time correction EARLY (Nov 1st this year). I'm not in the building but can check tomorrow. My co-projectionist reported this. We are suddenly an hour out of real-time and somewhere they were able to see that it is reporting the "Next" time-change to be April 2027.
Our server has never had a TMS or used a local or internet time server for sync other than during intentional corrections. It does drift. We applied a big correction not too long ago and still have correction quota available. But is having a NTP server configured necessary to keep it picking the correct DST change dates too?
Most of this festival is unencrypted. During prep yesterday I noted one tech window KDM that was 15 min after the scheduled hour venue window, but I did NOT catch that it appeared to be due to our server time having bonked itself out by a full hour!! Honestly I was too busy dealing with moving all their festival features and content off the delivered ExFAT drives so that we did not fall behind on ingesting on Day 1.
The logical follow up is does it have the correct DATE! lol. I'll have to investigate tomorrow.
But I think I can rule that out from home. The festival keys were extremely tight, within the day/hour. So they would have been way out in terms of validity window if the server date was wrong too.
Due to some serendipitous tech window schedule shifting by the festival anyway, this issue did not bite us day 1. But it may as we get the outstanding keys. I'm tempted to do the NTP time correction steps first thing in the morning.


Comment