- syslog-ng - lists.balabit.hu

[PULL REQ]: scratch-buffers
by Gergely Nagy 09 Nov '11

09 Nov '11

I've added the finishing touches to the scratch buffer patch, and I believe it's ready for a merge. Scratch buffers are a way to store reusable GStrings on a per-thread basis. They're allocated on demand, and once released, they're not free'd, but returned to the pool, so the next time the code requests a scratch buffer, it will reuse an existing one, instead of creating a new one. This reduces memory fragmentation, memory use, among other things. It's also very trivial. I have prepared a branch for both syslog-ng 3.3 and 3.4 too. The 3.3 branch also updates the value-pairs implementation to use scratch buffers (and thus, become thread-safe). The 3.4 branch does this too, and it also updates the json parser similarly. The branches are available as feature/3.3/scratch-buffers[0] and feature/3.4/scratch-buffers[1] in my github repo[2]. [0]: https://github.com/algernon/syslog-ng/commits/feature/3.3/scratch-buffers [1]: https://github.com/algernon/syslog-ng/commits/feature/3.4/scratch-buffers [2]: git://github.com/algernon/syslog-ng.git I'm not posting the patches here, as they'd be pretty much the same, and I've already posted a previous version (and the difference is about 3 lines). Though, if it's easier to review if I post it again, let me know, it's a git send-email away. -- |8]

2 1

Re: [syslog-ng] Quick filter question
by Lay, James 08 Nov '11

08 Nov '11

Excellent...thanks so much Patrick. This is working nicely. At some point in time I may want to add in the firewalls "Deny" statement, but for now this will work. Thanks again. James From: Patrick H. [mailto:syslogng@feystorm.net] Sent: Tuesday, November 08, 2011 11:57 AM To: Lay, James Cc: Syslog-ng users' and developers' mailing list Subject: [Spam] Re: [syslog-ng] Quick filter question Importance: Low That might work, but what the order of operations is on boolean operations (and/or) is, is unclear. In situations like that its always best to explicitly force the order yourself. filter f_firewall { not ( program ("firewall" flags(ignore-case)) and ( message("192\.168\.") or message("169\.254\.") ) ); }; Sent: Tue Nov 08 2011 11:46:35 GMT-0700 (MST) From: Lay, James <james.lay(a)wincofoods.com> <mailto:james.lay@wincofoods.com> To: Patrick H. <syslogng(a)feystorm.net> <mailto:syslogng@feystorm.net> , Syslog-ng users' and developers' mailing list <syslog-ng(a)lists.balabit.hu> <mailto:syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Quick filter question Ah...so I need or then yes? filter f_firewall { not ( program ("firewall" flags(ignore-case)) and message("192\.168\.") or message("169\.254\.") ); }; How's that look? James P.S. And thank you :) James From: Patrick H. [mailto:syslogng@feystorm.net] Sent: Tuesday, November 08, 2011 11:40 AM To: Syslog-ng users' and developers' mailing list Cc: Lay, James Subject: Re: [syslog-ng] Quick filter question I'm not sure if semicolons are valid in filter rules, but technically valid or not, they shouldnt be there so try removing them. The filter should look like filter f_firewall { not ( program ("firewall" flags(ignore-case)) and message("192\.168\.") and message("169\.254\.") ); }; Note though, that filter will only trigger if both 192.168. and 169.254. are in the same log entry. Unless that IP address you masked out with "x"s is 169.254 it wont trigger. Sent: Tue Nov 08 2011 11:21:11 GMT-0700 (MST) From: Lay, James <james.lay(a)wincofoods.com> <mailto:james.lay@wincofoods.com> To: Syslog-ng users' and developers' mailing list <syslog-ng(a)lists.balabit.hu> <mailto:syslog-ng@lists.balabit.hu> Subject: Re: [syslog-ng] Quick filter question Hey again all. So...I'm still having issue with this..not sure why. Here's the raw log: Nov 8 11:13:38 x.x.x.x firewall: Deny tcp 20 125 x.x.x.x 192.168.0.15 9517 17777 offset 7 S 3371425811 win 64 And from my syslog-ng.conf filter f_firewall { not ( program ("firewall" flags(ignore-case)); and message("192\.168\."); and message("169\.254\."); ) }; log { source(s_local); filter(f_dumb); filter(f_firewall); destination(d_file); destination(other); }; Any hints as to why these aren't matching? Should I not be \ing the periods? Thanks all. James From: syslog-ng-bounces(a)lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Frank Collette Sent: Tuesday, November 08, 2011 8:36 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Quick filter question filter f_firewall { not ( program("firewall" flags(ignore-case)) and message("169\.254\.[0-9]+\.[0-9]+" value("MESSAGE")); ) }; Thanks, Frank E. Collette IV Technical Services Systems Administrator II Trustmark National Bank Office: 601-208-7517 Fax: 601-208-6105 fcollette(a)trustmark.com From: "Lay, James" <james.lay(a)wincofoods.com> <mailto:james.lay@wincofoods.com> To: <syslog-ng(a)lists.balabit.hu> <mailto:syslog-ng@lists.balabit.hu> Date: 11/08/2011 09:14 AM Subject: [syslog-ng] Quick filter question Sent by: syslog-ng-bounces(a)lists.balabit.hu ________________________________________ Hey all! Real quick...trying to filter OUT firewall hits that have say...169.254. Will this do the trick? filter f_firewall { not program (firewall flags(ignore-case)); and not message("169\.254\.[0-9]+\.[0-9]+"); }; Thanks all. James___________________________________________________________________ ___________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq ________________________________________________________________________ ______ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq

