- syslog-ng - lists.balabit.hu

no compatibility between syslog and mysql log priority more
by gatfi sami 04 Jun '09

04 Jun '09

Hi i a successfully configured a centralised syslog server using syslog-ng 2.09 here is the structure: syslog-client(read mysql error log) -------> *send* to a syslog-relay --------->* forword* to a syslog server ----> centralise in a mysql tabe 'logs' CREATE TABLE `syslogtopnet`.`log` ( `seq` int(10) unsigned NOT NULL auto_increment, `host` varchar(60) NOT NULL, `facility` varchar(40) NOT NULL, `*priority*` varchar(40) NOT NULL, `*level*` varchar(40) NOT NULL, `date_log` date NOT NULL, `time_log` time NOT NULL, `program` varchar(40) NOT NULL, `*message*` text NOT NULL, PRIMARY KEY (`seq`), KEY `index_log` (`host`) ) ENGINE=InnoDB AUTO_INCREMENT=684 DEFAULT CHARSET=latin1; my problème is : i find for exemple priority ='*Notice*' and level='*Notic*e' but in the message i find *[warn]* here is an exemple: INSERT INTO `syslogtopnet`.`log` VALUES (320,'192.168.9.195','user',* 'notice'*,*'notice'*,'2009-05-19','19:33:24','','[Tue May 19 19:33:24 2009] *[warn]* Init: Session Cache is not configured [hint: SSLSessionCache]'); INSERT INTO `syslogtopnet`.`log` VALUES (24445,'192.168.9.197','user','notice','notice','2009-06-04','17:21:02','090604','090604 17:21:02 mysqld started'), (24446,'192.168.9.197','user','notice','notice','2009-06-04','17:21:02','090604','090604 17:21:02 mysqld started'), (24447,'192.168.9.197','user',*'notice'*,*'notice'*,'2009-06-04','17:21:02','InnoDB','InnoDB: Unable to lock ./ibdata1, *error: 11*'), i discovered that apache log level are different then syslog's so !!!!! 1 wired isnt it lease is there a solution to keep the same level in the original priority? 2 beside in more than 20589 line in my table priority and level have the same values. is it normal that the level and priority are the same how can this be? thank you

1 0

Beta-testers needed for documentation draft
by Robert Fekete 03 Jun '09

03 Jun '09

Dear syslog-ng users, I am Robert Fekete, the writer of the syslog-ng Administrator Guide (and of the documentation of other BalaBit products as well). First of all, thank you very much for all of you who took the time to send me feedback and corrections about the admin guide. In the last few days, I have prepared an update for the admin guide that covers the news of the recent syslog-ng 3.0.2 OSE release, and also includes documentation for the pattern database feature. However, it seems that currently Bazsi and the other developers and testers will not have time to review the docs for a few weeks. So if you have some time and would line to test the pattern database, the draft is available at http://people.balabit.hu/frobert/syslog-ng-v3.0-guide-admin-en-6ed-draft.pdf If you find anything that is unclear, not accurate, or otherwise wrong (especially in the config examples), please let me know either here on the list, or via the documentation(a)balabit.com address. Among others, the following sections need review: Section 2.12, “Classifying log messages” (p. 15), Section 3.9, “Classifying messages” (p. 61), and Section 8.6.2, “Pattern databases” (p. 201). Thank you very much for your help. Regards, Robert Fekete

2 1

syslog-ng 3.0.2 issues: Extraneous colon (:) in forwarded log; two instances of syslog-ng
by Marvin Nipper 03 Jun '09

03 Jun '09

