- syslog-ng - lists.balabit.hu

syslog-ng 3.4.0rc1 has been released
by devel＠balabit.hu 07 Jan '13

07 Jan '13

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.4.0rc1 SUMMARY : new stable release candidate DATE : Jan 7, 2013 ------------------------------------------------------------------------------ DESCRIPTION: A new release candidate of syslog-ng Open Source Edition (3.4.0rc1) has been released. For latest fixes in the 3.4.x feature branch you are recommended to upgrade to this version. CHANGES: 3.4.0rc1 Mon, 7 Jan 2013 16:00:00 +0100 Features ======== * Make it possible to link crypto stuff directly into libsyslog-ng, using the new --with-embedded-crypto option to configure. Bugfixes ======== * DNS resolving was made thread-safe, by either using getnameinfo() on platforms where it is available, or protecting the lookups with a mutex. * Restored support for systems that lack GLOB_NOMAGIC. * The syslog() destination now correctly enforces IPv4, so using udp6() followed by syslog() in the same source block will not result in syslog() trying to use IPv6. To use the syslog protocol over IPv6, use the new network() statement. * On AIX, load modules from "a" archives instead of "so" ones. * The config version checking mechanism was patched, which fixes a crash in certain cases when running under systemd. * The GeoIP module can now be built even on systems that do not have a pkg-config file for the geoip library, by setting the GEOIP_LIBS environment variable prior to running configure. Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. These people have helped in this release: Balint Kovacs <blint(a)blint.hu> Balazs Scheidler <bazsi(a)balabit.hu> Ben Lentz <blentz(a)cswg.com> Brian Kroth <bpkroth(a)gmail.com> Gergely Nagy <algernon(a)balabit.hu> Jan Schaumann <jschauma(a)netmeister.org> Peter Czanik <czanik(a)balabit.hu> Tamas Pal <folti(a)balabit.hu> Viktor Juhasz <jviktor(a)balabit.hu> DOWNLOAD: You can download the source or binary packages from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at http://www.balabit.com/support/documentation/

1 0

sql-driver and "ON duplicate KEY UPDATE"
by system＠ra-schaal.de 02 Jan '13

02 Jan '13

