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.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...