Hi David,

There were some changes on related code last week and I noticed similar
problems. If you can send the full test including input files, I can then
take a look whether my changes helped or not.

Thanks,
Botond

On Mon, 16 Feb 2015 12:58:58 -0800
David Greekas <dgree...@gmail.com> wrote:

> I have nxlog setup to ship json messages to logstash, however I was getting
> a lot of corrupt messages for my SQL Error logs.
> 
> I setup a little test that uses an im_file input and an om_file output with
> Exec convert_fields('UCS-2LE','UTF-8'); if $raw_event == '' drop(); fairly
> consistently an encoding error happens every 200- 300 lines resulting in
> scrambled characters EVEN if every line in the source file is the same (cut
> and paste repeated).
> 
> I have also tested using the convert() function with the same results.
> 
> This seems to happen on both Windows 7 and 2008 server with
> nxlog-ce-2.8.1248
> 
> 
> 
> <Extension charconv>
>     Module xm_charconv
> </Extension>
> 
> <Input SQLErr>
>     Module im_file
>     File "C:\Temp\Logs\ERRORLOG*"
>     Exec convert_fields('UCS-2LE','UTF-8'); if $raw_event == '' drop();
> </Input>
> 
> 
> <Output NxOut>
>     Module    om_file
>     File "C:\\Temp\\Logs\\nx_output.txt"
> </Output>
> 
> <Route 1>
>     Path        SQLErr => NxOut
> </Route>
> 
> -- 
> David

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users

Reply via email to