Hi all, is it possible to perform an "ON duplicate KEY UPDATE" with the sql-driver for a mysql-database? At the moment I use destination d_sql { program("/usr/bin/mysql -uUSER -pPASSWORD DATABASE" template("INSERT INTO TABLE VALUES (inet_aton('${.apache.client_ip}') ,${.apache.content_length},CURRENT_TIMESTAMP,1 ) ON duplicate KEY UPDATE bytes=bytes+${.apache.content_length}, hits=hits+1;\n") template-escape(yes)); }; without any problems. By using this destination, syslog-ng can´t use the sql-driver. I`m not sure if there is any difference between sql-driver and the destination above. regards Florian

2 1

Statistics summary
by Anton Koldaev 30 Dec '12

30 Dec '12

Is there a nice way to get total numbers of processed/stored/dropped messages in syslog-ng v3.3? >From docs: > The *center(received)* entry shows the total number of messages received from every configured sources. But in my stats center() shows zero almost for every host. I see zero in some other examples in docs too. -- Best regards, Koldaev Anton

3 7

SYSLOG-NG 3.4 exiting without any error print
by Deepak Gaur 28 Dec '12

28 Dec '12

Hello, I have cross-compiled syslog-ng for ARM target but it is exiting without showing any error code (on target). I am attaching strace output (syslog.txt). If anyone can help me out # syslog-ng -V syslog-ng 3.4.0alpha3 Installer-Version: 3.4.0alpha3 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.4#master#709ab1252920063e6d4d0d610ad5c1ee5ebdfb75 Compile-Date: Nov 27 2012 14:59:53 Available-Modules: syslogformat,afsocket-notls,afuser,basicfuncs,confgen,dbparser,tfuuid,afmongodb,afsocket-tls,afprog,afsocket,affile,csvparser Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: off Enable-Linux-Caps: off Enable-Pcre: on ATTACHMENT syslog.txt

2 2

Re: [syslog-ng] syslog-ng 3.4.0beta1 has been released
by Evan Rempel 27 Dec '12

27 Dec '12

I thought that 3.4 was going to include - junctions so that results of multiple parsers could be combined - the ability to run a parser against a user defined macro rather than always parsing the complete MESSAGE marcro. Did these features fail to make it into 3.4 or is the documentation just missing these items? Thanks, -- Evan Rempel Senior Systems Administrator, Data Centre Services University of Victoria 250.721.7691

4 6

syslog-ng 3.3.6 make error on solaris 8
by Rakesh Rajasekharan 24 Dec '12

24 Dec '12

syslog-ng 3.3.6 on a Solaris 8 sparc machine gives the below error on the make stage.. I have used.. dynamic linking option... Undefined first referenced symbol in file __sync_lock_release ../../.libs/libivykis.a(iv_signal.o) __sync_lock_test_and_set ../../.libs/libivykis.a(iv_signal.o) Anyone faced a similar issue..? or if someone can help out please... Thanks, Rakesh..

2 2

syslog-ng 3.3.6 - AIX Issue
by Manimaran kk 23 Dec '12

23 Dec '12

I have compiled the syslog-ng version 3.3.6 on a AIX 5.3 . The compilation went through fine but when I try to run syslog-ng, i am getting following error. # ./syslog-ng Error opening plugin module; module='affile', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libaffile.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='afprog', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libafprog.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Plugin module not found in 'module-path'; module-path='/opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng', module='afsocket' Error opening plugin module; module='afuser', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libafuser.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='basicfuncs', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libbasicfuncs.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='csvparser', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libcsvparser.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='dbparser', error='rtld: 0712-001 Symbol __iv_now_location was referenced\x0a from module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libdbparser.so(), but a runtime definition\x0a of the symbol was not found.' Error opening plugin module; module='syslogformat', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libsyslogformat.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='syslogformat', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libsyslogformat.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='basicfuncs', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libbasicfuncs.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Plugin module not found in 'module-path'; module-path='/opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng', module='afsocket' Error opening plugin module; module='affile', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libaffile.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='afprog', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libafprog.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='afuser', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libafuser.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='dbparser', error='rtld: 0712-001 Symbol __iv_now_location was referenced\x0a from module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libdbparser.so(), but a runtime definition\x0a of the symbol was not found.' Error opening plugin module; module='csvparser', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libcsvparser.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='confgen', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libconfgen.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error opening plugin module; module='confgen', error='\x090509-022 Cannot load module /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng/libconfgen.so.\x0a\x090509-026 System error: A file or directory in the path name does not exist.' Error parsing source, source plugin system not found in /opt/soe/local/syslog-ng-3.3.6/etc/syslog-ng.conf at line 10, column 2: system(); ^^^^^^ syslog-ng documentation: http://www.balabit.com/support/documentation/?product=syslog-ng mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng # Compiler Option ------------------------------------- syslog-ng Open Source Edition 3.3.6 configured Compiler options: compiler : gcc -std=gnu99 compiler options : -g -O2 -Wall -pthread -D_LARGE_FILES=1 -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/opt/soe/local/syslog-ng-3.3.6/eventlog/include/eventlog -I$(top_srcdir)/lib/ivykis/lib/include -I$(top_builddir)/lib/ivykis/lib/include -I$(top_srcdir)/lib/ivykis/modules/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 linker flags : -L/opt/soe/local/syslog-ng-3.3.6/lib -L/usr/local/lib -L/usr/ccs/lib -L/usr/lib -lpthread -Wl,-brtl prefix : /opt/soe/local/syslog-ng-3.3.6 linking mode : dynamic __thread keyword : yes Submodules: ivykis : internal libmongo-client : internal Features: Debug symbols : no GCC profiling : no Memtrace : no IPV6 support : yes spoof-source support : no tcp-wrapper support : no Linux capability support : no PCRE support : no Env wrapper support : yes systemd support : no (unit dir: none) Modules: Module search path : /opt/soe/local/syslog-ng-3.3.6/lib/syslog-ng Default module list : affile,afprog,afsocket,afuser,basicfuncs,csvparser,dbparser,syslogformat Sun STREAMS support (module): no SSL support (module) : no SQL support (module) : no PACCT module (EXPERIMENTAL) : no MongoDB destination (module): yes JSON support (module) : no (using no) Could any one assist please.

2 2

[Bug 212] New: strange hostnames from /etc/hosts with threaded(yes);
by bugzilla＠bugzilla.balabit.com 21 Dec '12

21 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=212 Summary: strange hostnames from /etc/hosts with threaded(yes); Product: syslog-ng Version: 3.3.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: bpkroth(a)gmail.com Type of the Report: --- Estimated Hours: 0.0 Created an attachment (id=67) --> (https://bugzilla.balabit.com/attachment.cgi?id=67) syslog-ng.conf Hi, I've backported syslog-ng 3.3.5 for Debian squeeze in order to get the threaded feature for our main syslog server, but I've found that with threaded(yes) and sending logs to directories byhost ($FROM_FULLHOST) set, then I get a few directories that are actually weird mashups from entries in /etc/hosts (eg: fqdn{tab}shortname{newline}, where {tab} is an actual tab character, similarly for newlines). As an example: 13 lager.$domain lager loghost 2.208 ldap1.$domain ldap1 Here, 13 and 2.208 are the last part of the IP listing for that host, but the rest is missing. This seems similar to Bug #183, except that I'm not getting segfaults, just goofy log file names and directory names, which in turn causes some other problems on our end. For now, I've disabled threaded (and was happy to find that the CPU load on the machine is still quite reduced, so good work on whatever other scalability improvements you've done - epoll?), but I'd like to take advantage of the slew of cores the machine has. use_dns(yes) and dns_cache(yes) are set, but it doesn't use a persistent file, but rather the system resolver is set to 127.0.0.1 and there's a local bind named slave running (which has all of the necessary reverse lookup information). Attached is my full conf file. Please let me know if you need anymore info. Thanks, Brian -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 19

syslog-ng 3.4.0beta1 has been released
by devel＠balabit.hu 20 Dec '12

20 Dec '12

------------------------------------------------------------------------------ PACKAGE : syslog-ng VERSION : 3.4.0beta1 SUMMARY : new stable release DATE : Dec 15, 2012 ------------------------------------------------------------------------------ DESCRIPTION: A new version of syslog-ng Open Source Edition (3.4.0beta1) has been released. For latest fixes in the 3.4.x feature branch you are recommended to upgrade to this version. CHANGES: 3.4.0beta1 Sat, 15 Dec 2012 02:21:14 +0100 Features: ========= * Added support for the amqp() destination driver, which sends messages to an AMQP queue. * Added support for a new parser named syslog-parser() that can invoke the RFC3164 and RFC5424 parser outside the source driver that received the message. Delaying the syslog parsing can be advantageous in case some preprocessing or filtering needs to take place before the actual syslog parsing. * Added support for dot notation in the $(format-json) template function. * Changed the MongoDB driver to use inserts instead of upserts. * Added support for UNIX domain sockets in the MongoDB driver by using the new path() option. * Added new template functions to perform various cryptographic hash functions on data, like: $(md5), $(md4), $(sha1), $(sha256), $(sha512) * Added a couple of new parsers to db-parser() pattern format: * @PCRE@: use this to parse using a regexp * @EMAIL@: to parse email addresses * @HOSTNAME@: to parse host names * @LLADDR@: to parse link-level addresses, like ethernet MAC addresses * Added the possibility to set TCP keepalive options for TCP based transports: tcp-keepalive-time(), tcp-keepalive-probes(), tcp-keepalive-intvl(). Also added the tcp-keepalive() option as an alias to the earlier so-keepalive() parameter. TCP keepalive became enabled by default. Bugfixes: ========= * Updated with the bugfixes from v3.3.7 * Fixed SQL statement formatting used to create indexes on Oracle. The original query contained an apostrophe when specifying the column name. * Fixed an incorrect validation in the file() source, which caused the entire file to be resent in case syslog-ng was restarted and an encoding() is specified. * Increased the performance when following files with the encoding() option set. Previously, the code to check if the source encoding is fixed size was incorrect, which in turn caused syslog-ng to excercise its slow path when processing these files, instead of a faster alternative. * Fixed a memory leak issue when encoding() is used for file sources and syslog-ng was reloaded. * Fixed a bug in processing the encoding() option for udp() sources. syslog-ng incorrectly propagated the character decoding state from one frame to the next, which might have originated from different senders. * Infinite feedback loops of internal messages triggering another set of internal messages are now detected and suppressed. Earlier it was not safe to enable debug/trace messages during runtime, now it is. * Fixed a race condition in resolving IP address to hostnames, which might have caused garbage in the hostname part of messages. This is most likely mitigated by the DNS cache. Other changes: ============== * Added unit test coverage for various log transport implementations. * Reorganized the LogProto code to support plugins, the transport() option for the syslog() and network() drivers can be used to specify a transport protocol plugin. Credits: ======== syslog-ng is developed as a community project, and as such it relies on volunteers to do the work necessarily to produce syslog-ng. Reporting bugs, testing changes, writing code or simply providing feedback are all important contributions, so please if you are a user of syslog-ng, contribute. These people have helped in this release: Attila Nagy <bra(a)fsn.hu> Balazs Scheidler <bazsi(a)balabit.hu> Balint Kovacs <blint(a)balabit.hu> Brian Kroth <bpkroth(a)gmail.com> Conrad Hoffmann <ch(a)bitfehler.net> Csaba Major <csaba.major(a)balabit.com> Cy Schubert <cy(a)FreeBSD.org> Eun Kyung <ekyung01(a)googlemail.com> Evan Rempel <erempel(a)uvic.ca> Gergely Nagy <algernon(a)balabit.hu> Jose Oliveira <jpo(a)di.uminho.pt> Juhasz Viktor <jviktor(a)balabit.hu> Marvin Nipper <marvin.nipper(a)stream.com> Michael Hocke <michael.hocke(a)nyu.edu> Peter Czanik <czanik(a)balabit.hu> Peter Gyongyosi <gyp(a)balabit.hu> Sandor Geller <wildy(a)muhelybt.hu> Sergey <cloun-rulez(a)yandex.ru> shih dane <daneshih1125(a)gmail.com> Tamas Pal <folti(a)balabit.hu> Viktor Juhasz <jviktor(a)balabit.hu> DOWNLOAD: You can download the source or binary packages from: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… The documentation of the syslog-ng Open Source Edition is available in The syslog-ng Open Source Edition Administrator's Guide at http://www.balabit.com/support/documentation/

2 2

Re: [syslog-ng] syslog-ng Digest, Vol 92, Issue 18
by Frank Scalzo 20 Dec '12

20 Dec '12

> Message: 12 > Subject: Re: [syslog-ng] having an issue with syslog and SElinux > > > On 2012-12-18 14:40, Frank Scalzo wrote: >> kernel: : type=1400 audit(1355841452.964:21866): avc: denied { fowner >> } for pid=861 comm="syslog-ng" capability=3 >> scontext=system_u:system_r:syslogd_t:s0 >> tcontext=system_u:system_r:syslogd_t:s0 tclass=capability >> >> >> How do i fix this without disabling SElinux > > Which Linux distribution are you using? And which versions of syslog-ng > and selinux? A copy of your syslog-ng configuration file would > also be helpful. Im running the following Red Hat Enterprise Linux Server release 6.3 (Santiago) selinux-3.7.19-187 syslog-ng 3.2.5 Installer-Version: 3.2.5 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.2#master#9d4bea28198bd731df1a61e980a2af5b88d81116 Compile-Date: Jan 15 2012 19:47:30 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: off Enable-SQL: on Enable-Linux-Caps: off Enable-Pcre: on Enable-Pacct: off conf below: @version:3.2 # syslog-ng configuration file. # # This should behave pretty much like the original syslog on RedHat. But # it could be configured a lot smarter. # # See syslog-ng(8) and syslog-ng.conf(5) for more information. # options { flush_lines(100); log_fetch_limit(100); log_iw_size(100); log_fifo_size(1000); time_reopen (10); log_fifo_size (1000); use_dns (yes); use_fqdn (yes); create_dirs (yes); keep_hostname (yes); }; source s_sys { file ("/proc/kmsg" program_override("kernel: ")); unix-stream ("/dev/log"); internal(); # udp(ip(0.0.0.0) port(514)); }; destination d_cons { file("/dev/console"); }; destination d_mesg { file("/var/log/messages"); }; destination d_auth { file("/var/log/secure"); }; destination d_mail { file("/var/log/maillog" flush_lines(10)); }; destination d_spol { file("/var/log/spooler"); }; destination d_boot { file("/var/log/boot.log"); }; destination d_cron { file("/var/log/cron"); }; destination d_kern { file("/var/log/kern"); }; destination d_mlal { usertty("*"); }; filter f_kernel { facility(kern); }; filter f_default { level(info..emerg) and not (facility(mail) or facility(authpriv) or facility(cron)); }; filter f_auth { facility(authpriv); }; filter f_mail { facility(mail); }; filter f_emergency { level(emerg); }; filter f_news { facility(uucp) or (facility(news) and level(crit..emerg)); }; filter f_boot { facility(local7); }; filter f_cron { facility(cron); }; #log { source(s_sys); filter(f_kernel); destination(d_cons); }; log { source(s_sys); filter(f_kernel); destination(d_kern); }; log { source(s_sys); filter(f_default); destination(d_mesg); }; log { source(s_sys); filter(f_auth); destination(d_auth); }; log { source(s_sys); filter(f_mail); destination(d_mail); }; log { source(s_sys); filter(f_emergency); destination(d_mlal); }; log { source(s_sys); filter(f_news); destination(d_spol); }; log { source(s_sys); filter(f_boot); destination(d_boot); }; log { source(s_sys); filter(f_cron); destination(d_cron); }; ## Additions for central syslog source s_udp { udp(); }; source s_tcp { tcp(ip(0.0.0.0) port(514)); }; destination d_hosts { file("/var/log/hosts/$HOST/$YEAR$MONTH$DAY" owner(syslog) group(syslog) perm(0644) dir_perm(0755) create_dirs(yes)); }; log { source(s_udp); destination(d_hosts); }; log { source(s_tcp); destination(d_hosts); }; # For testing: aka logger "my little pony" #log { source(s_sys); destination(d_hosts); }; ## End additions for central syslog # vim:ft=syslog-ng:ai:si:ts=4:sw=4:et: On Dec 20, 2012, at 8:59 AM, syslog-ng-request(a)lists.balabit.hu wrote: > Send syslog-ng mailing list submissions to > syslog-ng(a)lists.balabit.hu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.balabit.hu/mailman/listinfo/syslog-ng > or, via email, send a message with subject or body 'help' to > syslog-ng-request(a)lists.balabit.hu > > You can reach the person managing the list at > syslog-ng-owner(a)lists.balabit.hu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of syslog-ng digest..." > > > Today's Topics: > > 1. syslog-ng Insider - December 2012 (Peter Czanik) > 2. [Bug 213] Build Failure on AIX with syslog-ng-3.3.6 and gcc > 4.2.0 (bugzilla(a)bugzilla.balabit.com) > 3. [Bug 213] Build Failure on AIX with syslog-ng-3.3.6 and gcc > 4.2.0 (bugzilla(a)bugzilla.balabit.com) > 4. [Bug 214] Build / Install Issues on AIX > (bugzilla(a)bugzilla.balabit.com) > 5. [Bug 214] Build / Install Issues on AIX > (bugzilla(a)bugzilla.balabit.com) > 6. [Bug 173] Compile issues with syslog-ng_3.3.4.tar.gz > (bugzilla(a)bugzilla.balabit.com) > 7. [Bug 61] udp6 source declaration causes syslog forwarding to > assume IPv6 (bugzilla(a)bugzilla.balabit.com) > 8. [Bug 42] capabilities, chown, chmod > (bugzilla(a)bugzilla.balabit.com) > 9. [Bug 213] Build Failure on AIX with syslog-ng-3.3.6 and gcc > 4.2.0 (bugzilla(a)bugzilla.balabit.com) > 10. [Bug 61] udp6 source declaration causes syslog forwarding to > assume IPv6 (bugzilla(a)bugzilla.balabit.com) > 11. [Bug 61] udp6 source declaration causes syslog forwarding to > assume IPv6 (bugzilla(a)bugzilla.balabit.com) > 12. Re: having an issue with syslog and SElinux (Jose Pedro Oliveira) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 20 Dec 2012 12:01:01 +0100 > From: Peter Czanik <czanik(a)balabit.hu> > Subject: [syslog-ng] syslog-ng Insider - December 2012 > To: Syslog-ng users' and developers' mailing list > <syslog-ng(a)lists.balabit.hu> > Message-ID: <50D2EFED.9080108(a)balabit.hu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > Dear syslog-ng users, > > > This is the 19th issue of the syslog-ng Insider, a monthly newsletter > that brings you syslog-ng related news. > > Your feedback and news tips about the next issue is welcome at > documentation(a)balabit.com <mailto:documentation@balabit.com> > > > FEATURED NEWS > > > syslog-ng 3.4 beta1 is released > > ------------------------------- > > Version 3.4 beta1was released thisweek, right before the > Christmasholidays. It has many new features and bug fixes even since the > last alpha release, most notably a new AMQP destination a JSON parser > and a reworked syslog parser and network configuration, which makes > configuring syslog-ng even more simple and flexible. > > For a complete list of changes, check the announcement at > https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… > > For binary package availability check our 3^rd party binary page at > http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… > > > balabit.logstore 0.1.0 is released > > ---------------------------------- > > The second version of the balabit.logstore project was announced last > week. It is a library written in Clojure, that tries to provide a > convenient API to read syslog-ng PE LogStore files. Development is still > in its early phases, but it can already read unencrypted logstore files, > search in them and print many useful information about them. Compared to > the previous version, this has a Java API. > > For more details, check the announcement at > https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html > > > > NEW RELEASES: > > * > > syslog-ng OSE 3.4 beta1: > https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… > > * > > balabit.logstore 0.1.0: > https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html > > ARCHIVE > > > http://insider.blogs.balabit.com/ > > -- > Peter Czanik (CzP) <czanik(a)balabit.hu> > BalaBit IT Security / syslog-ng upstream > http://czanik.blogs.balabit.com/ > > > > > ------------------------------ > > Message: 2 > Date: Thu, 20 Dec 2012 13:02:58 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 213] Build Failure on AIX with > syslog-ng-3.3.6 and gcc 4.2.0 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120258.155B339DC65(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=213 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|--- |3.3.8 > CC| |algernon(a)balabit.hu > AssignedTo|bazsi(a)balabit.hu |algernon(a)balabit.hu > > > > > --- Comment #3 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:02:57 --- > Thanks for the report and the patch, I will apply this to 3.3's git head shortly, with some minor modifications: I don't want to replace GLOB_NOMAGIC with > GLOB_NOCHECK, as they're not the same. > > With GLOB_NOMAGIC, "/etc/syslog-ng/foo.conf" both would return foo.conf, but for "/etc/syslog-ng/conf.d/*.conf", NOCHECK would return the pattern, NOMAGIC > would return GLOB_NOMATCH. So on platforms that do have NOMAGIC, syslog-ng should use it, on others, it should fall back to NOCHECK as the next best option. > > I plan to do this with something along these lines: > > #ifndef GLOB_NOMAGIC > #define GLOB_NOMAGIC GLOB_NOCHECK > #endif > > Or better yet, implement NOMAGIC if the platform does not support it. I'll see which option is more feasible in our case. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 3 > Date: Thu, 20 Dec 2012 13:03:08 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 213] Build Failure on AIX with > syslog-ng-3.3.6 and gcc 4.2.0 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120308.8D50439DC58(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=213 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |ASSIGNED > > > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 4 > Date: Thu, 20 Dec 2012 13:06:40 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 214] Build / Install Issues on AIX > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120640.1E33C39DC6B(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=214 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |algernon(a)balabit.hu > AssignedTo|bazsi(a)balabit.hu |algernon(a)balabit.hu > > > > > --- Comment #2 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:06:40 --- > (In reply to comment #1) >> Also to note, version 3.2.5 does not have any issues with lib/syslog-ng/libafsocket.so dependencies... the ldd output doesn't seem to indicate a requirement >> for libsyslog-ng-crypto. >> > > libsyslog-ng-crypto was split out of libsyslog-ng in 3.3. > > My guess is that libsyslog-ng-crypto gets installed into /opt/local/syslogng/lib/syslog-ng/, which is not on the dynamic loader's path, and the AIX linker > thingies do not support RPATH. > > The best course of action here would be to link libsyslog-ng-crypto directly into libsyslog-ng, I believe. Or, move it out of lib/syslog-ng, into lib/ itself. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 5 > Date: Thu, 20 Dec 2012 13:06:52 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 214] Build / Install Issues on AIX > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120652.23B0039DC75(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=214 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|--- |3.3.8 > Status|NEW |ASSIGNED > > > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 6 > Date: Thu, 20 Dec 2012 13:09:21 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 173] Compile issues with > syslog-ng_3.3.4.tar.gz > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220120921.688A011E004(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=173 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REOPENED |NEEDINFO > > > > > --- Comment #4 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:09:21 --- > (In reply to comment #3) >> (In reply to comment #2) >>> Is this still and issue, or can I close it? I don't think this is a bug in syslog-ng... >>> >> >> I am facing the same issue while compiling syslog-ng-3.4.0-alpha3 on CentoOS 6.3 . > [...] >> when i set the env varilable export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig , eventlog went through fine but glib gave errors >> checking for GLIB... no >> configure: error: Package requirements (glib-2.0 >= 2.10.1 gmodule-2.0 gthread-2.0) were not met: > [...] > > Can you attach the config.log files from all three configure runs? That would help me figure out what goes wrong. > > Thanks! > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 7 > Date: Thu, 20 Dec 2012 13:12:03 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 61] udp6 source declaration causes syslog > forwarding to assume IPv6 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220121203.AA09339DC23(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=61 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|3.0.6 |3.4.1 > > > > > --- Comment #5 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:12:03 --- > This is partially fixed in 3.4 already with the network() statement, we only need to force syslog() to set last_addr_family to IPv4. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 8 > Date: Thu, 20 Dec 2012 13:15:24 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 42] capabilities, chown, chmod > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220121524.A692E39DCAA(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=42 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |algernon(a)balabit.hu > Resolution| |FIXED > Status|REOPENED |RESOLVED > > > > > --- Comment #10 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:15:23 --- > I'm closing this issue, as I believe it is not relevant for recent syslog-ng anymore. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 9 > Date: Thu, 20 Dec 2012 14:12:50 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 213] Build Failure on AIX with > syslog-ng-3.3.6 and gcc 4.2.0 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220131250.317AC39DC2A(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=213 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution| |FIXED > Status|ASSIGNED |RESOLVED > > > > > --- Comment #4 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 14:12:49 --- > (In reply to comment #3) >> Or better yet, implement NOMAGIC if the platform does not support it. I'll see which option is more feasible in our case. > > This is what I ended up doing, as the code required was pretty simple. I pushed the fix for both the iv_event.h include and the GLOB_NOMAGIC implementation to > 3.3's master, both will be part of syslog-ng 3.3.8. > > Thanks for the report! > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 10 > Date: Thu, 20 Dec 2012 14:19:41 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 61] udp6 source declaration causes syslog > forwarding to assume IPv6 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220131941.CE0DC39DC95(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=61 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Target Milestone|3.4.1 |3.3.8 > > > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 11 > Date: Thu, 20 Dec 2012 14:23:47 +0100 (CET) > From: bugzilla(a)bugzilla.balabit.com > Subject: [syslog-ng] [Bug 61] udp6 source declaration causes syslog > forwarding to assume IPv6 > To: syslog-ng(a)lists.balabit.hu > Message-ID: <20121220132347.5C94639DCAC(a)lists.balabit.hu> > Content-Type: text/plain; charset="UTF-8" > > https://bugzilla.balabit.com/show_bug.cgi?id=61 > > > Gergely Nagy <algernon(a)balabit.hu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution| |FIXED > Status|ASSIGNED |RESOLVED > > > > > --- Comment #6 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 14:23:47 --- > I ended up fixing this in 3.3, by forcing the syslog() destination to use IPv4, similar to how the source does it. In 3.4, network() can be used if one wants > syslog over IPv6. > > > -- > Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are watching all bug changes. > > > ------------------------------ > > Message: 12 > Date: Thu, 20 Dec 2012 13:58:55 +0000 > From: Jose Pedro Oliveira <jpo(a)di.uminho.pt> > Subject: Re: [syslog-ng] having an issue with syslog and SElinux > To: syslog-ng(a)lists.balabit.hu > Message-ID: <50D3199F.8020004(a)di.uminho.pt> > Content-Type: text/plain; charset=ISO-8859-1 > > On 2012-12-18 14:40, Frank Scalzo wrote: >> kernel: : type=1400 audit(1355841452.964:21866): avc: denied { fowner >> } for pid=861 comm="syslog-ng" capability=3 >> scontext=system_u:system_r:syslogd_t:s0 >> tcontext=system_u:system_r:syslogd_t:s0 tclass=capability >> >> >> How do i fix this without disabling SElinux > > Which Linux distribution are you using? And which versions of syslog-ng > and selinux? A copy of your syslog-ng configuration file would > also be helpful. > > jpo > -- > Jos? Pedro Oliveira > * mailto:jpo@di.uminho.pt * > > > ------------------------------ > > _______________________________________________ > syslog-ng maillist - syslog-ng(a)lists.balabit.hu > https://lists.balabit.hu/mailman/listinfo/syslog-ng > > > End of syslog-ng Digest, Vol 92, Issue 18 > *****************************************

2 1

having an issue with syslog and SElinux
by Frank Scalzo 20 Dec '12

20 Dec '12

kernel: : type=1400 audit(1355841452.964:21866): avc: denied { fowner } for pid=861 comm="syslog-ng" capability=3 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:system_r:syslogd_t:s0 tclass=capability How do i fix this without disabling SElinux

3 2

[Bug 61] udp6 source declaration causes syslog forwarding to assume IPv6
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=61 Gergely Nagy <algernon(a)balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |FIXED Status|ASSIGNED |RESOLVED --- Comment #6 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 14:23:47 --- I ended up fixing this in 3.3, by forcing the syslog() destination to use IPv4, similar to how the source does it. In 3.4, network() can be used if one wants syslog over IPv6. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 61] udp6 source declaration causes syslog forwarding to assume IPv6
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=61 Gergely Nagy <algernon(a)balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.4.1 |3.3.8 -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

[Bug 213] New: Build Failure on AIX with syslog-ng-3.3.6 and gcc 4.2.0
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=213 Summary: Build Failure on AIX with syslog-ng-3.3.6 and gcc 4.2.0 Product: syslog-ng Version: 3.3.x Platform: PC OS/Version: AIX Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: blentz(a)cswg.com Type of the Report: --- Estimated Hours: 0.0 /bin/sh ../libtool --tag=CC --mode=compile gcc -g -Wl,-blibpath:/opt/local/syslog-ng/lib:/usr/lib:/lib,-brtl -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/syslog-ng/include -pthread -I/opt/local/syslog-ng/include/glib-2.0 -I/opt/local/syslog-ng/lib/glib-2.0/include -I/opt/local/syslog-ng/include/eventlog -I/opt/local/syslog-ng/include -I/opt/local/syslog-ng/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/opt/local/syslog-ng/include -Wall -pthread -D_LARGE_FILES=1 -MT mainloop.lo -MD -MP -MF .deps/mainloop.Tpo -c -o mainloop.lo mainloop.c libtool: compile: gcc -g -Wl,-blibpath:/opt/local/syslog-ng/lib:/usr/lib:/lib,-brtl -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/syslog-ng/include -pthread -I/opt/local/syslog-ng/include/glib-2.0 -I/opt/local/syslog-ng/lib/glib-2.0/include -I/opt/local/syslog-ng/include/eventlog -I/opt/local/syslog-ng/include -I/opt/local/syslog-ng/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/opt/local/syslog-ng/include -Wall -pthread -D_LARGE_FILES=1 -MT mainloop.lo -MD -MP -MF .deps/mainloop.Tpo -c mainloop.c -DPIC -o .libs/mainloop.o mainloop.c: In function 'main_loop_call': mainloop.c:177: warning: implicit declaration of function 'iv_event_post' mainloop.c: In function 'main_loop_call_init': mainloop.c:217: warning: implicit declaration of function 'IV_EVENT_INIT' mainloop.c:218: error: invalid use of undefined type 'struct iv_event' mainloop.c:219: error: invalid use of undefined type 'struct iv_event' mainloop.c:220: warning: implicit declaration of function 'iv_event_register' make[4]: *** [mainloop.lo] Error 1 make[4]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6/lib' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/blentz/build/syslog-ng-3.3.6' make: *** [all] Error 2 Making install in lib -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 42] New: capabilities, chown, chmod
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=42 Summary: capabilities, chown, chmod Product: syslog-ng Version: 3.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: zbyniu(a)pld-linux.org Type of the Report: bug Estimated Hours: 0.0 Let's take a look at syslog-ng-3.0.1/src/affile.c lines 60-83 1. CAP_SYS_ADMIN is needed only for /proc/kmsg, it is added w/o check 2. CAP_DAC_READ_SEARCH should be added only if open fail with errno 13 2a. CAP_DAC_OVERRIDE should be added only if open fail with errno 13 and with CAP_DAC_READ_SEARCH set 3. fchown needs CAP_CHOWN unconditionaly 4. fchmod needs CAP_FOWNER if file owner != euid (root here) 5. all caps should be restored summary: - CAP_SYS_ADMIN and CAP_DAC_OVERRIDE are set always even if unnecessary, and permanently - owner, group and perm doesn't work -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 10

[Bug 61] udp6 source declaration causes syslog forwarding to assume IPv6
by bugzilla＠bugzilla.balabit.com 20 Dec '12

20 Dec '12

https://bugzilla.balabit.com/show_bug.cgi?id=61 Gergely Nagy <algernon(a)balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.0.6 |3.4.1 --- Comment #5 from Gergely Nagy <algernon(a)balabit.hu> 2012-12-20 13:12:03 --- This is partially fixed in 3.4 already with the network() statement, we only need to force syslog() to set last_addr_family to IPv4. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 0

syslog-ng Insider - December 2012
by Peter Czanik 20 Dec '12

20 Dec '12

Dear syslog-ng users, This is the 19th issue of the syslog-ng Insider, a monthly newsletter that brings you syslog-ng related news. Your feedback and news tips about the next issue is welcome at documentation(a)balabit.com <mailto:documentation@balabit.com> FEATURED NEWS syslog-ng 3.4 beta1 is released ------------------------------- Version 3.4 beta1was released thisweek, right before the Christmasholidays. It has many new features and bug fixes even since the last alpha release, most notably a new AMQP destination a JSON parser and a reworked syslog parser and network configuration, which makes configuring syslog-ng even more simple and flexible. For a complete list of changes, check the announcement at https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… For binary package availability check our 3^rd party binary page at http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… balabit.logstore 0.1.0 is released ---------------------------------- The second version of the balabit.logstore project was announced last week. It is a library written in Clojure, that tries to provide a convenient API to read syslog-ng PE LogStore files. Development is still in its early phases, but it can already read unencrypted logstore files, search in them and print many useful information about them. Compared to the previous version, this has a Java API. For more details, check the announcement at https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html NEW RELEASES: * syslog-ng OSE 3.4 beta1: https://lists.balabit.hu/pipermail/syslog-ng-announce/2012-December/000150.… * balabit.logstore 0.1.0: https://lists.balabit.hu/pipermail/syslog-ng/2012-December/019788.html ARCHIVE http://insider.blogs.balabit.com/ -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

1 0

[ANN]: balabit.logstore 0.1.0 - Open Source LogStore reader API
by Gergely Nagy 19 Dec '12

19 Dec '12

--------------------------------------------------------------- PACKAGE : com.balabit/logstore VERSION : 0.1.0 SUMMARY : Rewritten from scratch, now includes simple Java API DATE : 2012 December 15 HOMEPAGE : http://algernon.github.com/balabit.logstore --------------------------------------------------------------- DESCRIPTION: The balabit.logstore project is a library written in Clojure, that tries to provide a convenient API to read syslog-ng PE LogStore files. The reason behind the implementation is to have an independent, open source reader for the LogStore file format, so that one is not tied to syslog-ng to read one's logs stored in this format. An open implementation makes it possible to read these logs on systems where syslog-ng is not installed, or where the lgstool program is not available. LogStore itself is a storage format for log messages, supporting encryption, compression, secure timestamps, serialized messages (think name-value pairs as opposed to just a plain, formatted string) and a lot more. This format is being opened, and this library is meant to provide an implenetation for a LogStore reader, that will eventually support reading all kinds of LogStore files. This release is a complete rewrite of an earlier attempt, and this time, it comes with a simple Java API. EXAMPLE: Clojure: (ns example (:require [balabit.logstore.sweet :as logstore])) (prn (logstore/messages (logstore/from-file "/path/to/logstore/messages.store"))) Java: import BalaBit.LogStore; import clojure.lang.LazySeq; import clojure.lang.Keyword; import java.util.Map; public class LGSCat { public static void main(String[] args) { Keyword k = BalaBit.LogStore.keyword("MESSAGE"); Object o = BalaBit.LogStore.fromFile (args[0]); LazySeq s = (LazySeq) BalaBit.LogStore.messages (o); for (Object m : s.toArray()) { Map msg = (Map) m; System.out.println(msg.get(k)); } } } More examples can be found bundled with the sources, and as part of the documentation: http://algernon.github.com/balabit.logstore/#balabit.logstore.cli FEATURES: The library - while still experimental - can read most unencrypted LogStores, created by syslog-ng PE 4.0 or any later version, and the messages stored within can be explored. It comes with a test suite and quite a few examples. FUTURE DIRECTION: The library is very simple right now, the error handling is pretty much non-existent, and it does not perform any kind of validation. The Java API is very thin, and exposes far more Clojure-isms than it ideally should, this will be improved upon in the future. Once things stabilized a bit, we plan to publish ready to use JAR files that can be used from any Java or Clojure project. DOWNLOADS: The source is available from the git repository at github: git://github.com/algernon/balabit.logstore.git Documentation and more information about the library is available on its homepage at http://algernon.github.com/balabit.logstore/. -- |8]

1 1

newbie question
by Groups 14 Dec '12

14 Dec '12

Newbie question My Goals (2) To replace the current CentOS 5.x log server with a SL 6.x syslog-ng server. *************************************** *************************************** Goal 1 To have all Linux servers log by the following: All Linux servers are running either syslog or rsyslog - Accept logs from Linux servers and separate them to messages.$YEAR$MONTH$DAY secure.$YEAR$MONTH$DAY maillog.$YEAR$MONTH$DAY messages can be a 'catchall' ================== My success on Linux servers... The mods in the syslog-ng.conf I have for Linux servers does work but catches everything. *************************************** *************************************** Goal 2 To have all (Cisco) switches / routers log according to their current syslog settings Current syslog server uses /etc/hosts to log the following. Receive logging messages from network devices (Router/Switch/VPN) to 3 files #based on priority local4.err /var/log/NetLog/NetDeverr local4.notice,local4.!err /var/log/NetLog/NetDevnote local4.=debug,local4.=info /var/log/NetLog/NetDevdebug #Receive logging messages from all other devices to 3 files based on priority syslog.err /var/log/OtherLog/OthDeverr syslog.notice,syslog.!err /var/log/OtherLog/OthDevnote syslog.=debug,syslog.=info /var/log/OtherLog/OthDevdebug #Receive logging messages from all wireless devices to 3 files based on priority local3.err /var/log/NetLog/Wirelesserr local3.notice,local3.!err /var/log/NetLog/Wirelessnote local3.=debug,local3.=info /var/log/NetLog/Wirelessdebug #Receive logging messages from all UPS's to 3 files based on priority local5.err /var/log/UPSLog/UPSerr local5.notice,local5.!err /var/log/UPSLog/UPSnote local5.=debug,local5.=info /var/log/UPSLog/UPSdebug *************************************** Thx for any pointers. tk --------------------- rsyslog is turned off -- OS: Scientific Linux 6.2 (RHEL 6 clone) -- #syslog-ng -V syslog-ng 3.2.5 Installer-Version: 3.2.5 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline--3.2#master#9d4bea28198bd731df1a61e980a2af5b88d81116 Compile-Date: Jan 15 2012 19:52:28 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: on Enable-SSL: off Enable-SQL: on Enable-Linux-Caps: off Enable-Pcre: on Enable-Pacct: off -- syslog-ng.conf (out of the box) with one change create_dirs (yes); --------------------- @version:3.2 # syslog-ng configuration file. # # This should behave pretty much like the original syslog on RedHat. But # it could be configured a lot smarter. # # See syslog-ng(8) and syslog-ng.conf(5) for more information. # options { flush_lines (0); time_reopen (10); log_fifo_size (1000); long_hostnames (off); use_dns (no); use_fqdn (no); create_dirs (yes); keep_hostname (yes); }; source s_sys { file ("/proc/kmsg" program_override("kernel: ")); unix-stream ("/dev/log"); internal(); # udp(ip(0.0.0.0) port(514)); }; destination d_cons { file("/dev/console"); }; destination d_mesg { file("/var/log/messages"); }; destination d_auth { file("/var/log/secure"); }; destination d_mail { file("/var/log/maillog" flush_lines(10)); }; destination d_spol { file("/var/log/spooler"); }; destination d_boot { file("/var/log/boot.log"); }; destination d_cron { file("/var/log/cron"); }; destination d_kern { file("/var/log/kern"); }; destination d_mlal { usertty("*"); }; filter f_kernel { facility(kern); }; filter f_default { level(info..emerg) and not (facility(mail) or facility(authpriv) or facility(cron)); }; filter f_auth { facility(authpriv); }; filter f_mail { facility(mail); }; filter f_emergency { level(emerg); }; filter f_news { facility(uucp) or (facility(news) and level(crit..emerg)); }; filter f_boot { facility(local7); }; filter f_cron { facility(cron); }; ## Begin Mods source s_udp { udp( flags(no-parse) ); };# An UDP source source s_tcp { tcp( flags(no-parse) ); };# An TCP source ###### Filter statements ####### ### Linux logs filter f_mailhost {host(172.25.85.41); }; filter f_merlin {host(172.25.45.10); }; ###### Destination statements ####### destination d_linux_servers {file("/var/log/devices/linux_servers/$HOST/log.$YEAR$MONTH$DAY"); }; ###### Log statements ####### ### Linux servers log {source(s_udp); filter(f_merlin); destination(d_linux_servers); }; log {source(s_udp); filter(f_mailhost); destination(d_linux_servers); }; --------------------- Thx

1 0

FreeBSD 3.4 pre beta testing
by Peter Czanik 14 Dec '12

14 Dec '12

Hello, Attached is a diff against the current sysutils/syslog-nd-devel port. Please test it, so problems could be discovered before the beta release. To use the attached diff, change to the /usr/ports/sysutils/syslog-ng-devel directory and run: patch -p1 < /path/to/prebeta.diff Changes since alpha3: - latest sources - redundant patches removed - glib json support removed (json parser needs json-c) - added patch to fix libnet (will be part of the beta release) - lot of pkg-list changes Once 3.4 beta is released I plan to update the port too. Happy testing! Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

1 0

3.4 head on FreeBSD
by Peter Czanik 12 Dec '12

12 Dec '12

Hello, While trying to compile on FreeBSD 9.1, I ran into this problem: /bin/sh ../../libtool --tag=CC --mode=compile cc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../lib -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/include/eventlog -I/usr/local/include -I/usr/local/include -I../../lib/ivykis/lib/include -I../../lib/ivykis/lib/include -I../../lib/ivykis/modules/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -pipe -I/usr/local/include/libnet116 -I/usr/local/include -fno-strict-aliasing -Wall -g -pthread -MT libafsocket_notls_la-afinet-dest.lo -MD -MP -MF .deps/libafsocket_notls_la-afinet-dest.Tpo -c -o libafsocket_notls_la-afinet-dest.lo `test -f 'afinet-dest.c' || echo './'`afinet-dest.c libtool: compile: cc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../lib -I../../lib -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/include/eventlog -I/usr/local/include -I/usr/local/include -I../../lib/ivykis/lib/include -I../../lib/ivykis/lib/include -I../../lib/ivykis/modules/include -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -pipe -I/usr/local/include/libnet116 -I/usr/local/include -fno-strict-aliasing -Wall -g -pthread -MT libafsocket_notls_la-afinet-dest.lo -MD -MP -MF .deps/libafsocket_notls_la-afinet-dest.Tpo -c afinet-dest.c -fPIC -DPIC -o .libs/libafsocket_notls_la-afinet-dest.o In file included from /usr/local/include/libnet116/libnet.h:120, from afinet-dest.c:43: /usr/local/include/libnet116/./libnet/libnet-structures.h:235: error: redefinition of typedef 'libnet_t' afinet-dest.h:35: error: previous declaration of 'libnet_t' was here gmake[4]: *** [libafsocket_notls_la-afinet-dest.lo] Error 1 gmake[4]: Leaving directory `/root/syslog-ng-devel/work/syslog-ng-3.4.0alpha3/modules/afsocket' gmake[3]: *** [all] Error 2 gmake[3]: Leaving directory `/root/syslog-ng-devel/work/syslog-ng-3.4.0alpha3/modules/afsocket' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/root/syslog-ng-devel/work/syslog-ng-3.4.0alpha3/modules' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/root/syslog-ng-devel/work/syslog-ng-3.4.0alpha3' gmake: *** [all] Error 2 *** [do-build] Error code 1 Disabling libnet support results in a successful build, but it can't be started: root@fb91:/root/syslog-ng-devel # /usr/local/etc/rc.d/syslog-ng onerestart syslog_ng not running? (check /var/run/syslog.pid). Starting syslog_ng. WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode Please update it to use the syslog-ng 3.4 format at your time of convinience, compatibility mode can operate less efficiently in some cases. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.; Unable to determine how to monitor this fd, follow_freq() not set and it is not possible to poll it with the current ivykis polling method, try changing IV_EXCLUDE_POLL_METHOD environment variable; fd='11' Error initializing log_reader, closing fd; fd='11' Error initializing message pipeline; /usr/local/etc/rc.d/syslog-ng: WARNING: failed to start syslog_ng FreeBSD installs syslog-ng-3.4.0alpha3/scl/syslog-ng.conf by default, so it needs a version bump. It can easily be fixed by me. But system() is now in C instead of shell scripts... Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/

