December 2010 - syslog-ng - lists.balabit.hu

memory exhausted in /opt/syslog-ng/etc/syslog-ng.conf at line 5347
by Mukarram Syed 17 Dec '10

17 Dec '10

Hi , I am getting the following error when starting syslog-ng.conf file which has more than 5000 lines in it and getting the following error: # service syslog-ng start memory exhausted in /opt/syslog-ng/etc/syslog-ng.conf at line 5347. syslog-ng documentation: http://www.balabit.com/support/documentation/?product=syslog-ng mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng [FAILED] When I truncate the file to < 5000 lines it starts up fine. This is running version syslog-ng-3.0.8-1.rhel5.x86_64 Mailing list does not have any clues to it. Anything in the syslog-ng.conf file that needs to be done to accept more lines? Any ideas would be appreciated. Thanks # mukarram Mukarram Syed

6 23

Patch for launch path bug in syslog-ng.h
by Matthew Hall 17 Dec '10

17 Dec '10

Hello, When compiling syslog-ng 3.2.1 into my environment I discovered a bug in how this configure option is applied: --libexecdir=/home/y/libexec64 When this option is entered, this is generated in lib/syslog-ng.h: #if ENABLE_ENV_WRAPPER #define PATH_SYSLOGNG PATH_PREFIX "/libexec/syslog-ng" #endif As you can see this is a hard coded libexec path which does not match what my environment expects. Unfortunately it appears that the libexec variable never makes it into a C macro so I'm not totally clear on how to make a permanent patch for this one. I will work around it with something like this temporary patch for now. --- /home/megahall/syslog-ng.h 2010-12-13 15:54:56.000000000 -0800 +++ syslog-ng-3.2.1/lib/syslog-ng.h 2010-12-13 16:06:22.000000000 -0800 @@ -44,7 +44,7 @@ #define PATH_PIDFILE PATH_PIDFILEDIR "/syslog-ng.pid" #define PATH_CONTROL_SOCKET PATH_PIDFILEDIR "/syslog-ng.ctl" #if ENABLE_ENV_WRAPPER -#define PATH_SYSLOGNG PATH_PREFIX "/libexec/syslog-ng" +#define PATH_SYSLOGNG PATH_PREFIX "/libexec64/syslog-ng" #endif #define PATH_PERSIST_CONFIG PATH_LOCALSTATEDIR "/syslog-ng.persist" Another issue. Because of this bug syslog-ng fails to launch with return code 127. But it prints nothing to the console explaining why it failed: execve("/home/y/libexec/syslog-ng", ["/home/y/sbin64/syslog-ng"], [/* 21 vars */]) = -1 ENOENT (No such file or directory) exit_group(127) = ? I think some message should be added in syslog-ng/wrapper.c. This is an uncompiled example but should be very close. --- /home/megahall/wrapper.c 2010-12-13 16:15:29.000000000 -0800 +++ syslog-ng-3.2.1/syslog-ng/wrapper.c 2010-12-13 16:14:21.000000000 -0800 @@ -45,6 +45,7 @@ putenv(ldlibpath); } #endif + fprintf(stderr, "syslog-ng failed to launch because of XYZ\n"); execv(PATH_SYSLOGNG, argv); return 127; } Thanks for maintaining syslog-ng. I hope this helps keep the product great! Regards, Matthew Hall.

2 2

Convert syslog to traps
by Jay 14 Dec '10

14 Dec '10

Have a requirement to convert all incoming syslogs to SNMP traps and send it to another host. One option I could think of is to use program () destination. When I tried this option, I find that syslog-ng is continuously sending newline characters to the specified program. i.e. even when no syslog is received, syslog-ng seems to be pumping newline chars to the specified program. Also I read the warning message in admin guide that, it will open up the door to DOS attack. Could someone let me know the best way to achieve this, please ? Thanks in advance for the help. John

5 8

Microsoft SQL connect issue
by Shawn Cannon 14 Dec '10

14 Dec '10

When a Microsoft SQL connection is attempted, I get the following errors. I am trying to connect to a names instance of MS SQL over TCP 1785. Any ideas? Thanks.... Dec 13 10:33:23 syslog01 syslog-ng[27963]: Error running SQL query; type='freetds', host='sql.hidden.local\instance', port='1785', user='user', database='syslog', error='', query='CREATE TABLE syslogng (datetime varchar(16), host varchar(32), program varchar(32), pid varchar(8), message varchar(4096))' Dec 13 10:33:23 syslog01 syslog-ng[27963]: Error creating table, giving up; table='syslogng' Dec 13 10:33:23 syslog01 syslog-ng[27963]: Error checking table, disconnecting from database, trying again shortly; time_reopen='60' Shawn Cannon IT Professional http://www.shawncannon.com Contact Me <http://www.linkedin.com/pub/shawn-cannon/5/84/81a> LinkedIn<http://www.linkedin.com/pub/shawn-cannon/5/84/81a> <http://www.facebook.com/rolltidega72> Facebook<http://www.facebook.com/rolltidega72> <http://twitter.com/rolltidega> Twitter <http://twitter.com/rolltidega> My blog: My thoughts on VMworld… a week later…<http://www.shawncannon.com/?p=19>

