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!

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...