topic Re: Why UF think my file is binary? in Getting Data In

Why UF think my file is binary?

yutaka1005 — Mon, 15 Jan 2018 06:51:08 GMT

In my environment, UF monitors the file and forwards it to Splunk.

It was able to capture the file without problems before,
Due to the version upgrade of software that outputs log that was being monitored,
and the character code is changed from Shift_jis to utf-16LE (with BOM), it is no longer imported.

When checking the internal log of UF, message saying "it was a binary file, so ignored it".

Is this a bug?
Is there any workaround other than updating?

If anyone knows, it would be greatly appreciated if you could tell me.

UF ver: 6.2.0

Re: Why UF think my file is binary?

inventsekar — Mon, 15 Jan 2018 07:16:46 GMT

Good discussions at https://answers.splunk.com/answers/373137/why-does-splunk-think-my-file-is-binary.html

Re: Why UF think my file is binary?

mayurr98 — Mon, 15 Jan 2018 07:50:12 GMT

hey

specify this attribute in props.conf

[host::my-foreign-docs]
CHARSET=AUTO

http://docs.splunk.com/Documentation/Splunk/6.3.3/data/Configurecharactersetencoding#Automatically_specify_a_character_set

Also put this

NO_BINARY_CHECK = [true|false]
* When set to true, Splunk processes binary files.
* Can only be used on the basis of [<sourcetype>], or [source::<source>],
  not [host::<host>].
* Defaults to false (binary files are ignored).
* This setting applies at input time, when data is first read by Splunk.
  The setting is used on a Splunk system that has configured inputs
  acquiring the data.

let me know if this helps!

Re: Why UF think my file is binary?

yutaka1005 — Tue, 16 Jan 2018 05:18:53 GMT

Thank you for answer mayurr98.

As a result of setting like below,
similar events did not recur.

[<sourcetype name>]
CHARSET=utf-16le
NO_BINARY_CHECK = true

It was very helpful!