3 13

Help configuring a basic setup
by Shawn Cannon 10 Dec '10

10 Dec '10

OK I want to setup syslog-ng to listen for syslog traffic on the standard UDP port and have the messages received logged to a Microsoft SQL database. I am having trouble finding documentation I can understand. I am a very GUI driven admin so all the command line stuff is messing with me! If anyone can assist I would appreciate it. Thanks.... Shawn Cannon IT Professional http://www.shawncannon.com Contact Me <http://www.linkedin.com/pub/shawn-cannon/5/84/81a> LinkedIn<http://www.linkedin.com/pub/shawn-cannon/5/84/81a> <http://www.facebook.com/rolltidega72> Facebook<http://www.facebook.com/rolltidega72> <http://twitter.com/rolltidega> Twitter <http://twitter.com/rolltidega> My blog: My thoughts on VMworld… a week later…<http://www.shawncannon.com/?p=19>

1 0

Re: [syslog-ng] Creating a "log" block (OSE 3.2.1)
by Eric Berggren 10 Dec '10

10 Dec '10

> thanks for noticing this error. I've corrected it in the source repo of the > adminguide, and will update the docs on the website when someone tells me if > using {} within blocks is permitted (but now buggy) or forbidden. > changing the type of the block to root should workaround the problem. I see, it's really about using { }'s within the block definition. Making it a "root" block (as a completely separately log {} stanza) is probably cleaner in this particular case, but the same restriction applies at the moment -- the example from the OSE 3.2 documentation [5.3.2]: block root mylogs() { source s_file { file("/var/log/mylogs.log" follow_freq(1)); }; destination d_local { file("/var/log/messages"); }; log { source(s_file); destination(d_local); }; }; doesn't parse either (same error on the final "};") The documentation (html/PDF) could use some minor updates in this area for clarity: - block definitions also require ()'s after the name (including non-parameterized); e.g. block root foo() { ... } - perhaps add an additional example for using parameterized blocks; e.g. block destination foo ( logname("some.log") ) { file( "/var/log/`logname`" ... ); }; destination bar { foo( logname("other.log") ) }; destination baz { foo() }; regards, -eric ps: I have yet to actually *test* any of this new functionality myself yet (later today :)

3 4

Re: [syslog-ng] Creating a "log" block (OSE 3.2.1)
by Eric Berggren 10 Dec '10

10 Dec '10

