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
Get Updates on the Splunk Community!

Updated Data Type Articles, Anniversary Celebrations, and More on Splunk Lantern

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

A Prelude to .conf25: Your Guide to Splunk University

Heading to Boston this September for .conf25? Get a jumpstart by arriving a few days early for Splunk ...

4 Ways the Splunk Community Helps You Prepare for .conf25

.conf25 is right around the corner, and whether you’re a first-time attendee or a seasoned Splunker, the ...