Getting Data In

Universal forwarder consuming 100% CPU. "WARN TimeoutHeap - Either time adjusted forwards by, or event loop was descheduled for 490844ms"

regriffith
Path Finder

Splunk consumes 100% of the CPU. Installed version is 6.4.

Splunk log:

07-13-2016 19:18:11.904 -0500 WARN  TimeoutHeap - Either time adjusted forwards by, or event loop was descheduled for 490844ms.
07-13-2016 19:18:11.904 -0500 WARN  TimeoutHeap - Either time adjusted forwards by, or event loop was descheduled for 490813ms.
0 Karma
1 Solution

regriffith
Path Finder

The system time was adjusted backwards by NTP. Changing to a different NTP server fixed the CPU issue. It appears that the UF can't handle this type of change.

View solution in original post

regriffith
Path Finder

The system time was adjusted backwards by NTP. Changing to a different NTP server fixed the CPU issue. It appears that the UF can't handle this type of change.

Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...