Hi. I'm been running syslog-ng 2.0.9 for eons, and wanted to get 3.0.2 in place, but have run into two issues. First, the prerequisite info: This is on Solaris 10 x86, and I'm running the eventlog-0.2.9 component. It has all compiled cleanly. I'm using the same script to initialize syslog-ng as I was using before. In the conf file, added in some value() parameters on my filters, in accordance with the 3.0 "warnings", and added in the @version directive, but other than that, it's essentially the same (reasonably simple) conf file I was using with my 2.0.9 version of the code. For reference, I've appended my conf file at the end of the email. "Generally" syslog-ng, seems to start-up fine, and does feed the output files that I've indicated in the conf file. If I didn't "look too closely", I would have thought it was all fine, but... My problems: As part of my test environment, I'm forwarding data from another (production 2.0.9) server, to my test server, so that I can see how things are working. Here are some (truncated) messages, showing both the original message (as it looks in the output file on the 2.0.9 server), and the second message being what gets written to the file by the 3.0.2 component: Original: May 29 09:15:05 10.132.240.25 id=firewall sn=0006B10B2E88 <truncated> Received and written by 3.0.2: May 29 09:15:05 10.132.240.25 id=firewall: sn=0006B10B2E88 <truncated> So the "bug" (I assume it to be a bug) is that "colon" that is now sitting just behind the word "firewall". When my test server is running a 2.0.9 daemon, these two lines match, but the 3.0.2 daemon has inserted that colon. I can only assume that this is tied to a bug in the filtering activity, because if you look at my conf file, you will see these lines: filter SonicWallNoise { match("id=firewall" value("MSG")) and filter(SonicWallMsgs); }; Bottom line, I am doing a filter that happens to "match on" that exact "firewall" string, and it seems like more than just coincidence that this is the exact location where that unwanted colon now appears. It seems like that filtering process has somehow injected that character into the output. (Maybe I'm just missing some "new functionality or feature" in the 3.0 docs, that would intentionally cause this?) Anyway... I'm obviously looking for any input as to why this is different, and/or how to fix it (or even just work-around the problem until it is fixed). And secondly, as my subject line implies, when I run my "/etc/init.d/syslog-ng start" scripting (the same one I've always used), I find, right away, that I now have two instances of syslog-ng running. I saw a bug report from back in 2006, mentioning a similar behavior that was related to (I think) syslog-ng restarting itself, but that was supposedly fixed. I'm ass-u-me-ing that something is now causing the daemon to restart itself, but again, when I run my 2.0.9 code on place of the 3.0.2 code, I get just the one copy running. Again, I'm looking for any guidance as to something that might be driving that behavior (and as I said, maybe it's just something stupid on my part, because I'm missing something "new" in the 3.0 behavior). Thanks, in advance, for any help and/or guidance as to what these issues might be. I'm glad to provide further information if it will help. Marvin Nipper syslog-ng.conf: @version:3.0 options { dir_perm(0755); perm(0600); chain_hostnames(no); keep_hostname(yes); log_fifo_size(1000); dns_cache_size(5000); dns_cache_expire(86400); dns_cache_expire_failed(86400); }; source any_udp { udp(); }; source any_tcp { tcp(port(601)); }; destination SEC {pipe("/tmp/sec"); }; destination routers_log { file("/var/adm/log/routers.log" create_dirs(yes)); }; destination ravlin_log { file("/var/adm/log/ravlin.log" create_dirs(yes)); }; destination windows_log { file("/var/adm/log/windows.log" create_dirs(yes)); }; destination workstation_log { file("/var/adm/log/workstation.log" create_dirs(yes)); }; destination catch-all_log { file("/var/adm/log/catch-all.log" create_dirs(yes)); }; destination test { file("/var/adm/log/test.log" create_dirs(yes)); }; destination dev_null {}; filter f_4 { facility(syslog) and level(info..emerg); }; log { source(any_udp); filter(f_4); destination(windows_log); flags(final); }; filter f_1 { facility(local5) and level(debug..emerg); }; log { source(any_udp); filter(f_1); destination(routers_log); flags(final); }; filter SonicWallNoise { match("id=firewall" value("MSG")) and filter(SonicWallMsgs); }; filter SonicWallMsgs { match("m=97" value("MSG")) or match("m=98" value("MSG")) or match("m=537" value("MSG")); }; log { source(any_udp); filter(SonicWallNoise); destination(dev_null); flags(final); }; filter f_3 { facility(local0) and level(debug..emerg); }; log { source(any_udp); filter(f_3); destination(ravlin_log); flags(final); }; log { source(any_tcp); destination(workstation_log); flags(final); }; log { source(any_udp); destination(catch-all_log); flags(final); }; This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

2 2

Help on trying to build syslog-ng 3.0.2 on RHEL AS 4
by Joe Wood 03 Jun '09

03 Jun '09

Hello. I'm having troubles getting syslog-ng to compile on RHEL AS 4, with all appropriate libs installed. The configure script errors out with: checking pkg-config is at least version 0.14... yes checking for GLIB - version >= 2.10.1... no *** Could not run GLIB test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GLIB is incorrectly installed. configure: error: Cannot find GLIB version >= 2.10.1: is pkg-config in path? When I examine config.log, I see the following: configure:8496: gcc -o conftest -g -O2 -Wall conftest.c >&5 conftest.c:42:18: glib.h: No such file or directory conftest.c: In function `main': conftest.c:48: error: `glib_major_version' undeclared (first use in this function) conftest.c:48: error: (Each undeclared identifier is reported only once conftest.c:48: error: for each function it appears in.) conftest.c:48: error: `glib_minor_version' undeclared (first use in this function) conftest.c:48: error: `glib_micro_version' undeclared (first use in this function) configure:8502: $? = 1 configure: failed program was: However, glib.h and all appropriate glib headers are installed in /usr/local/include, which even when specified to configure (through --includedir) it doesn't seem to pick up on.... Anyone encountered this before? Joe

2 1

intentionally dropping messages
by Jan Schaumann 03 Jun '09

03 Jun '09

Hello, I'm trying to drop a certain set of messages. Following http://www.balabit.com/dl/html/syslog-ng-admin-guide_en.html/ch07s08.html I notice that if I do *not* include a 'destination' in the 'log' statement, then a very large number of messages that should *not* be dropped are in fact dropped. As soon as I add a 'destination' to the log statement, it filters the correct messages. That is: destination d_dev_null { file("/dev/null" perm(0666) ); }; filter demo_debugfilter { (level(debug..notice) and facility(local0); }; log { source(s_udp); filter(demo_debugfilter); flags(final); }; Appears to falsely drop a number of messages that were of local1.info. As soon as I change the 'log' directive to be: log { source(s_udp); filter(demo_debugfilter); destination(d_dev_null); flags(final); }; it correctly filters only level0.{debug,info,notice}. This happens on a host with a large number of messages per second, but not on a host that receives very little traffic. I can't make much sense of this and was hoping somebody on this list could... -Jan

2 2

Re: [syslog-ng] db-parser issues
by Jakub Jankowski 03 Jun '09

03 Jun '09

On 2009-06-02, Robert Fekete wrote: > I think the problem is that you define a pattern in your xml for the program > as well: >> <program name='logger'> >> <pattern>param</pattern> > The <pattern> tag overrides the <program name>, so instead of logger, > syslog-ng thinks this rule applies to messages that have "param" in their > PROGRAM field. In addition to what you've quoted above, I also tried: 1. <program name='logger'> <pattern>logger</pattern> 2. <program name='somethingirrelevant'> <pattern>logger</pattern> and even without <pattern>: 3. <program name='logger'> All of these give me the same result - no match. Any other suggestions? Cheers, Jakub. -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D

2 1

Roadmap for syslog-ng OSE 4.0
by Balazs Scheidler 03 Jun '09

03 Jun '09

Dear syslog-ng users, The roadmap for syslog-ng OSE has been updated and published at: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system… The same page also describes important release policy changes, thus it is recommended reading for all syslog-ng users. A related blog post can be found here: http://bazsi.blogs.balabit.com/2009/05/syslog-ng-40-roadmap-plus-release.ht… -- Bazsi

1 0

plz help
by dreamywoman 02 Jun '09

02 Jun '09

Hi All last week i have installed php-syslog-ng-2.5.1 and it works and i can see all logs in my web but after week i have decided to change the version of php-syslog-ng to php-syslog-ng-2.9.8j.tgz but after web installation i decided to change the perivious version (php-syslog-ng-2.5.1 ) after that i have problems i can get logs in other file like /var/log/catchall but i cant get anything in my php-syslog-ng in my web i use tcpdump i can get logs but i cant see anything in my web what should i do? source s_remote { unix-stream("/dev/log"); internal(); udp(); }; destination d_mysql { pipe("/tmp/mysql.pipe " template("INSERT INTO logs (host, facility, priority, level, tag, date, time, program, msg) VALUES ('$HOST', '$FACILITY', '$PRIORITY', '$LEVEL', '$TAG', '$YEAR-$MONTH-$DAY', '$HOUR:$MIN:$SEC', '$PROGRAM', '$MSG' );\n") template-escape(yes)); }; log { source(s_remote); destination(d_mysql); }; what is my problem in installation?

1 0

iptables logging in a separate logfile works not properly
by Ralf Heidenreich 02 Jun '09

02 Jun '09

Hello, I have the following line in iptables: iptables -A INPUT -j LOG --log-prefix "INPUT: " In syslog-ng (/etc/syslog-ng/syslog-ng.conf) I have the following config: ############################################# options { sync (0); time_reopen (10); log_fifo_size (1000); long_hostnames (off); use_dns (no); use_fqdn (no); create_dirs (no); keep_hostname (yes); }; source s_sys { file ("/proc/kmsg" log_prefix("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" sync(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/messages"); }; destination d_mlal { usertty("*"); }; # direct iptables logs into /var/log/firewall.log destination iptables { file("/var/log/firewall.log"); }; filter iptables { match("INPUT:"); }; log { source(s_sys); filter(iptables); destination(iptables); }; filter noiptables { not match("INPUT:"); }; log { source(s_sys); filter(noiptables); destination(d_kern); }; 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); }; ################################################################ iptables loggs to /var/log/firewall.log, but also to /var/log/messages. A line in messages is: May 29 14:13:55 hostname kernel: INPUT: IN=eth0 OUT= MAC=00:16:17:6b:34:bf:00:02:85:12:c9:40:08:00 SRC=source-ip DST=server-ip LEN=104 TOS=0x00 PREC=0x00 TTL=56 ID=38612 PROTO=TCP SPT=26787 DPT=122 WINDOW=1032 RES=0x00 ACK PSH URGP=0 What I am doing wrong. with kind regards Ralf

2 3

rotate logs in recursive directories
by Reaky Rok 01 Jun '09

01 Jun '09

Hi friends I have a problem with syslog-ng in my server, I setup it successfuly in RHEL5 and It waorking without any problems, I make it a central log server for all servers in my company, The problem is that I orgnized it for each server bu date and facility like that $HOST/$YEAR.$MONTH.$DAY/$FACILITY.log which makes a lot of recursive directory for each server, Now I'm facing a problem to rotate it as I don't know how to make the logrotate rotate all this files in the recursive directories, Could you help me please, This is my /etc/logrotate.d/syslog-ng /var/log/syslog-ng { daily rotate 30 compress missingok notifempty create 0600 root root } Thanks & Best Regards Bassam Muhammad _________________________________________________________________ Windows Live™: Keep your life in sync. Check it out! http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_012009

1 0