1 0

Documentation errors
by VÁMOS Balázs 08 Nov '11

08 Nov '11

Hi, I have found some mistakes on the documentation page. 1. This link does not work: http://www.balabit.com/support/documentation/syslog-ng-windows-agent-v3.1-g… 2. This link is for version 3.1 but the header says it is 3.2 http://www.balabit.com/sites/default/files/documents/syslog-ng-windows-agen… -- VÁMOS Balázs LOGalyze.com

2 2

Cannot start syslog-ng on Debian
by Hery Fanomezantsoa 07 Nov '11

07 Nov '11

I installed syslog-ng-3.2.4 from source on Debian Lenny and when I start syslog-ng with /usr/local/syslog-ng/sbin/ syslog-ng it shows me this error: Error creating persistent state file; filename='/usr/local/syslog-ng/var/syslog-ng.persist-', error='No such file or directory (2)' Can someone help me please?

2 4

3.2 and 3.3 git experiences
by Peter Czanik 05 Nov '11

05 Nov '11

Hello, I compiled and quickly tested the latest git versions of syslog-ng 3.2 and 3.3. Here are some results: OS X: 3.2 compiles and runs fine once I remove "#define HAVE_ENVIRON 1" from the generated config.h No luck at all compiling 3.3 FreeBSD: tested only 3.3 by slightly editing the sysutils/syslog-ng port. As syslog-ng 3.3 dependencies were already on the machine, it was easy to generate a new tgz release: export LEX=/usr/local/bin/flex ./autogen.sh ./configure gmake dist I copied the resulting tgz to /usr/ports/distfiles, under a new name: syslog-ng_3.3.2.tar.gz and deleted /usr/ports/sysutils/syslog-ng/distinfo, as it contains checksum info for 3.3.1. The Makefile had to be modified only to reflect the version change to 3.3.2. "pkg-plist" also had to be fixed to follow up the change in line "lib/libsyslog-ng-3.3.1.so". The resulting syslog-ng binary worked fine for me with any configuration options set during "make config". The above tests were done on a FreeBSD 8.1 machine. I'll do a quick test on FreeBSD 9 (the current cvs version) later this afternoon, as the Makefile seems to have v9 related fixes: .if ${OSVERSION} >= 900007 @${REINPLACE_CMD} \ -e 's|utmp|utmpx|' -e 's|getutent|getutxent|' \ -e 's|ut_name|ut_user|' \ ${WRKSRC}/configure ${WRKSRC}/modules/afuser/afuser.c \ ${WRKSRC}/lib/utils.c ${WRKSRC}/lib/utils.h .endif Updating my ports tree right now... Linux: I tested 3.2 only with openSUSE 11.4, and it worked for me without any problems. The package is available in the openSUSE build service at https://build.opensuse.org/project/show?project=home%3Aczanik%3Asyslog-ng32 with sources and download links. I tested 3.3 on openSUSE 11.4 and factory (well, actually 12.1 RC2), and also compiled for 11.3 (but did not test the resulting packages). The packages are available in the openSUSE build service at https://build.opensuse.org/project/show?project=home%3Aczanik%3Asyslog-ng33 with sources and download links. Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

