Getting Data In

Error in splunkd - fileclassifiermanager - Error (bad allocation) encountered ...

kcooper
Communicator

logs are not being ingested into Splunk. The Inputs and outputs are configured correctly. receiving the following error in the splunkd.log file
ERROR FileClassifierManager - Error (bad allocation) encountered while getting file type for 'c:\Program Files\SplunkUniversalForwarder\var\log\splunk\splunkd.log.1'.

Tags (1)

andrew_burnett
Path Finder

I'm also getting this issue, except my UF is delayed by 400 hours sending logs to Splunk. And only for Windows Events.

0 Karma

andrew_burnett
Path Finder

Anyone figure out why? I'm having this exact same issue.

0 Karma
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!

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

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 ...