# ClockDrift Warning

**URL:** <https://forum.inductiveautomation.com/t/clockdrift-warning/55594>\
**Category:** Ignition\
**Tags:** ignition79, vision\
**Created:** [February 1, 2022, 11:48am UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594 "2022-02-01T11:48:33Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 1, 2022, 11:48am UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/1 "2022-02-01T11:48:33Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/1/415aa69436143d092429e003f243777c12f4bf2f.png)  
I am getting warning for clock drift in my logger.  
I went through couple of forum answers but didn’t really understood the cause of this warning.

PS: I have SQL Tags updating every 1 second/5 Seconds, do it really have to do with this warnings?

Regards,  
Richita Pandey.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 1, 2022, 1:01pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/2 "2022-02-01T13:01:38Z")

</div>

That’s likely a garbage collection “pause-the-world”. When happening so fast, that suggests you haven’t given your gateway enough memory to work with (set in ignition.conf and restart). Show your gateway’s Performance Status page.

---

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 1, 2022, 1:18pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/3 "2022-02-01T13:18:32Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/0/609a42c7b94db195f0cc7fed293bdeda8eb86db2.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 1, 2022, 1:28pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/4 "2022-02-01T13:28:54Z")

</div>

Seems like plenty of memory…

Is this 7.9 or 8.x? Might be worth making sure G1GC is being used if it’s 7.9.

What’s the hardware here? Sustained CPU usage seems maybe a little high without justification.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 1, 2022, 1:30pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/5 "2022-02-01T13:30:51Z")

</div>

(Tagged 7.9) Also ensure G1GC has a maximum pause milliseconds target. I recommend 100ms, as the default is 1 second. That doesn’t play well with the 1 second clock drift detector.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 1, 2022, 1:32pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/6 "2022-02-01T13:32:19Z")

</div>

Pretty sure the default has always been 200ms, not 1s.

@Richita_Pandey if you can upload your `ignition.conf` file that would help.

---

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 1, 2022, 1:54pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/7 "2022-02-01T13:54:11Z")

</div>

I don’t have the access to that ingition.conf file.  
If you can guide me to check few config setting, I can check with team to get that details.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 1, 2022, 1:56pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/8 "2022-02-01T13:56:06Z")

</div>

Interested in the contents of the section that looks something like this:

```auto
# Java Additional Parameters
wrapper.java.additional.1=-XX:+UseConcMarkSweepGC
wrapper.java.additional.2=-XX:+CMSClassUnloadingEnabled
wrapper.java.additional.3=-Ddata.dir=data
wrapper.java.additional.4=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
#wrapper.java.additional.5=-Xdebug
#wrapper.java.additional.6=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

```

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 1, 2022, 2:34pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/9 "2022-02-01T14:34:40Z")

</div>

> [@Kevin.Herron](#):
>
> Pretty sure the default has always been 200ms, not 1s.

I stand corrected. Now I'm going to wonder how I mislearned that. /:

---

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 2, 2022, 6:01am UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/10 "2022-02-02T06:01:41Z")

</div>

```auto
# Java Additional Parameters
wrapper.java.additional.1=-XX:+UseG1GC
wrapper.java.additional.2=-XX:MaxGCPauseMillis=100
wrapper.java.additional.3=-XX:+CMSClassUnloadingEnabled
wrapper.java.additional.4=-Ddata.dir=data
wrapper.java.additional.5=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
#wrapper.java.additional.6=-Xdebug
#wrapper.java.additional.7=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=16384

```

---

<div class="post-metadata">

**Author:** ![Adriaan.leRoux](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Adriaan.leRoux](https://forum.inductiveautomation.com/u/Adriaan.leRoux)\
**Post date:** [February 2, 2022, 6:12am UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/11 "2022-02-02T06:12:25Z")

</div>

Are you running Ignition on a VM perhaps?

---

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 2, 2022, 6:19am UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/12 "2022-02-02T06:19:55Z")

</div>

No, its running on windows server OS

---

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 2, 2022, 1:10pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/13 "2022-02-02T13:10:54Z")

</div>

I believe this is what you are looking for. @Kevin.Herron

```auto
# Java Additional Parameters
wrapper.java.additional.1=-XX:+UseG1GC
wrapper.java.additional.2=-XX:MaxGCPauseMillis=100
wrapper.java.additional.3=-XX:+CMSClassUnloadingEnabled
wrapper.java.additional.4=-Ddata.dir=data
wrapper.java.additional.5=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
#wrapper.java.additional.6=-Xdebug
#wrapper.java.additional.7=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=16384

```

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 2, 2022, 1:25pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/14 "2022-02-02T13:25:23Z")

</div>

Yep, that looks fine. Not sure what else you can do. Call support and have them help you figure out why the CPU usage is constantly \>30% maybe? That may very well be fine, but it’s worth looking at to be sure.

---

<div class="post-metadata">

**Author:** ![Richita\_Pandey](https://avatars.discourse-cdn.com/v4/letter/r/6bbea6/32.png) [@Richita\_Pandey](https://forum.inductiveautomation.com/u/Richita_Pandey)\
**Post date:** [February 2, 2022, 1:27pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/15 "2022-02-02T13:27:01Z")

</div>

Thank you @Kevin.Herron .  
Just curious to know if this issue can arise if we have network issue for some time?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 2, 2022, 1:27pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/16 "2022-02-02T13:27:36Z")

</div>

That shouldn’t matter, and your CPU usage and memory pattern seem very consistent.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 2, 2022, 1:28pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/17 "2022-02-02T13:28:45Z")

</div>

Aside from the longer pauses your system looks fine. Longer pauses like that are usually only seen on crappy hardware or when running in a virtual machine.

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [February 2, 2022, 2:28pm UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/18 "2022-02-02T14:28:50Z")

</div>

How much RAM does the server have? Is Ignition the only software running on this machine (e.g. database, designer, client, etc…)

---

<div class="post-metadata">

**Author:** ![josborn](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@josborn](https://forum.inductiveautomation.com/u/josborn)\
**Post date:** [February 8, 2022, 12:07am UTC](https://forum.inductiveautomation.com/t/clockdrift-warning/55594/19 "2022-02-08T00:07:23Z")

</div>

This may or may not be relevant, I recently discovered that vulnerability scanning can spike CPU usage dramatically and cause clock drifts. In my case it was a daily Nessus scan, adding a 2nd CPU resolved it for me.
