Didn't hear about that before. According to the error maybe is because the UTF-8/16 like you said, we can find in logcollector read_multiline log <https://github.com/wazuh/ossec-wazuh/blob/5441889d963ce6d8ee3fae0e9f273e701b6c89eb/src/logcollector/read_multiline.c#L52> or at syslog collector <https://github.com/wazuh/ossec-wazuh/blob/5441889d963ce6d8ee3fae0e9f273e701b6c89eb/src/logcollector/read_syslog.c#L44>, I would say OSSEC is not detecting the \n character...
On Sunday, April 17, 2016 at 2:05:53 PM UTC+2, DefensiveDepth wrote: > > It appears that OSSEC does not support log files encoded with UTF-8/16? I > haven't seen any specific documentation on it, so I wanted to confirm. From > the screenshot below, you can see that the once a null char is encountered > (after the T), it fails to read any further. > > http://screencast.com/t/tqozmdlzje > > -Josh > > > -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to ossec-list+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
