Getting Data In
×

Are you a member of the Splunk Community?

Sign in or Register with your Splunk account to get your questions answered, access valuable resources and connect with experts!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question

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

kcooper
Communicator
‎10-30-2018 09:18 AM

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)
Reply

andrew_burnett
Path Finder
‎02-10-2023 08:09 AM

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
Reply

andrew_burnett
Path Finder
‎05-11-2023 10:26 AM

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

0 Karma
Reply
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...