- syslog-ng - lists.balabit.hu

Configuring syslog to log on both central server as well as local host( 3.0.7 version)
by Rakesh Rajasekharan 28 Mar '11

28 Mar '11

Hi, I am using syslog-ng 3.0.7 version. I have a requirement to log the messages on both the central server as well as my local machine. The central server is a HPUX machine and my cleint is a SUSE machine. From my SUSE machine I am able to get he messages logged on to the HPUX machine by this entry in my conf file destination loghost { tcp("20.5.68.85" port(514)); }; 20.5.68.85 being the ip for the central server. This works perfectly fine. But is this possible to ge the logs generated on my SUSE machine as well simulatneously. Please let me know if there seems any way around to do this. Thanks, Rakesh

2 1

Re: [syslog-ng] Rewrite facility names of remote logs
by Steve Smith 25 Mar '11

25 Mar '11

I'm actually writing logs out to syslog as local6 facility using log4j. Then using rsyslog, I am forwarding those logs to the syslog-ng server using 'local6.* @centrallogserverhost'. So when syslog-ng receives those logs, it writes them out to a file named local5.$DAY according to my destination configuration. So, I don't know that $PROGRAM would accurately record the name. Will give it a shot and see. -----Original Message----- From: Martin Holste [mcholste(a)gmail.com] Received: Friday, 25 Mar 2011, 12:21pm To: Syslog-ng users' and developers' mailing list [syslog-ng(a)lists.balabit.hu] CC: Steve Smith [ssmith(a)xpressdocs.com] Subject: Re: [syslog-ng] Rewrite facility names of remote logs Is "tomcat" the $PROGRAM or the $FACILITY name? I would think it would be $PROGRAM like "ssh" or "apache." On Fri, Mar 25, 2011 at 9:44 AM, Steve Smith <ssmith(a)xpressdocs.com> wrote: > I’ve setup Syslog-NG to receive logs from other servers which have been > configured as follows - > Tomcat servers are forwarding logs as facility6 to rsyslog, which then > forwards to central log server. > Apache servers are forwarding logs as faility5 to rsyslog which then > forwards to central log server. > > When I receive these logs on the central log server, they are written to > files as their facility name, i.e. local6.$DAY. > Is there a way to change or re-write the facility name on the fly so that > instead of local6.$DAY I can get the file written as tomcat.$DAY? > > Here is the configuration I’m using to store the logs - > > destination d_net { > file("/var/log/hosts/$YEAR/$MONTH/$HOST/$FACILITY.$DAY" > owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes) > ); > }; > > log { > source(s_net); > destination(d_net); > }; > > ______________________________________________________________________________ > Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng > Documentation: > http://www.balabit.com/support/documentation/?product=syslog-ng > FAQ: http://www.campin.net/syslog-ng/faq.html > > >

1 0

[RFC/RFR] value-pairs() code preview
by Gergely Nagy 25 Mar '11

25 Mar '11