Admittedly, I ended up just using a separate log {} statement (obviating the need for the block statement in this particular instance, but using blocks successfully elsewhere -- very nice). I tested the earlier lexer patch and found it works (as I imagined you did), and sure I'll find more creative uses . Allowing the extra ";" when referencing blocks indeed makes it look more consistent . thanks again -eric > I've just committed these 3 patches that implement block support for > block statements. I've also resolved the '{' issue and also made it > possible to use several ';' characters in place of a single one.

1 0

keep_timestamp() and use_time_recvd() equivalent?
by Craig Bell 09 Dec '10

09 Dec '10

Q: Is option keep_timestamp(no) reasonably equivalent to use_time_recvd(yes)? Background: We recently upgraded from OSE v2.1 to v3.1.2. This went well, but our global options include the deprecated use_time_recvd(). We see this advisory on startup: > Your configuration file uses an obsoleted keyword, please update your configuration; keyword='use_time_recvd', change='Use R_ or S_ prefixed macros in templates' We don't modify the default templates, so adding these for the first time wouldn't be my first choice. Instead, can I simply use global option keep_timestamp(no) as a replacement? I looked around for advice, but didn't see anything obvious. Thanks in advance! -cheers, CSB

2 2

advice/assistance with parsing attempt requested
by syslog-ng2010＠hushmail.com 08 Dec '10

08 Dec '10

i've spent the better part of the past week reading and trying to understand both the documentation and list posts trying to sort this out, if anyone can offer some advice as to whether this is possible or not and if so, what i'm doing wrong; i would really appreciate it! … i have a simple enough task, or so i thought! i've got a syslog stream being received by syslog-ng with too much data. what i'd like to do is parse out pieces of the stream and write only those to a file. the tricky part is that the order of the stream is very variable so that sometimes the desired named parser preceding strings and associated values are present and sometimes not. furthermore, the extra data is also quite variable. can this challenge even be addressed with syslog-ng ose? if so, can it be done with patterned without creating a pattern for EVERY variation of possible streams? for clarification, we've tried to leverage an external perl script which does this using regexs but, it seems that it can't keep up with the stream, we only receive 10% of the original events in the output. if this (external parsing script) only way this can be done, we will continue our efforts to enhance the external script but, if this is possible to be done natively within syslog-ng, i'd rather do that. with the following configuration, i am able to generate output log entries which correctly contain the global macros of $DATE $FULLHOST $PROGRAM as well as the strings preceding the named parser variables but, not the named parser macros. my output looks like this: Dec 2 11:11:11 127.0.0.1 ABC: 0 namedparser1= namedparser2= namedparser3= namedparser4= namedparser5= *****examples of entries in source stream***** Dec 2 11:11:11 127.0.0.1 ABC: 0 namedparser1=namedparser1value extra1=extravalue1 namedparser2=namedparser2value namedparser3=namedparser3value extra2=extravalue2 namedparser4=namedparser4value namedparser5=namedparser5value extra3=extravalue3 Dec 2 11:11:11 127.0.0.1 ABC: 0 extra1=extravalue1 namedparser3=namedparser3value extra2=extravalue2 namedparser4=namedparser4value namedparser5=namedparser5value extra3=extravalue3 extra4=extravalue4 Dec 2 11:11:11 127.0.0.1 ABC: 0 namedparser1=namedparser1value extra1=extravalue1 namedparser2=namedparser2value namedparser3=namedparser3value extra2=extravalue2 namedparser4=namedparser4value extra3=extravalue3 *****examples of desired output***** Dec 2 11:11:11 127.0.0.1 ABC: 0 namedparser1=namedparser1value namedparser2=namedparser2value namedparser3=namedparser3value namedparser4=namedparser4value namedparser5=namedparser5value Dec 2 11:11:11 127.0.0.1 ABC: 0 namedparser3=namedparser3value namedparser4=namedparser4value namedparser5=namedparser5value Dec 2 11:11:11 127.0.0.1 ABC: 0 namedparser1=namedparser1value namedparser2=namedparser2value namedparser3=namedparser3value namedparser4=namedparser4value *****included in conf file***** parser pattern_db { db_parser(file("/opt/syslog-ng/config/patterndb.xml") }; template reduced { template("$DATE $FULLHOST $PROGRAM: 0 namedparser1=$NAMEDPARSER1 namedparser2=$NAMEDPARSER2 namedparser3=$NAMEDPARSER3 namedparser4=$NAMEDPARSER4 namedparser5=$NAMEDPARSER5 \n"); template_escape(no); } destination d_logfile { file("/opt/syslog-ng/logs/logfile" template(reduced)); } log { source(source); parser(pattern_db); destination(d_logfile); }; *****patterndb.xml contents***** <patterndb version='3' pub_date=''> <ruleset name='globe' id='1234567890'> <pattern>ABC</pattern> <rules> <rule provider='someone' id='123' class='system'> <patterns> <pattern>ABC namedparser1=@ESTRING:NAMEDPARSER1:\ @ namedparser2=@ESTRING:NAMEDPARSER2:\ @ namedparser3=@ESTRING:NAMEDPARSER3:\ @ namedparser4=@ESTRING:NAMEDPARSER4:\ @ namedparser5=@ESTRING:NAMEDPARSER5:\ @</pattern> <patterns> </rule> <rules> </ruleset> </patterndb> MANY thanks in advance!

5 8

[Bug 99] New: syslog-ng unable to write to files owned by another user and not world writable
by bugzilla＠bugzilla.balabit.com 08 Dec '10

08 Dec '10

https://bugzilla.balabit.com/show_bug.cgi?id=99 Summary: syslog-ng unable to write to files owned by another user and not world writable Product: syslog-ng Version: 3.1.x Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: unspecified Component: syslog-ng AssignedTo: bazsi(a)balabit.hu ReportedBy: mimosinnet(a)ningunlugar.org Type of the Report: bug Estimated Hours: 0.0 I used to have a new destination that logged messages into a file owned by a certain user. This worked in syslog-ng-3.0.4: destination problem { file("/var/log/problem.log" owner("o3o") group("users")); }; # ls -lisah problem.log 6268890 920K -rw------- 1 o3o users 915K 7 des 12:52 problem.log After upgrading to syslog-ng-3.1.1, I get the following message: Dec 7 12:52:37 o3o syslog-ng[12594]: Error opening file for writing; filename='/var/log/problem.log', error='Permission denied (13)' Dec 7 12:52:37 o3o syslog-ng[12594]: syslog-ng internal() messages are looping back, preventing loop by suppressing further messages; recurse_count='2' I can write to the file as the o3o user (i.e. echo "test" >> /var/log/problem.log). I have tried to put the file in the home directory with the same result: destination problem { file("/home/o3o/problem.log" owner("o3o") group("users")); }; I had to give world permissions to the file for syslog-ng to be able to write to it: destination problem { file("/var/log/problem.log" owner("o3o") group("users") perm(0622)); }; The file should only be writable for the specific user. This seems similar to this other bug: https://bugzilla.balabit.com/show_bug.cgi?id=52 Thanks for the attention! -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

3 5