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?

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

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...