2 3

WARNING: window sizing for tcp sources
by Anton Koldaev 11 Dec '12

11 Dec '12

Hello, I have two questions: 1. % sudo /etc/init.d/syslog-ng restart * Stopping system logging syslog-ng [ OK ] * Starting system logging syslog-ng WARNING: window sizing for tcp sources were changed in syslog-ng 3.3, the configuration value was divided by the value of max-connections(). The result was too small, clamping to 100 entries. Ensure you have a proper log_fifo_size setting to avoid message loss.; orig_log_iw_size='80', new_log_iw_size='100', min_log_fifo_size='25000' I have a lot of tcp sources, destination and options. Where should I look for this warning? I don't have "log_iw_size=80" anywhere. 2. `syslog-ng --preprocess-into=/tmp/pre.conf` ^Does it work for anybody? It writes the config file but it hangs after it for me. Is it supposed to be used when syslog-ng daemon is down? -- Best regards, Koldaev Anton

2 4

syslog-ng 3.4beta
by Balazs Scheidler 10 Dec '12

10 Dec '12

Hi, Having finally been able to finish the network() source and destination drivers I declare 3.4 as feature complete, and plan to publish 3.4beta1 fairly soon. Let's say, before the winter holiday. In hindsight, this took much longer than it should have, 3.4 has grown a lot of interesting functionality: - junctions and more complicated log processing paths - amqp destination - smtp destination - json output and parser plugins - key rewriting in destination drivers (add, remove prefixes) - a number of new template functions (uuid, hash functions, etc) - a number of new parsers in db-parser (set, pcre, ...) - allow 32 bit message and nvpair sizes - improved systemd support - demand loaded plugins - plugin support for log transport protocols and the network driver to be able to use them easily And other things I've probably forgot. I have just merged Algernon's accumulated merge queue, and will probably cherry-pick stuff before the final release and merge in the fixes from 3.3 before the beta release. If you have stuff that you want to see in the beta, please speak up now. Testing _before_ the beta would also be appreciated, so that the beta is actually usable by laymen. Thanks :) As always, the latest code is in git, Algernon builds daily snapshots. Thanks -- Bazsi

