[syslog-ng] [Bug 112] New: Problems when using encoding in 3.1.3 ose edition
bugzilla at bugzilla.balabit.com
bugzilla at bugzilla.balabit.com
Fri Feb 11 14:32:46 CET 2011
https://bugzilla.balabit.com/show_bug.cgi?id=112
Summary: Problems when using encoding in 3.1.3 ose edition
Product: syslog-ng
Version: 3.1.x
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: unspecified
Component: syslog-ng
AssignedTo: bazsi at balabit.hu
ReportedBy: aseques at gmail.com
Type of the Report: ---
Estimated Hours: 0.0
Good morning,
I needed to reencode some windows logs emited by snare so they are stored ad UTF on the fly.
After reading the documentation, I found what seems to be the solution.
Instead of creating a single source of data. I create an extra one, called src_win.
source src {
udp(ip("192.168.1.200") port(514));
};
source src_win {
udp(ip("192.168.1.200")
port(514)
encoding("WINDOWS-1252"));
};
Whenever I want to use the filter encoding for the logs, I will use this source instead of the generic one.
log {
source(src_win);
filter(f_host_name);
filter(f_messages);
destination(name_messages);
};
The problem is that as soon as I enable the source src_win for any log, it just stop logging the rest of sources.
Is that a known bug or something I should fix.
--
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the syslog-ng
mailing list