2 3

3.2.5 preparations
by Balazs Scheidler 04 Nov '11

04 Nov '11

Hi, I wanted to publish a last maintenance release from the 3.2 branch before moving on to work on 3.4. I've backported the relevant patches, tests have ran (both on my development computer and a separate build environment), but I'd like to ask anyone running 3.2.x to test it in more production-like environments. The current state is available in git, but I've also uploaded a tarball to: http://people.balabit.hu/bazsi/syslog-ng-3.2.4+20111022+0801.tar.gz These patches were applied since 3.2.4: 4f27ef33af4d84a31f237469e493ddd3834404fe nvtable: implement proper limitation on NVTable size b6136da08fb3421239a1c2dc40b582a5a7a2e78b gprocess: Implement stricter CAP_SYSLOG checking. 7e1a3903c0635a9a5070a6998ebc3f4e1282f33e syslogformat: handle AIX style message forwards properly 304539186bab96254d683b3026a00d5404903252 cfg_persist_config_add_entry(): call destroy notify if persist config is empty 409304c6fdcabbd1c321d57e2bbbd3d412a43cf2 cfg-lexer.c: don't include hidden files when including a directory 7ca0e8d65048b65fe3c0015ffc7ac8d73a234833 timezone format: handle half hours in the negative range properly e9dfe15a804610def3186f104853cc5626adbf53 Copyright fixups 320e4d065df521a61ff000e848f1e6a7a787c616 program-override(): disable the effect of store-legacy-msghdr flag ef4a0ff535f2860036d8901b290b204aca7568fa persist-state: fixed a memory small leak fc91010594fe80ba111020f1bb4e23ef41acfdc6 cfg-lexer: closed a memory leak in token blocks handling 9f2153fdb3d9b9cdc120af85db5e87f93cbcec0b PCRE matcher: free the pointer returned by pcre_study() to close a memory leak 2884c8fa188ec1ab8e09799b9c6d497cf8aa423f blocks: propagate include problems as parser errors c2669ffeeae0825c9de637c04794dcfa3965b3de logmatcher: fixed a possible crash in case a regexp match is applied to a read-only macro a2fdfc9ee73c1def081eed0c554c592fd6bea572 [SCL] set empty default parameter to block ce2d45f63b9b2ee7b3b486e517b92662158c321d logproto: fixed an inbalanced get_state()/put_state() pair 3e9be2596c298e31a3b3478c430d517f5bfe42c9 [lex-rules.am]: rules use $(EGREP) instead of grep -E.(EGREP is -E compliant grep implementati b00fde64d08642eb06e1cc342f1c762a7dde6767 afsocket: Fixed a wrong cast in afsocket_dd_set_keep_alive(). 5490cf73b95a597c8695407c875cf55d23679bb9 [plugin] on AIX syslog-ng try to load .a archive modules e98032d07cdcb3a51fe1a7ddda3d3d24b0985a92 zone_info_parser: move variable declaration to the beginning of the function 88596d2b069bcdc46e207487be398ef31aa0aad9 tlscontext: fixed a possible segfault in certificate validation 160e7ebe5e6bd2ef1b0c0e79563d617c3f6f0065 [SDATA] Allow store sdata section without name or value 8bcab2e198863847036809c765b5415371d34760 afprog: automatically close pipes to child programs when executing external programs cd47492eb7733c443bccac4891efc398ab393a62 [syslog-ng-ctl] Added GLIB check version 81e350e410344e3eb1b79464359aa838507bf56a func_test: improve SQL autodetection e138c672b11eee0b30f5036872f0866dbaa6e255 system(): Bail out on unknown systems, and use a clean environment to generate config. 32650278fb35fb6f82522df54014c8d57f1705aa [persist]: only check the buffer size if no encoding is specified 2dc66883f722709b50e30875f8bb64daf24536ca LogProtoBufferedServer: fixed error handling in case the persist-state cannot be restored a4ff6764e06d7ae9eeaab8b9a89336680362ebb1 gprocess: fixed compilation error on old glibc versions f69ded4f05ddb1afcdf0ffbf3e16f1fbe3d6b53a func_test: make it possible to check whether it makes sense to run a testcase ae0ff59d9a761c2fda8a19b0c05e0e05c59bae57 Use CAP_SYSLOG instead of CAP_SYS_ADMIN, if available. f54686441496ded775877e33ad2c3e0310861b7b logreader flags: fixed segfault on unknown flags e2961e1c738c8b02ca6057ac34415536830dd0e9 add support for installing systemd unit files 2db971fc37471e39f6a8b34595ca23833166831e fixed chain-hostnames() processing 2f214c4f87d944aa28d53e331a67b1fd88d9840f systemd: make sure the acquired fd is in non-blocking mode I intend to wait a couple of days to do the actual release, but I'll proceed in a week or so without feedback too. -- Bazsi

4 12

RFC/RFH: JSON status report and plans
by Gergely Nagy 03 Nov '11

03 Nov '11

Hi! To support CEE[1] stuff better, a few things are needed for syslog-ng's JSON support, and I'd like to take this opportunity to both give a headsup on what's still needed, and present a few easy bits that we need, and are very low hanging fruits for aspiring syslog-ng hackers to grab. Whitespace ---------- First of all, for compactness, the JSON we generate should be free of any unneccessary whitespace. At the moment, we generate JSON like this: { "foo": "bar", "baz": "quux" } The whitespace between key and value should be dropped, so should the whitespace at the curly brackets, so that we'd generate the following instead: {"foo":"bar","baz":"quux"} This is fairly trivial to fix, at least when using json-c (and that's the only case we need fixed, for other reasons): * Each json_object struct has a ->_to_json_string, which is used to format the string. * The default implementation puts in whitespace * The fix is: + #include <json_object_private.h> + copy the json_object_object_to_json_string() function from json.c, changing it to not emit extra whitespace + Override the ->to_json_string of the root JSON object in syslog-ng's modules/tfjson/tfjson.c's tf_json_append(), so that it points to the new function that doesn't do whitespace. This is a trivial patch, and I pretty much already wrote it for you. If someone can turn that into a patch, that would be grand! Nested JSON ----------- Another thing that would be very good to have, and not only for JSON, but for the MongoDB driver aswell, is to be able to generate nested objects. So that a key-value pair like "foo.bar"="quux" would end up as {"foo":{"bar":"quux"}} when formatted as JSON. That is, we'd need to split up keys by "." chars, and treat the first piece as the parent object. The harder part is that keys are not ordered within syslog-ng, and there might be conflicts (ie, syslog-ng allows "foo" and "foo.bar" to coexist, but we can't format that as JSON if we split by dots, because foo would then be a string and an object at the same time), which need to be handled one way or the other. My idea was that we could sort the keys in descending order, so that if we have "foo.aaa", "foo.bbb", and "foo", we'd end up with "foo.bbb", "foo.aaa", and "foo" list, split them up at the dots, pack stuff into foo, notice later that we already have a foo object, so a foo string is no-no, and threw a hissy fit (an error, that is). I'm not going to explain the whole algorithm here, but it's not too hard to figure it out. The question in this case is two-fold: anyone up for implementing this (I can provide assistance)? And if not, should this nesting be enabled by default? Should it be an option at all, or the only supported way? (I tend to side with going with nesting and not providing an option to disable it, but I can be persuaded otherwise) JSON parser ----------- Another thing that's reasonably easy to put together, is a JSON parser. Something like the existing CSV and patterndb parsers, except this would parse JSON with the json-c library. I have a few rough ideas, and am happy to provide help if someone feels up to the task of tackling this and developing the feature. =) Other pending issues -------------------- There's also a case for types. It would be beneficial if numbers could be represented as, well, numbers in the generated JSON (and similary, stored as numbers when using the MongoDB destination). This, however, requires some deeper changes, and I'm not yet familiar with that part of the code yet, either. So I'm not going to go into details. Nevertheless, I felt I need to mention this here, so that it won't fall under the table. [1]: http://cee.mitre.org/ -- |8]

