Time drift problem

Question

Question by Jiri K. · Oct 16, 2014 at 08:15 PM ·

Time drift problem

Hi,

in Server log our customer found this line:

2014-10-16 10:52:13 [2de833f4] info [native] Found high autosensor overhead, might hint to time drift problem, tsCounter: 729

Could this refer to an incorrect Timer being used? Or is that possibly a network issue? Has anyone seen this before?

0

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 1 · 2015-02-19T06:07:55Z

Answer by Jiri K. · Feb 19, 2015 at 06:07 AM

This is what I got from Support, it helped me to resolve the problem:

The autosensor overhead measurement is to verify how long it takes getting a thread dump of all threads with sensors on it. So if it measures high overhead, it is reducing the interval to not cause overhead issues and additionally slow down a maybe already busy server.
This measurement can be unreliable in case the application server is virtualized and the VM is moved to different physical CPU cores by the hypervisor. Then the timers are most likely jumping ahead or back in time and if so, we might also detect "high overhead" even if there is no problem. 'Low-Res System Clock' should always work, but you can also try others. The change gets active on the next agent restart.

If that does not help, I would suggest opening a Support case.

0 Show 1 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Len C. · Feb 19, 2015 at 09:20 AM 0

Share

Thanks so much for your response. That explains it.

Answer 2 · 2015-02-19T04:12:29Z

Answer by Len C. · Feb 19, 2015 at 04:12 AM

Hi,

Did you guys find anything else on this "Time Drift" problem? I got an Incident Alert for Timed Out Purepaths due to this same same issuefound in the Logs: "Found high autosensor overhead, might hint to time drift problem".

I checked the Agent's Time and it appears correct.

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 3 · 2014-12-02T18:37:36Z

Answer by Jiri K. · Dec 02, 2014 at 06:37 PM

Hi,

yes, it was resolved with Support. It is due to virtual environment, you need to change the timer/clock (in Advanced options on the agent level).

Best,

Jiri

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 4 · 2014-12-02T09:32:56Z

Answer by Richard H. · Dec 02, 2014 at 09:32 AM

Jiri,

If you hear/heard back please update us here ... TY.

Thanks,

Rich

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 5 · 2014-10-21T19:24:12Z

Answer by Andreas G. · Oct 21, 2014 at 07:24 PM

please do so. I tried to get an answer but wasnt lucky so far

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 6 · 2014-10-21T05:43:39Z

Answer by Jiri K. · Oct 21, 2014 at 05:43 AM

Should I open a case with Support for this?

Best,

Jiri

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Time drift problem

6 Replies

How to get started:

NAM 2019 SP3 is available

LIVE WEBINAR

Follow this Question

Forum Tags