- syslog-ng - lists.balabit.hu

Trying to get json out of 3.7beta2
by Russell Fulton 08 Jul '15

08 Jul '15

Hi Thanks to various folks I managed to build 3.7b2 with json. I am now trying to convert my ELSA config to produce a parsed output in json that I can feed into Elastic Search. Having failed to make my full config work (I had to try ;) so I tried a basic one based on https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-latest-… [ Aside: minor syntax error on this page — lnside log {} you can not name parser elements ] here is my conf: @version: 3.7 source s_json { network(port(1514) flags(no-parse)); }; destination d_json { file("/data/russell/test.json” template("$(format-json --scope dot-nv-pairs)\n")); }; log { source(s_json); parser { json-parser (prefix(".json.")); }; destination(d_json); }; I get no output and ‘stats’ shows: [rful011@secmgrprd01 ~]$ sudo /usr/local/syslog-ng/sbin/syslog-ng-ctl stats SourceName;SourceId;SourceInstance;State;Type;Number src.none;;;a;processed;0 src.none;;;a;stamp;0 source;s_json;;a;processed;19375 global;payload_reallocs;;a;processed;25710 global;msg_clones;;a;processed;0 destination;d_json;;a;processed;0 center;;queued;a;processed;0 global;sdata_updates;;a;processed;0 center;;received;a;processed;19375 global;internal_queue_length;;a;processed;19378 Which is the same as I get with my full config with lots of patterns. As usual am missing something basic!

5 7

configure for beta 2 not finding jsonc on RHEL 6
by Russell Fulton 05 Jul '15

05 Jul '15

Hi I have installed the libjson-devel package via yum but ./configure says: checking for JSON: no the library is in /lib64 and headers in /usr/include/json-c/ I can’t figure out what configure options I need to get this to work. Thanks, Russell

3 3

syslog-ng 3.6.4 Debian packages are available
by Budai, László 03 Jul '15

03 Jul '15

Hi, I've just created an OBS repo[1] for syslog-ng 3.6.x series (current version: 3.6.4 [2] ). This means that this is not an official Debian/Ubuntu APT repository but one hosted by OBS. List of supported OSs (i386/amd64): * Debian 7.0 * Debian 8.0 * Ubuntu 12.04 * Ubuntu 14.04 * Ubuntu 14.10 * Ubuntu 15.04 Install ------- 1. get release key wget -qO - http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng-3.6… | sudo apt-key add - 2. add repo to APT sources eg.: /etc/apt/sources.list.d/syslog-ng-obs.list deb http://download.opensuse.org/repositories/home:/laszlo_budai:/syslog-ng-3.6… ./ Then `apt-get update` and `apt-get install syslog-ng-core=3.6.4-1` You can replace Debian_8.0 to * Debian_7.0 * xUbuntu_12.04, * xUbuntu_14.04 * xUbuntu_14.10 * xUbuntu_15.04 (`x` before Ubuntu is not a typo ;-) ) Available packages: * syslog-ng-core * syslog-ng-dbg * syslog-ng-dev * syslog-ng-mod-amqp * syslog-ng-mod-geoip * syslog-ng-mod-graphite * syslog-ng-mod-json * syslog-ng-mod-mongodb * syslog-ng-mod-redis * syslog-ng-mod-riemann * syslog-ng-mod-smtp * syslog-ng-mod-sql * syslog-ng-mod-stomp Links -------- [1] https://build.opensuse.org/project/show/home:laszlo_budai:syslog-ng-3.6 [2] https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.6.4 regards, Laszlo Budai (lbudai)

3 6

Problems trying to compile syslog-ng 3.6.4 on Solaris 11.2 (SPARC)
by Cottington-Bray, Ian 01 Jul '15

01 Jul '15

Have compiled and installed eventlog-0.2.12 (into /usr/local/syslog-ng). Now trying to compile syslog-ng I'm hitting the error shown at the end. Following commands were used to configure the environment for the compile export PKG_CONFIG_PATH=/usr/local/syslog-ng/lib/pkgconfig ./configure --prefix=/usr/local/syslog-ng --enable-sun-streams --enable-tcp-wrapper --enable-ipv6 --enable-sql --enable-ssh --with-ld-library-path=/usr/local/syslog-ng/lib --disable-amqp --enable-sun-door Any suggestions ? Thanks Ian CC modules/afsocket/modules_afsocket_libafsocket_notls_la-transport-mapper-unix.lo CC modules/afsocket/modules_afsocket_libafsocket_notls_la-transport-unix-socket.lo modules/afsocket/transport-unix-socket.c: In function â_format_proc_file_nameâ: modules/afsocket/transport-unix-socket.c:50:3: warning: format â%dâ expects argument of type âintâ, but argument 4 has type âpid_tâ [-Wformat=] g_snprintf(buf, buflen, "/proc/%d/%s", pid, proc_file); ^ modules/afsocket/transport-unix-socket.c: In function â_unix_socket_readâ: modules/afsocket/transport-unix-socket.c:219:6: error: âstruct msghdrâ has no member named âmsg_controlâ msg.msg_control = ctlbuf; ^ modules/afsocket/transport-unix-socket.c:220:6: error: âstruct msghdrâ has no member named âmsg_controllenâ msg.msg_controllen = sizeof(ctlbuf); ^ modules/afsocket/transport-unix-socket.c: In function âlog_transport_unix_dgram_socket_newâ: modules/afsocket/transport-unix-socket.c:261:3: warning: implicit declaration of function âsocket_set_pass_credentialsâ [-Wimplicit-function-declaration] socket_set_pass_credentials(fd); ^ modules/afsocket/transport-unix-socket.c: At top level: modules/afsocket/transport-unix-socket.c:36:1: warning: â_add_nv_pair_intâ defined but not used [-Wunused-function] _add_nv_pair_int(LogTransportAuxData *aux, const gchar *name, gint value) ^ modules/afsocket/transport-unix-socket.c:102:1: warning: â_add_nv_pair_proc_read_unless_unsetâ defined but not used [-Wunused-function] _add_nv_pair_proc_read_unless_unset(LogTransportAuxData *aux, const gchar *name, pid_t pid, const gchar *proc_file, const gchar *unset_value) ^ modules/afsocket/transport-unix-socket.c:115:1: warning: â_add_nv_pair_proc_read_argvâ defined but not used [-Wunused-function] _add_nv_pair_proc_read_argv(LogTransportAuxData *aux, const gchar *name, pid_t pid, const gchar *proc_file) ^ modules/afsocket/transport-unix-socket.c:135:1: warning: â_add_nv_pair_proc_readlinkâ defined but not used [-Wunused-function] _add_nv_pair_proc_readlink(LogTransportAuxData *aux, const gchar *name, pid_t pid, const gchar *proc_file) ^ gmake[2]: *** [modules/afsocket/modules_afsocket_libafsocket_notls_la-transport-unix-socket.lo] Error 1 gmake[1]: *** [all-recursive] Error 1 gmake: *** [all] Error 2 The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you are not the intended recipient you should not read, copy, retransmit or disclose its contents. If you have received this email in error please delete it from your system immediately and notify us either by email or telephone. The views expressed in this communication may not necessarily be the views held by McLaren Technology Group Limited. McLaren Technology Group Limited | McLaren Technology Centre | Chertsey Road | Woking | Surrey | GU21 4YH | UK | Company Number: 01967715

4 8

syslog-ng 3.7.0beta2
by Budai, László 26 Jun '15

26 Jun '15

3.7.0beta2 This is the second beta release of the upcoming syslog-ng OSE 3.7 branch. Changes compared to the previous alpha release: Features - Added a geoip parser. - ssl_options inside tls() extended with the following set: no-sslv2, no-sslv3, no-tlsv1, no-tlsv11, no-tlsv12 - minimal libriemann-client version bumped from 1.0.0 to 1.6.0 - TLS support added to Riemann destination - timeout() option added to Riemann destination Fixes - SyslogNg.jar removed from the release tarball. - When the configured host was not available during the initialization of afsocket destination syslog-ng just didn't start. From now, syslog-ng starts in that case and will retry connecting to the host periodically. - When a not writeable file becomes writeable later, syslog-ng recognize it (with the help of reopen-timer) and delivers messages to the file without dropping those which were received during the file was not available. - Fixed a configure error around libsystemd-journal. - --disable-python option and other Python related fixes addded to configure - Retries fixed in SQL destination. In some circumstances when retry_sql_inserts was set to 1, after an insertion failure all incoming messages were dropped. - Added DOS/Windows line ending support in config. - Parallel build is supported for Python and Java destination drivers. - Fixed compilation failure on OpenBSD - Memory leak around reload and internal queueing mechanism has been fixed. - AMQP connection process fixed. - Fixed a potential abort when the localhost name cannot be detected. - Security issue fixed around $HOST. Tech details: When the name of the host is too long, the buffer we use to format the chained hostname is truncated. However snprintf() returns the length the result would be if no truncation happened, thus we will read uninitialized bytes off the stack when we use that pointer to set $HOST with log_msg_set_value(). There can be some security implications, like reading values from the stack that can help to craft further exploits, especially in the presense of address space randomization. It can also cause a DoS if the hostname length is soo large that we would read over the top-of-the-stack, which is probably not mmapped causing a SIGSEGV. - Journal entries containing name-value pairs without '=' caused syslog-ng to crash. Instead of crashing, syslog-ng just drop these nv pairs. 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. We would like to thank the following people for their contribution: Alex Badics, Andras Mitzki, Balazs Scheidler, Bence Tamas Gedai, Fabien Wernli, Gergely Nagy, Gergo Nagy, Gyorgy Pasztor, Istvan Adam Mozes, Laszlo Budai, Peter Czanik, Robert Fekete, Tibor Benke, Viktor Juhasz, Zoltan Pallagi. — View it on GitHub <https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.7.0beta2>.

3 2

3.7beta2 packages for openSUSE / SLES
by Czanik, Péter 26 Jun '15

26 Jun '15

Hi, My unofficial syslog-ng 3.7 beta2 packages for openSUSE / SLES are now available, at this time completely untested (I'm sitting at a conference right now... :-) ). They are available at the usual location: https://build.opensuse.org/package/show/home:czanik:syslog-ng37/syslog-ng Python support failed to build on SLES11 (most likely missing pkg-config information for python) and java failed in post build checks... Have a nice weekend! Bye, Peter Czanik (CzP) <peter.czanik(a)balabit.com> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik

1 0

Migrating from syslog-ng v 3.2.5 to 3.6.4
by Tech Support 26 Jun '15

26 Jun '15

All; I am currently migrating a CentOS 6.6 server running syslog-ng 3.2.5 to a CentOS 7.1 system running syslog-ng 3.6.4. I'm trying to use the same configuration file, but I'm getting the following message: /usr/sbin/syslog-ng -v -s -f /etc/syslog-ng/syslog-ng.conf [2015-06-25T09:05:16.796854] Using /dev/log Unix socket with systemd is not possible. Changing to systemd-syslog source, which supports socket activation.; I know one problem is that I'm just not up to speed yet with systemd, but I was hoping that someone could shed some light on this error. Any help at all would be greatly appreciated. Thanks; John V. Tech Support Tech Support VoIP Business Solutions 240-215-3479 x325 <mailto:fsd@voipbusiness.us> support(a)voipbusiness.us

2 2

syslog-ng with http
by westlake 26 Jun '15

26 Jun '15

is it possible to send http-put traffic as a destination with syslog-ng? thanks

3 2

snmp traps from network devices
by Ranganathan Kanagarajan 25 Jun '15

25 Jun '15

Hi All, I have setup a syslog-ng version 3.6.3 in Suse linux. I am able to configure and get the logs from linux servers. I am trying to collect the snmp traps for the follwing logging snmp-trap emergencies logging snmp-trap alerts logging snmp-trap critical logging snmp-trap errors logging snmp-trap warnings logging snmp-trap informational logging host 10.10.10.10 snmp-server enable traps syslog PLease provide me a existing configuration file which will help me. Thanks, Ranga

2 1

CentOS7 syslog-ng 3.5.6: TLS: SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca
by Schulte, Klaus (Nokia - DE/Ulm) 25 Jun '15

25 Jun '15

Dear all, I've this source settings for TLS: source s_tcp_tls { network( transport("tls") ip(10.46.130.65) port(6514) tls( peer-verify("optional-untrusted") key-file("/etc/syslog-ng/key.d/syslog-ng.key") cert-file("/etc/syslog-ng/cert.d/syslog-ng.cert") ) ); }; But when a client connects via TCP/TLS to the syslog-ng service.. In syslog-ng these messages are showing up: syslog-ng starting up; version='3.5.6' Syslog connection accepted; fd='12', client='AF_INET(10.46.160.78:48075)', local='AF_INET(10.46.130.65:6514)' SSL error while reading stream; tls_error='SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca' I/O error occurred while reading; fd='12', error='Connection reset by peer (104)' Syslog connection closed; fd='12', client='AF_INET(10.46.160.78:48075)', local='AF_INET(10.46.130.65:6514)' Closing log transport fd; fd='12' I don't know why syslog-ng is proving the CA? As far as I know the configuration is a non-mutual authentication - so the CA shouldn't play a role in this - is this correct? The client sends messages in RFC5424 format. Any help is appriciated - I've no clue what's going wrong. Best regards Klaus ____________________________________________

2 3