1 1

Memory leak on SIGHUP on 3.0.1 and up
by Simon Gauthier 01 Nov '11

01 Nov '11

Hi, I am using syslog-ng 3.01 and I experience memory leak on SIGHUP. This has been seen on a standard Fedora 10 system with syslog-ng 3.0.1 to 3.0.10. the same test leak also with 3.3.1. My syslog-ng.conf file has no rules in it. A simple bash script sending a SIGHUP to the syslog-ng process will leak memory at a fast face. #!/bin/bash while true; do date # $1 is syslog-ng pid sudo /usr/bin/kill -1 $1 done Any idea about, that? Thanks Simon Gauthier

2 2

NFS support
by Omer Faruk SEN 01 Nov '11

01 Nov '11

Hi, Is there a known issue with syslog-ng and NFS (Netapp Storage) share? Can syslog-ng write to NFS storage ? It should write without problem but i wanted to be sure. I have tried to write to NFS storage of syslog message with version 3.2 Regards.

2 1

[Bug 96] New: pdbtool misleading error message
by bugzilla＠bugzilla.balabit.com 01 Nov '11

01 Nov '11

https://bugzilla.balabit.com/show_bug.cgi?id=96 Summary: pdbtool misleading error message Product: syslog-ng Version: 3.2.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: czanik(a)balabit.hu Type of the Report: --- Estimated Hours: 0.0 When trying to test a non-existent file with pdbtool it gives misleading error messages and even calls an external application before failing. czanik@linux-6y8u:~/patterndb> pdbtool test --validate uw-imapd.ceee uw-imapd.ceee: Unable to detect patterndb version, please write the <patterndb> tag on a single line warning: failed to load external entity "/usr/share/syslog-ng/xsd/patterndb-0.xsd" Schemas parser error : Failed to locate the main schema resource at '/usr/share/syslog-ng/xsd/patterndb-0.xsd'. WXS schema /usr/share/syslog-ng/xsd/patterndb-0.xsd failed to compile warning: failed to load external entity "uw-imapd.ceee" uw-imapd.ceee: xmllint returned an error, the executed command was: xmllint --noout --nonet --schema /usr/share/syslog-ng/xsd/patterndb-0.xsd uw-imapd.ceeeError opening classifier configuration file; filename='uw-imapd.ceee', error='No such file or directory (2)' I think, that the proper behavior would be, that pdbtool detect that the file is nonexistent, prints a message about it (without any other misleading messages) and quits without calling external apps. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2