- syslog-ng - lists.balabit.hu

syslog network loging problem
by jscheibe＠css.tayloru.edu 10 May '01

10 May '01

1 0

syslog network loging problem
by jscheibe＠css.tayloru.edu 10 May '01

10 May '01

1 0

RE: [syslog-ng]filter() call bug fix
by Hamilton, Andrew Mr RAYTHEON 5 SIG CMD 08 May '01

08 May '01

I guess it would depend on how important this change is to everyone and if it is the only fix/enhancement in the next prospective version. For me this change alone is not that significant so you could hold off if you wanted. Regards, Drew -----Original Message----- From: Balazs Scheidler [mailto:bazsi@balabit.hu] Sent: Tuesday, May 08, 2001 10:30 AM To: syslog-ng(a)lists.balabit.hu Subject: Re: [syslog-ng]filter() call bug fix On Fri, May 04, 2001 at 05:21:56PM -0500, Jon Marks wrote: > Hi, > > I've uncovered a small bug in the filter() call within filter definitions. > Attached is a patch to filters.c against the current stable release > (1.4.11) to fix the bug. Thanks for the fix. This slipped my attention before releasing 1.5.6 so it doesn't contain this fix. I applied to both of my 1.4.x and 1.5.x trees. I don't know whether to release a new versions though. What do you people think? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

2 1

Syslog-ng v1.4.11, libol 0.2.21, Slackware Linux 7.1, Not Logging
by Jon Todaro 08 May '01

08 May '01

I am trying to get syslog-ng running. I am using the stock syslog-ng.conf.RedHat config file, and syslog-ng starts, but will not autocreate the files, and it also wont log at all. If I run syslog-ng in -d mode. This is some of the output it shows me when I telnet in from another client. [root@bone:/root] syslog-ng -d io.c: listening on fd 3 io.c: listening on fd 4 syslog-ng version 1.4.11 starting io.c: Preparing fd 5 for reading io.c: Preparing fd 6 for reading Read EOF on fd 5. Marking fd 5 for closing. Closing fd 5. io.c: Preparing fd 5 for reading Read EOF on fd 5. Marking fd 5 for closing. Closing fd 5. Read EOF on fd 6. Marking fd 6 for closing. Closing fd 6. io.c: Preparing fd 5 for reading Any help would be greatly appreciated. Note.. libol was configured with no ./configure options specified. And syslog-ng was configured with only -sysconf -sbindir -bindir and -prefix specified. And I have moved the config file all together to make sure it was in the correct place, and when I did, it would not start. Help, I have used earlier versions of this daemon before, just fine. Jon Todaro

2 5

filter() call bug fix
by Jon Marks 08 May '01

08 May '01

Hi, I've uncovered a small bug in the filter() call within filter definitions. Attached is a patch to filters.c against the current stable release (1.4.11) to fix the bug. The following is a description of the problem. Take the following bit of configuration code for illustration: ############################ source local { unix-dgram("/dev/log"); udp(); internal(); }; filter f_test { host("myhost"); }; filter f_test2 { program("something"); }; filter f_test3 { filter("f_test"); }; # <-- ERROR occurs because of this destination d_test { file("/what/ever"); log { source(local); filter(f_test3); destination(d_test); }; ############################ When filters are defined in the configuration file, they're added to a list. If they contain a call to another filter (as in f_test3), the actual filter to which they refer is resolved the first time the former's evaluated against a log message. (So you can refer to a filter in the config file before you define it). The filter call resolution procedure traverses the list, comparing the name of each filter to the name its looking for. The problem is just a little mixup in the logic used to detect when the right filter is found. Here's the code responsible, from filters.c/do_filter_call(): if (!self->call_rule) { struct log_filter *p = rule->prev_filter; while (p && p->name->length != self->name->length && memcmp(p->name->data, self->name->data, self->name->lengt h)) { p = p->prev_filter; } ... } In the while() loop, the previous filter is meant to be chosen until the right one is found. But the condition logic says, "Try the next filter while 1) there IS a next filter AND 2) the filter's name length is different AND 3) the filter's name's contents don't match what we're looking for." But what happens when the length of the present filter doesn't match, but the contents *DO*? This can happen since the code only compares the as many bytes as the target name has. This condition would stop the loop, and choose the wrong filter (as p would be left pointing to the unmatching filter). This (and the other lookup phase, not shown) is fixed by the attached patch, by changing the logic as follows: if (!self->call_rule) { struct log_filter *p = rule->prev_filter; while (p && (p->name->length != self->name->length || memcmp(p->name->data, self->name->data, self->name->length)) ) { p = p->prev_filter; } ... } This should guarantee that the loop ends on p only when p is either NULL, or when it points to a filter with a name of matching length AND matching contents (thank DeMorgan for this explanation of that code). Otherwise, in the configuration snippet above, the filter() call in f_test3 resolves to "f_test2" in the lookup procedure, when "f_test" is the desired referent. That's because, as it traverses the list backwards from itself, it encounters f_test2 first (which is defined AFTER f_test). And f_test2 has unmatching length (good for advancing p) but matching contents up the the length of the string "f_test" which is what's being sought. Thanks. -- Jonathan Marks Systems Administrator, Production Systems Group Computing and Communication Services Office University of Illinois at Urbana-Champaign