5 9

[PATCH 1/2] pdbtool: match with supplied message did not perform processing
by balint.kovacs＠balabit.com 10 Dec '12

10 Dec '12

From: Balint Kovacs <blint(a)blint.hu> Under some circumstances pdbtool match did not process the message if it was provided on the command line due to a regression introduced as part of a LogProto refactoring (2d0fb042) Signed-off-by: Balint Kovacs <blint(a)blint.hu> --- modules/dbparser/pdbtool/pdbtool.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/dbparser/pdbtool/pdbtool.c b/modules/dbparser/pdbtool/pdbtool.c index deab84d..25014fe 100644 --- a/modules/dbparser/pdbtool/pdbtool.c +++ b/modules/dbparser/pdbtool/pdbtool.c @@ -503,7 +503,7 @@ pdbtool_match(int argc, char *argv[]) { dbg_list = g_array_new(FALSE, FALSE, sizeof(RDebugInfo)); } - while (!eof && buf) + while (!eof && (buf || match_message)) { invalidate_cached_time(); if (G_LIKELY(proto)) -- 1.7.9.5

1 1

[PATCH] afsocket: Add an ip-protocol() option for the network driver
by Gergely Nagy 08 Dec '12

08 Dec '12

To make it easy to set up IPv6 sources or destinations, the network() driver should have an option to select the IP protocol. This patch does just that, in the form of an ip-protocol() option, which allows one to select either IPv4 or IPv6. In the end, this allows us to have a source as follows: source s_v6_syslog { network(port(12345) transport(framed) ip-protocol(6)); }; The option is available for both the source and destination version of network(). Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- modules/afsocket/afsocket-grammar.ym | 29 ++++++++++++++++++++++++++++- modules/afsocket/afsocket-parser.c | 1 + 2 files changed, 29 insertions(+), 1 deletion(-) diff --git a/modules/afsocket/afsocket-grammar.ym b/modules/afsocket/afsocket-grammar.ym index 7beb6e8..464d5d8 100644 --- a/modules/afsocket/afsocket-grammar.ym +++ b/modules/afsocket/afsocket-grammar.ym @@ -79,6 +79,7 @@ TLSContext *last_tls_context; %token KW_UDP6 %token KW_NETWORK %token KW_TRANSPORT +%token KW_IP_PROTOCOL %token KW_IP_TTL %token KW_SO_BROADCAST @@ -136,6 +137,8 @@ TLSContext *last_tls_context; %type <ptr> dest_afnetwork %type <ptr> dest_afnetwork_params +%type <num> afinet_ip_protocol_option + %% start @@ -149,6 +152,25 @@ start | LL_CONTEXT_DESTINATION dest_afnetwork { YYACCEPT; } ; +afinet_ip_protocol_option + : LL_NUMBER + { + CHECK_ERROR($1 == 4 || $1 == 6, @1, "ip-protocol option can only be 4 or 6!"); + if ($1 == 4) + { + $$ = AF_INET; + } + else + { + $$ = AF_INET6; + } + } + ; + +source_afinet_ip_protocol + : KW_IP_PROTOCOL '(' afinet_ip_protocol_option ')' { ((AFSocketSourceDriver *)last_driver)->address_family = $3; } + ; + source_afunix : KW_UNIX_DGRAM '(' source_afunix_dgram_params ')' { $$ = $3; } | KW_UNIX_STREAM '(' source_afunix_stream_params ')' { $$ = $3; } @@ -314,6 +336,7 @@ source_afnetwork_option : source_afinet_option | source_afsocket_transport | source_afsocket_stream_params {} + | source_afinet_ip_protocol ; source_afsocket_transport @@ -335,7 +358,10 @@ source_afsocket_transport } ; - +dest_afinet_ip_protocol + : KW_IP_PROTOCOL '(' afinet_ip_protocol_option ')' { ((AFSocketDestDriver *)last_driver)->address_family = $3; } + ; + dest_afunix : KW_UNIX_DGRAM '(' dest_afunix_dgram_params ')' { $$ = $3; } | KW_UNIX_STREAM '(' dest_afunix_stream_params ')' { $$ = $3; } @@ -500,6 +526,7 @@ dest_afnetwork_options dest_afnetwork_option : dest_afinet_option | dest_afsocket_transport + | dest_afinet_ip_protocol ; dest_afsocket_transport diff --git a/modules/afsocket/afsocket-parser.c b/modules/afsocket/afsocket-parser.c index 4065d31..f9e14a4 100644 --- a/modules/afsocket/afsocket-parser.c +++ b/modules/afsocket/afsocket-parser.c @@ -72,6 +72,7 @@ static CfgLexerKeyword afsocket_keywords[] = { { "tcp_keepalive_intvl", KW_TCP_KEEPALIVE_INTVL, 0x0304 }, { "spoof_source", KW_SPOOF_SOURCE }, { "transport", KW_TRANSPORT }, + { "ip_protocol", KW_IP_PROTOCOL }, { "max_connections", KW_MAX_CONNECTIONS }, { "keep_alive", KW_KEEP_ALIVE }, { NULL } -- 1.7.10.4

2 1