Getting Data In

Windows Forwarder reading file just fine while Linux isn't.

bosburn_splunk
Splunk Employee
Splunk Employee

I'm migrating from a Windows server to a Linux machine, and I'm finding that the Linux machine isn't reading a specific file. The file is UTF16-LE per the file command:

[root@bpoundiag01 xml]# file test.xml 
test.xml: Little-endian UTF-16 Unicode text, with very long lines

Why isn't this working?

Bosley

bosburn_splunk
Splunk Employee
Splunk Employee

This is due to a difference of the default CHARSET setting in the props.conf in Windows vs. Linux.

By default, the CHARSET in Windows is set to AUTO, and will determine which CHARSET to use.

In Linux, it defaults to UTF-8.

The fix is to add the following to the props.conf:

[mysourcetype]
CHARSET=UTF16-LE
Bosley
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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...