Thank you for bringing this to our attention.  Can you please create an 
issue at https://github.com/logstash-plugins/logstash-codec-json ?

Thanks!

On Wednesday, December 10, 2014 7:13:16 AM UTC-8, Vagif Abilov wrote:
>
> Hello,
>
> We have been successfully using Logstash to parse our JSON logs data and 
> import them to Elasticsearch database, but recently had failures on some 
> machines. Here's the error Logstash displays:
>
> ←[32mRegistering file input 
> {:path=>["D:/Octopus/Applications/prod-ndoa/Bridge.Web/logs/BridgeSoap.*.txt"],
>  
> :level=>:info}←[0m
> ←[32mPipeline started {:level=>:info}←[0m
> ←[31mA plugin had an unrecoverable error. Will restart this plugin.
>   Plugin: <LogStash::Inputs::File add_field=>{"_environment"=>"prod-ndoa", 
> "_application"=>"bridge_rest"}, 
> path=>["D:/Octopus/Applications/prod-ndoa/Bridge.Rest.Host/logs/BridgeRest.*.txt"],
>  
> sincedb_path=>"D:/Octopus/Applications/prod-ndoa/Bridge.Rest.Host/logs/sincedb",tags=>["bridge_rest"],
>  
> start_position=>"end">
>   Error: incompatible encodings: Windows-1252 and UTF-8 
> {:level=>:error}←[0m
>
> The input file is a set of JSON documents in UTF-8 encoding (with BOM). If 
> edit the file and remove BOM symbols, the import goes fine.
>
> And here's the input file configuration:
>
> input {
>   file {
>     path => 
> "D:/Octopus/Applications/prod-ndoa/Bridge.Web/logs/BridgeSoap.*.txt"
>     sincedb_path => 
> "D:/Octopus/Applications/prod-ndoa/Bridge.Web/logs/sincedb"
>     codec => json
>     start_position => "end"
>    }
> }
>
> If I remove codec "json", it doesn't fail but the output of course is 
> wrong because it treats JSON documents as plain text.
>
> The strangest things is that on other machines it works properly (same 
> 1.4.2 version of Logstash).
>
> Does anyone have an idea why this might happen?
>
> Thanks in advance
>
> Vagif Abilov
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/1fb33e9b-6fb9-49b7-ba4a-af97cf0610cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to