Hi! It's been a while I came to the list with value-pairs(), and the last time was a syntax RFC. This time, after almost two months of barely doing a thing with it, I'm able to present some code! The downside is, that the code is horribly inefficient at this time, but it's good enough to introduce the API (as can be used by destination drivers), as that part of it should be fairly complete by now. A lengthy description will follow - I hope I won't bore anyone out of their skull. If I do, apologies, I'll try to be more entertaining next time! To refresh our memories (mine included), the syntax we're trying to implement is something like the following: ,---- | destination d_mongo { | mongodb( | value-pairs( | scope(selected_macros nv_pairs) | exclude("R_*") | exclude("S_*") | exclude("HOST_FROM") | exclude("MSG") | pair("test" "test: ${loggen.runid}") | ) | database("test") | collection("syslog") | ); | }; `---- We'd like this to include every possible name-value pair, except the ones starting with R_ or S_, MSG and HOST_FROM. As a bonus, we'll add a custom key: "test" (with a custom template; more about that later). The purpose of this, is to be able to store a whole lot of (usually structured) data that are either dynamically generated (by patterndb) or cannot be easily predicted at configuration time (like SDATA), without the need to explicitly list all keys in a template. The code is available from the 'work/value-pairs/base' branch of my git tree at git://git.balabit.hu/algernon/syslog-ng-3.3.git (or browseable online at: http://git.balabit.hu/?p=algernon/syslog-ng-3.3.git;a=shortlog;h=work/value…) Adding value-pairs() support to drivers ======================================= >From the driver's point of view, it needs to do three things to support value-pairs(): * It needs to be able to understand value-pairs(). This is fairly easy: the core grammar rules provide 'value_pair_stmt', which can be used to parse these things. To use it, one should do something along these lines (in the driver's grammar file): ,---- | driver_option | : ... | | value_pair_stmt { driver_set_value_pairs(driver_instance, last_value_pairs); } `---- Where the _set_value_pairs() function can be as simple as this: ,---- | void | driver_set_value_pairs (LogDriver *d, ValuePairs *vp) | { | MyDriver *self = (MyDriver *)d; | | value_pairs_free (self->vp); | self->vp = vp; | } `---- With this, value-pairs() are recognised. * The driver needs to set up defaults. This can be done with calling the various functions in value-pairs.h. I'm not going to describe them, they're pretty darn self explanatory, especially after one had a look at the core grammar file. The idea is, that if no value-pairs() are defined, we'll use a sane default. If the user specifies value-pairs(), then the _set_value_pairs() function will free up the defaults, and replace them with the user supplied configuration. * The driver needs to make use of value-pairs(). To actually _use_ value pairs, the driver needs to iterate over these pairs. The way to do that, is the value_pairs_foreach() function. This takes a couple of parameters: + The ValuePairs object. + A driver-supplied foreach callback (more about this later) + An NVTable (the message payload in most cases) + An NVRegistry (logmsg_registry in most cases) + A LogMessage object + An extra user_data argument, which will be passed down to the callback. The interesting things here are the callback and the user_data. The user_data pointer can be used to pass custom data to the callback, so that it can actually do something with the data it receives. The callback itself will be called for each and every name-value pair that matches the user-configured criteria, with the following arguments: + The key name + The key value + The user_data argument passed to value_pairs_foreach() Using these, the callback can do whatever it wants with the data. Do note, that both the key name and key value will likely be freed after the foreach loop completed, so if their value will be used later by the driver, it needs to copy them. An example ========== I have updated my mongodb destination driver to use value-pairs(), the code is available from the work/afmongodb-vp branch of my git tree, or browsable online at http://git.balabit.hu/?p=algernon/syslog-ng-3.3.git;a=shortlog;h=work/afmon… Using a configuration like the following: ,---- | @version: 3.3 | @include "scl.conf" | | @module afmongodb | | source s_network { | tcp(port (10514) tags("tcp-tag")); | syslog(port (10515) tags("syslog-tag")); | }; | | destination d_mongo { | mongodb( | value-pairs( | scope(selected_macros nv_pairs) | exclude("R_*") | exclude("S_*") | exclude("HOST_FROM") | exclude("MSG") | pair("test" "test: ${loggen.runid}") | ) | database("test") | collection("syslog") | ); | }; | | parser p_loggen { | db_parser( | file("etc/loggen.pdb") | ); | }; | | log { | source(s_network); | parser(p_loggen); | destination(d_mongo); | }; `---- (for etc/loggen.pdb, see the attachment of this message) When poking syslog-ng with a couple of standard loggen messages, mongodb would contain documents like the following: ,---- | { | "DATE" : "Mar 25 16:06:37", | "FACILITY" : "auth", | "HOST" : "localhost", | "MESSAGE" : "seq: 0000000018, thread: 0000, runid: 1301065597, stamp: 2011-03-25T16:06:37 PADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPADDPAD", | "PID" : "1234", | "PRIORITY" : "info", | "PROGRAM" : "prg00000", | "SDATA" : "", | "SEQNUM" : "", | "SOURCE" : "s_network", | "SOURCEIP" : "127.0.0.1", | "TAGS" : ".classifier.system,syslog-tag,.source.s_network,loggen", | "_id" : ObjectId("4d8caf7d8ccffe2227000013"), | "classifier" : { | "class" : "debug", | "rule_id" : "d7d3ada4-6907-4dad-924f-d254e8f29f92" | }, | "loggen" : { | "runid" : "1301065597", | "seq" : "0000000018", | "stamp" : "2011-03-25T16:06:37", | "thread" : "0000" | }, | "test" : "test: 1301065597" | } `---- Even though SDATA and SEQNUM are empty (there's no SDATA in the message, and SEQNUM is not supported by value-pairs() at the moment), the document in mongodb is neatly structured. Implementation details ====================== The way value-pairs() work right now, is very simple: during setup, we just store a couple of things (the scopes, as an ORed together value; the exclude patterns and the explicitly added keys). The bulk of the work is done by value_pairs_foreach(), which will construct a base set of name-value pairs, based on the scope, then iterate over them, filter out anything that is excluded, and pass the rest to the callback. When done, it goes over the explicitly added keys, and runs those through the callback too. The implementation is horribly inefficient in many ways, but for a preview, it's good enough. I'll tune it for efficiency in the near future. However, the public API should not change anymore. And that's about it! TODO ==== * Add helpers that can be used by template functions that want to support value-pairs() (for example tfjson). * Support SEQNUM * Possibly filter out empty, zero-length values, since they're kinda useless. * Performance tuning: + Pre-allocate LogTemplate structures, if possible + Try to reduce the number of memory allocations + Possibly move away from GHashTable (as used for the temporary base-set and for the explicit keys) to something lighter. * Clean up the grammar Right now, the grammar is messy, there's a lot of global symbols we use, which really should be local to value-pairs(). I still need to get familiar with bison/flex again to understand how these things work. Once these are sorted out, I'll flatten the patch set and submit a merge request. In the meantime, if anyone feels up to it, I'd appreciate any code reviews and comments. -- |8]

1 1

Rewrite facility names of remote logs
by Steve Smith 25 Mar '11

25 Mar '11

I've setup Syslog-NG to receive logs from other servers which have been configured as follows - Tomcat servers are forwarding logs as facility6 to rsyslog, which then forwards to central log server. Apache servers are forwarding logs as faility5 to rsyslog which then forwards to central log server. When I receive these logs on the central log server, they are written to files as their facility name, i.e. local6.$DAY. Is there a way to change or re-write the facility name on the fly so that instead of local6.$DAY I can get the file written as tomcat.$DAY? Here is the configuration I'm using to store the logs - destination d_net { file("/var/log/hosts/$YEAR/$MONTH/$HOST/$FACILITY.$DAY" owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes) ); }; log { source(s_net); destination(d_net); };

2 1

AUTO: James B Horwath/TheGuardian is out of the office. (returning 03/28/2011)
by James B Horwath 25 Mar '11

25 Mar '11

I am out of the office until 03/28/2011. I am out of the office until Monday March 28, 2011 and will have no access to e-mail. If there are urgent logging issues please contact Sunil Gupta at 610-807-6717. Any other issues please contact Christopher Clarke. Thanks, Jim Note: This is an automated response to your message "syslog-ng Digest, Vol 71, Issue 39" sent on 3/25/11 7:00:02. This is the only notification you will receive while this person is away. ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.

1 0

[PATCH] configure.in: Bump minimum eventlog version to 0.2.10.
by Gergely Nagy 23 Mar '11

23 Mar '11

As of a few patches ago, eventlog >= 0.2.10 is required due to evt_tag_long() use. As such, bump the requirement in configure.in to match reality. Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- configure.in | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.in b/configure.in index 7e42b3e..94fda95 100644 --- a/configure.in +++ b/configure.in @@ -21,7 +21,7 @@ dnl *************************************************************************** dnl dependencies GLIB_MIN_VERSION="2.10.1" -EVTLOG_MIN_VERSION="0.2" +EVTLOG_MIN_VERSION="0.2.10" OPENSSL_MIN_VERSION="0.9.8" LIBDBI_MIN_VERSION="0.8.0" IVYKIS_MIN_VERSION="0.18" -- 1.7.0.4

2 1

[PATCH] Fix --enable-mixed-linking mode.
by Gergely Nagy 23 Mar '11

23 Mar '11

When mixed linking is enabled, the tools (pdbtool, in particular) weren't linked against ivykis, which resulted in a link-time error, due to libsyslog-ng using ivykis, but not being linked to it. A similar problem was present in the linking of syslog-ng: -livykis DID appear in @SYSLOGNG_DEPS_LIBS@, but the neccessary library paths (when using the internal ivykis) did not. This patch fixes both problems. There is probably a more correct solution, but this will do for the time being. Signed-off-by: Gergely Nagy <algernon(a)balabit.hu> --- configure.in | 2 +- syslog-ng/Makefile.am | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.in b/configure.in index 7e42b3e..4e0160c 100644 --- a/configure.in +++ b/configure.in @@ -801,7 +801,7 @@ else # tools & unit tests that link against libsyslog-ng.so should be linked with this set of libraries. # other tools that do not use libsyslog-ng.so can use the _LIBS variables directly. - TOOL_DEPS_LIBS="$LIBS $BASE_LIBS $GLIB_LIBS $EVTLOG_LIBS $RESOLV_LIBS $LIBCAP_LIBS $PCRE_LIBS $REGEX_LIBS $DL_LIBS" + TOOL_DEPS_LIBS="$LIBS $BASE_LIBS $GLIB_LIBS $EVTLOG_LIBS $RESOLV_LIBS $LIBCAP_LIBS $PCRE_LIBS $REGEX_LIBS $IVYKIS_LIBS $DL_LIBS" # libsyslog-ng.so is linked with this set of libraries CORE_DEPS_LIBS="" diff --git a/syslog-ng/Makefile.am b/syslog-ng/Makefile.am index 33378e0..889483d 100644 --- a/syslog-ng/Makefile.am +++ b/syslog-ng/Makefile.am @@ -14,7 +14,7 @@ syslog_ng_SOURCES = main.c # libtool, because in mixed mode libtool is not used for the final linking # phase. See the comment in the configure script for details. -syslog_ng_LDADD = -L../lib/.libs -lsyslog-ng @SYSLOGNG_DEPS_LIBS@ +syslog_ng_LDADD = -L../lib/.libs -L../lib/ivykis/lib/.libs -L../lib/ivykis/modules/.libs -lsyslog-ng @SYSLOGNG_DEPS_LIBS@ syslog_ng_LINK = @SYSLOGNG_LINK@ syslog_ng_wrapper_SOURCES = wrapper.c -- 1.7.2.3

3 2

escapes in SQL statements (was Re: dbtype in SQL logging)
by Hendrik Visage 21 Mar '11

21 Mar '11

Hi there, Okay, looks like I was looking/thinking about something else, so lets explain my problem. I want the pid inseted to be a "proper" number/integer, not a string/character, and the fun starts with several of my sources not having a pid entry, thus that field I would like to be filled with NULL values. However, it still gets escaped, and when it gets escaped, the NULL is not null anymore, but the string 'NULL' :( I was hoping that in some why I could coerce syslog-ng to understand that that column is a integer column, thus should not be escaped as it is currently done ;( I have the following destination: destination d_pgsql { sql(type(pgsql) host("127.0.0.1") username("logwriter") password("logwriter") port("5432") database("syslog") table("logs_${HOST}_${R_YEAR}${R_MONTH}${R_DAY}") #or whatever you want, example ${HOST}" for hosts, ${LEVEL}" for levels.. etc columns("datetime varchar(16)", "host varchar(32)", "program varchar(16)", "pid varchar(8) default null", "message varchar") values("$R_DATE", "$HOST", "$PROGRAM", "${PID:-NULL}", "$MSG") indexes("datetime", "host", "program", "pid", "message")); }; and the following log lines: Incoming log entry; line='<166>Feb 22 08:38:59 Vpxa: [2011-02-22 08:38:59.862 1B7A7B90 verbose \'App\'] [VpxaHalServices] HostChanged Event Fired, properties changed []' Running SQL query; query='INSERT INTO logs_somedevice_20110222 (datetime, host, program, pid, message) VALUES (\'Feb 22 11:39:27\', \'somedevice\', \'Vpxa\', \'NULL\', \'[2011-02-22 08:38:59.862 1B7A7B90 verbose \'\'App\'\'] [VpxaHalServices] HostChanged Event Fired, properties changed []\')'

5 8

syslog-ng stats
by Ioan Indreias 21 Mar '11

21 Mar '11

Hello, Running with syslog-ng OSE 3.2.1 and wondering what exactly mean some of the parameters by STATS. Please find below an extract of the output we get (with the default stats_level) , hoping to receive some hints from you. global > payload_reallocs = ? global > msg_clones = ? global > sdata_updates = ? why center > received is 0 ? From OSE 3.2 manual, Chapter 14, it should be the "total number of messages received from every configured sources." BR, Ioan ### [root@myhost TOOLS]# /opt/syslog-ng/sbin/syslog-ng-ctl stats SourceName;SourceId;SourceInstance;State;Type;Number global;payload_reallocs;;a;processed;1643977 source;s_net;;a;processed;615301996 global;msg_clones;;a;processed;1230603992 destination;d_mysql1;;a;processed;247656 destination;d_mysql2;;a;processed;1354498 global;sdata_updates;;a;processed;0 center;;received;a;processed;0 center;;queued;a;processed;0 ###

2 2

Syslog-ng returning a TCP Reset
by Andy Ruch 20 Mar '11

20 Mar '11

Hello, I was evaluating syslog-ng and have come across a strange problem. When connecting to syslog-ng using the 'syslog' source, syslog-ng will return a TCP Reset at random intervals. The interesting thing about this error is it only seems to appear when the message length varies between logs. After some experimenting, I was able to reproduce the error using loggen to send logs from a file. However, when loggen generates its own fixed length messages, syslog-ng will receive everything properly. I'm concerned about the reliability of syslog-ng. I don’t want it to close the connection if it gets overloaded. I know that I can add some options to improve performance, but that seems like a patch and not a fix. I would think syslog-ng would utilize TCP flow control to prevent the sender from sending too fast. Am I doing something wrong? Does this look like a bug or have I just reached the max performance of syslog-ng? Any help is appreciated. Below I’ve included some information about the commands that I was running as well as my system setup. Thanks, Andy ***** Details ***** - Two machine setup (one sender and one receiver) - Receiver is using an evaluation copy of Syslog-PE-4.0.1a (but I first saw this issue using open source version 3.2.2 ) - CentOS 5.5 ***** Send Command ***** This is the console output that I receive from loggen. As you can see, the failure did not happen every time. In this particular case, it was the second execution that failed. I normally just run it back to back until it fails. $ ./loggen -P -r 40000 -R /tmp/syslog_10-40 10.64.27.38 6514 average rate = 16503.22 msg/sec, count=50000, time=3.297, (last) msg size=112, bandwidth=1627.75 kB/sec $ ./loggen -P -r 40000 -R /tmp/syslog_10-40 10.64.27.38 6514 Send error Connection reset by peer5 msg/sec average rate = 15483.69 msg/sec, count=15435, time=0.9968, (last) msg size=114, bandwidth=1527.27 kB/sec ***** Send File ***** The following pattern was put into a file and repeated for a total of 50,000 lines. I tried to attach the complete file but it was too large for this mailing list. Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Mar 16 10:35:28 guinness syslog-tester[proc-1234]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ***** Syslog-ng.conf ***** @version: 4.0 options { }; ###### # sources source s_local { # message generated by Syslog-NG internal(); # standard Linux log source (this is the default place for the syslog() # function to send logs to) unix-stream("/dev/log"); # messages from the kernel file("/proc/kmsg" program_override("kernel")); }; source s_net { syslog( ip(0.0.0.0) transport("tcp") port(6514) ); }; ###### # destinations destination d_messages { file("/var/log/messages"); }; destination d_tmp_file { file("/tmp/log_messages"); }; ###### # paths log { source(s_local); destination(d_messages); }; log { source(s_net); destination(d_tmp_file); flags(flow-control); };

3 2