2 1

RE: [syslog-ng]Filter oddity
by Hamilton, Andrew Mr RAYTHEON 5 SIG CMD 08 May '01

08 May '01

Chris, You are missing the "and" between authpriv and not. Regards, Drew -----Original Message----- From: Chris Wall [mailto:cwall@interaccess.com] Sent: Monday, May 07, 2001 10:50 PM To: syslog-ng(a)lists.balabit.hu Subject: [syslog-ng]Filter oddity Apologies if this has been covered... I'm trying to fine tune my filtering in syslog-ng combined with some features of 2.4.x iptables/netfilter and portsentry What want to do is log information coming from the log rule in iptables to a specific file without it falling over into my other logs. The default syslog-ng.conf came with this filter: filter f_filter2 { level(info) or facility(mail) or facility(authpriv); }; And I've added this filter: filter f_iptables { level(info) and match(portsentry); }; What I would like to do is use a "not" in the first filter - i.e. filter f_filter2 { level(info) or facility(mail) or facility(authpriv) not match(portsentry); }; however, I get a parse error. I'm using 1.4.11... if I understand the docs right, this ought to be okay, but I'm sure I'm missing something. Any help would be appreciated. _______________________________________________ syslog-ng maillist - syslog-ng(a)lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng

1 0

Filter oddity
by Chris Wall 07 May '01

07 May '01

Apologies if this has been covered... I'm trying to fine tune my filtering in syslog-ng combined with some features of 2.4.x iptables/netfilter and portsentry What want to do is log information coming from the log rule in iptables to a specific file without it falling over into my other logs. The default syslog-ng.conf came with this filter: filter f_filter2 { level(info) or facility(mail) or facility(authpriv); }; And I've added this filter: filter f_iptables { level(info) and match(portsentry); }; What I would like to do is use a "not" in the first filter - i.e. filter f_filter2 { level(info) or facility(mail) or facility(authpriv) not match(portsentry); }; however, I get a parse error. I'm using 1.4.11... if I understand the docs right, this ought to be okay, but I'm sure I'm missing something. Any help would be appreciated.

1 0

Solaris8-x86: Missing symbol when linking syslog-ng 1.4.11
by Sander 06 May '01

06 May '01

Hi, I'm trying to compile syslog-ng 1.4.11 on Solaris8-x86 with gcc-2.95.3 and get the following linker error: gcc -O2 -Wall -I/usr/local/include/libol -D_GNU_SOURCE -o syslog-ng main.o sources.o center.o filters.o destinations.o log.o cfgfile.o cfg-grammar.o cfg-lex.o affile.o afsocket.o afunix.o afinet.o afinter.o afuser.o afstreams.o afprogram.o utils.o syslog-names.o getopt.o getopt1.o -lpthread -ldoor /usr/local/lib/libol.a -lsocket -lnsl -lxnet Undefined first referenced symbol in file yywrap cfg-lex.o ld: fatal: Symbol referencing errors. No output written to syslog-ng collect2: ld returned 1 exit status *** Error code 1 Has anyone had this problem before? What library should this symbol be in? I've compiled it succesfully before on Solaris8-sparc with no problems whatsoever. Thanks in advance, Sander de Boer

4 5

Syslog.conf translator
by Jon Marks 06 May '01

06 May '01

Hi, In order to make the transition to syslog-ng easier for people, I thought it might be useful to have an automated translation from the old syslog.conf to a working syslog-ng.conf. I came up with an awk script which works OK for me. I was targeting Solaris and AIX specifically, but off-hand, RedHat linux syslogd looks the same and I presume other UNIX variants' do, too. Try it, it could work ;) In particular, there are three things to look out for if you're interested in porting this to another UNIX platform: 1) Change the local log device if necessary, from /dev/log to whatever it's supposed to be. 2) Change the device type (i.e. the syslog-ng.conf directive) for the local log device. The script checks 'uname' for SunOS and AIX and sets an appropriate variable; just add to that detection mechanism. A variable would do nicely for the log device, too, but they've got the same name in AIX and Solaris so I didn't worry about it. (I'm not using the "door" device). 3) The script is an awk script, but its invoked by ksh. It's easy to rearrange it so that it's invoked directly as awk, but for what I plan to do with it, I didn't need that. In either case, ksh won't be available on many linux distros, I think, so just change the shell to bash or something. (In this case, I hope the shell you pick is lenient about newlines within a quoted command line argument!) Hope this is useful! -- Jonathan Marks Systems Administrator, Production Systems Group Computing and Communication Services Office University of Illinois at Urbana-Champaign

2 4

Stability of 1.5 tree
by Chris Sibbitt 04 May '01

04 May '01

Just a basic question. How stable is the 1.5 tree compared to the 1.4? I've been using 1.4 for quite awhile, and it seems to hold up well for my purposes, however I'd like the additional functionality that is in 1.5.6. Has anyone been using the latest 1.5 builds in production? What, if any, problems have been experienced? Chris Sibbitt JetNet Internetworking Services Inc. Providing Secure Internet Communications Phone 613-271-6220x228 FAX 613-271-6229 Email csibbitt(a)jetnet.ca Web www.jetnet.ca <http://www.jetnet.ca/>

1 0