# Clock Drift on Azure Ubuntu VM **URL:** \ **Category:** Ignition\ **Created:** [July 21, 2017, 1:12pm UTC](https://forum.inductiveautomation.com/t/clock-drift-on-azure-ubuntu-vm/14855 "2017-07-21T13:12:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\ **Post date:** [July 21, 2017, 1:12pm UTC](https://forum.inductiveautomation.com/t/clock-drift-on-azure-ubuntu-vm/14855/1 "2017-07-21T13:12:53Z")
Ignition 7.9.3 just installed on Ubuntu Azure VM, trial license. CPU and memory usage is very minimal (close to 0), only one project set up, no tags created yet, no database activity, etc. Server CPU and memory usage is also minimal (close to 0). About 12 hours after installation there were about 50 Clock Drift warnings over a 15 minute period. 24 hours later the same thing happened. This flurry of Clock Drift warnings occurs periodically ever few hours now. The actual deviation cycles between positive and negative values for subsequent warnings. For example, if the first warning is -1400, the next one will be 1400, then -1400, and so on. Any ideas? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [July 21, 2017, 3:24pm UTC](https://forum.inductiveautomation.com/t/clock-drift-on-azure-ubuntu-vm/14855/2 "2017-07-21T15:24:58Z")
Sounds like either A: the VM is being paused by the host operating system or B: the guest is trying to synchronize with a network time provider and failing. ---
**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\ **Post date:** [July 21, 2017, 4:34pm UTC](https://forum.inductiveautomation.com/t/clock-drift-on-azure-ubuntu-vm/14855/3 "2017-07-21T16:34:17Z")
I don’t think it is A, the time between Clock Drift events is small. The Drift error is typically between 1.2 and 2.0 seconds. Do you have any suggestions on where I should look for B? ---
**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\ **Post date:** [July 24, 2017, 3:05pm UTC](https://forum.inductiveautomation.com/t/clock-drift-on-azure-ubuntu-vm/14855/4 "2017-07-24T15:05:46Z")
A bit more information… The clock drift error increases with time. It started at just over 1 second and has gradually increased with each error to now over 5 seconds. Any more ideas?