March 2005 - syslog-ng - lists.balabit.hu

logging to two files simultaneously
by Mike Pepe 10 Mar '05

10 Mar '05

I'm trying to log to two files at the same time. What's the best way to do it? I put two destinations in a log block, but it doesn't log to both places. Is there a trick to doing this? curious... -Mike

3 2

Re: [syslog-ng]logs are not generated and managed by syslog-ng but it is started properly
by jack alex 10 Mar '05

10 Mar '05

Thanks for listening! Below message is very long! Please specially read 2nd last line of below message becz it is depicting some UNKNOW message, which can help us to resolv the issue. # syslog-ng -d -v io.c: Preparing fd 3 for reading binding fd 4, inetaddr: 0.0.0.0, port: 514 io.c: Preparing fd 4 for reading binding fd 5, unixaddr: /dev/log io.c: listening on fd 5 syslog-ng version 1.6.0rc2 starting Garbage collecting while idle... gc_mark: Marking object of class 'syslog_backend' (0) gc_mark: Marking object of class 'syslog_config' (1) gc_mark: Marking object of class 'resource_list' (2) gc_mark: Marking object of class 'io_fd' (3) gc_mark: Marking object of class 'log_reader' (4) gc_mark: Marking object of class 'affile_source' (5) gc_mark: Marking object of class 'log_source_group' (6) gc_mark: Marking object of class 'log_source_group' (7) gc_mark: Marking object of class 'log_source_group' (8) gc_mark: Marking object of class 'afunix_source' (9) gc_mark: Marking object of class 'listen_fd' (10) gc_mark: Marking object of class 'afsocket_accept_callback' (11) gc_mark: Marking object of class 'io_fd' (11) gc_mark: Marking object of class 'log_reader' (12) gc_mark: Marking object of class 'afsocket_source_connection' (13) gc_mark: Marking object of class 'afinet_source' (14) gc_mark: Marking object of class 'inet_address_info' (15) gc_mark: Marking object of class 'object_queue' (15) gc_mark: Marking object of class 'afsocket_source_close_callback' (12) gc_mark: Marking object of class 'unix_address_info' (10) gc_mark: Marking object of class 'object_queue' (10) gc_mark: Marking object of class 'log_source_driver' (10) gc_mark: Marking object of class 'log_center' (9) gc_mark: Marking object of class 'log_connection' (10) gc_mark: Marking object of class 'log_endpoint_info' (11) gc_mark: Marking object of class 'log_endpoint_info' (12) gc_mark: Marking object of class 'log_endpoint_info' (11) gc_mark: Marking object of class 'log_filter' (12) gc_mark: Marking object of class 'filter_expr_pri' (13) gc_mark: Marking object of class 'log_filter' (13) gc_mark: Marking object of class 'filter_expr_op' (14) gc_mark: Marking object of class 'filter_expr_pri' (15) gc_mark: Marking object of class 'filter_expr_op' (15) gc_mark: Marking object of class 'filter_expr_pri' (16) gc_mark: Marking object of class 'filter_expr_pri' (16) gc_mark: Marking object of class 'log_filter' (14) gc_mark: Marking object of class 'filter_expr_op' (15) gc_mark: Marking object of class 'filter_expr_pri' (16) gc_mark: Marking object of class 'filter_expr_pri' (16) gc_mark: Marking object of class 'log_filter' (15) gc_mark: Marking object of class 'filter_expr_pri' (16) gc_mark: Marking object of class 'log_filter' (16) gc_mark: Marking object of class 'filter_expr_pri' (17) gc_mark: Marking object of class 'log_filter' (17) gc_mark: Marking object of class 'filter_expr_pri' (18) gc_mark: Marking object of class 'log_filter' (18) gc_mark: Marking object of class 'filter_expr_pri' (19) gc_mark: Marking object of class 'log_filter' (19) gc_mark: Marking object of class 'filter_expr_pri' (20) gc_mark: Marking object of class 'log_filter' (20) gc_mark: Marking object of class 'filter_expr_pri' (21) gc_mark: Marking object of class 'log_filter' (21) gc_mark: Marking object of class 'filter_expr_pri' (22) gc_mark: Marking object of class 'log_filter' (22) gc_mark: Marking object of class 'filter_expr_pri' (23) gc_mark: Marking object of class 'log_filter' (23) gc_mark: Marking object of class 'filter_expr_pri' (24) gc_mark: Marking object of class 'log_filter' (24) gc_mark: Marking object of class 'filter_expr_pri' (25) gc_mark: Marking object of class 'log_filter' (25) gc_mark: Marking object of class 'filter_expr_pri' (26) gc_mark: Marking object of class 'log_filter' (26) gc_mark: Marking object of class 'filter_expr_pri' (27) gc_mark: Marking object of class 'log_endpoint_info' (11) gc_mark: Marking object of class 'log_dest_group' (12) gc_mark: Marking object of class 'affile_dest' (13) gc_mark: Marking object of class 'log_connection' (11) gc_mark: Marking object of class 'log_endpoint_info' (12) gc_mark: Marking object of class 'log_endpoint_info' (13) gc_mark: Marking object of class 'log_endpoint_info' (12) gc_mark: Marking object of class 'log_endpoint_info' (12) gc_mark: Marking object of class 'log_dest_group' (13) gc_mark: Marking object of class 'log_dest_group' (14) gc_mark: Marking object of class 'affile_dest' (15) gc_mark: Marking object of class 'affile_dest' (14) gc_mark: Marking object of class 'log_connection' (12) gc_mark: Marking object of class 'log_endpoint_info' (13) gc_mark: Marking object of class 'log_endpoint_info' (14) gc_mark: Marking object of class 'log_endpoint_info' (13) gc_mark: Marking object of class 'log_endpoint_info' (13) gc_mark: Marking object of class 'log_dest_group' (14) gc_mark: Marking object of class 'affile_dest' (15) gc_mark: Marking object of class 'log_connection' (13) gc_mark: Marking object of class 'log_endpoint_info' (14) gc_mark: Marking object of class 'log_endpoint_info' (15) gc_mark: Marking object of class 'log_endpoint_info' (14) gc_mark: Marking object of class 'log_endpoint_info' (14) gc_mark: Marking object of class 'log_dest_group' (15) gc_mark: Marking object of class 'affile_dest' (16) gc_mark: Marking object of class 'log_connection' (14) gc_mark: Marking object of class 'log_endpoint_info' (15) gc_mark: Marking object of class 'log_endpoint_info' (16) gc_mark: Marking object of class 'log_endpoint_info' (15) gc_mark: Marking object of class 'log_endpoint_info' (15) gc_mark: Marking object of class 'log_dest_group' (16) gc_mark: Marking object of class 'log_dest_group' (17) gc_mark: Marking object of class 'log_dest_group' (18) gc_mark: Marking object of class 'log_dest_group' (19) gc_mark: Marking object of class 'affile_dest' (20) gc_mark: Marking object of class 'affile_dest' (19) gc_mark: Marking object of class 'affile_dest' (18) gc_mark: Marking object of class 'affile_dest' (17) gc_mark: Marking object of class 'log_connection' (15) gc_mark: Marking object of class 'log_endpoint_info' (16) gc_mark: Marking object of class 'log_endpoint_info' (17) gc_mark: Marking object of class 'log_endpoint_info' (16) gc_mark: Marking object of class 'log_endpoint_info' (16) gc_mark: Marking object of class 'log_connection' (16) gc_mark: Marking object of class 'log_endpoint_info' (17) gc_mark: Marking object of class 'log_endpoint_info' (18) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_endpoint_info' (17) gc_mark: Marking object of class 'log_endpoint_info' (17) gc_mark: Marking object of class 'log_dest_group' (18) gc_mark: Marking object of class 'log_dest_group' (19) gc_mark: Marking object of class 'log_dest_group' (20) gc_mark: Marking object of class 'log_dest_group' (21) gc_mark: Marking object of class 'log_dest_group' (22) gc_mark: Marking object of class 'log_dest_group' (23) gc_mark: Marking object of class 'log_dest_group' (24) gc_mark: Marking object of class 'log_dest_group' (25) gc_mark: Marking object of class 'affile_dest' (26) gc_mark: Marking object of class 'affile_dest' (25) gc_mark: Marking object of class 'affile_dest' (24) gc_mark: Marking object of class 'affile_dest' (23) gc_mark: Marking object of class 'affile_dest' (22) gc_mark: Marking object of class 'affile_dest' (21) gc_mark: Marking object of class 'affile_dest' (20) gc_mark: Marking object of class 'affile_dest' (19) gc_mark: Marking object of class 'log_connection' (17) gc_mark: Marking object of class 'log_endpoint_info' (18) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_endpoint_info' (18) gc_mark: Marking object of class 'log_endpoint_info' (18) gc_mark: Marking object of class 'log_connection' (18) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_endpoint_info' (20) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_endpoint_info' (19) gc_mark: Marking object of class 'log_connection' (19) gc_mark: Marking object of class 'log_endpoint_info' (20) gc_mark: Marking object of class 'log_endpoint_info' (21) gc_mark: Marking object of class 'log_endpoint_info' (20) gc_mark: Marking object of class 'log_endpoint_info' (20) gc_mark: Marking object of class 'log_connection' (20) gc_mark: Marking object of class 'log_endpoint_info' (21) gc_mark: Marking object of class 'log_connection' (21) gc_mark: Marking object of class 'log_endpoint_info' (22) gc_mark: Marking object of class 'log_endpoint_info' (23) gc_mark: Marking object of class 'log_endpoint_info' (22) gc_mark: Marking object of class 'log_endpoint_info' (22) gc_mark: Marking object of class 'log_connection' (22) gc_mark: Marking object of class 'log_endpoint_info' (23) gc_mark: Marking object of class 'log_endpoint_info' (24) gc_mark: Marking object of class 'log_endpoint_info' (23) gc_mark: Marking object of class 'log_endpoint_info' (23) gc_mark: Marking object of class 'log_connection' (23) gc_mark: Marking object of class 'log_endpoint_info' (24) gc_mark: Marking object of class 'log_endpoint_info' (25) gc_mark: Marking object of class 'log_endpoint_info' (24) gc_mark: Marking object of class 'log_endpoint_info' (24) gc_mark: Marking object of class 'log_connection' (24) gc_mark: Marking object of class 'log_endpoint_info' (25) gc_mark: Marking object of class 'log_endpoint_info' (26) gc_mark: Marking object of class 'log_endpoint_info' (25) gc_mark: Marking object of class 'log_endpoint_info' (25) gc_mark: Marking object of class 'UNKNOWN' (1) Objects alive: 169, garbage collected: 0 Any help appreciated, -jack --- Nate Campi <nate(a)campin.net> wrote: > On Wed, Mar 09, 2005 at 01:43:55AM -0800, jack alex > wrote: > > > > I am trying to configure syslog-ng package for > > managing logs, but there is some where something > wrong > > in my configuration such that it is not > generatinglogs > > > > below file is quite long > > <SNIP> > > > Any guess , why it is not managing log, no new > logs > > have been added to log directory, as > > /var/log/messages doens't contains any new message > > after i configured syslog-ng but if i will restart > my > > syslog(the default that comes with redhat) it will > > start adding new logs to /var/log/messages. . > ...... > > Your config file is syntactically correct (syslog-ng > -s), and I don't > see anything wrong at a glance. I suppose I'd make > sure it's running (as > root since /var/log has strict file perms by > default). Maybe there's > some problem making it exit, so keep it in the > foreground in debugging > when you start it and see what you get: > > # syslog-ng -d -v > > -- > Nate > > ". . . a classic - something that everybody wants to > have read and > nobody wants to read." - speech (1900) - Samuel > Clemens > > _______________________________________________ > syslog-ng maillist - syslog-ng(a)lists.balabit.hu > https://lists.balabit.hu/mailman/listinfo/syslog-ng > Frequently asked questions at > http://www.campin.net/syslog-ng/faq.html > > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

1 0

logs are not generated and managed by syslog-ng but it is started properly
by jack alex 09 Mar '05

09 Mar '05

Dear All, I am trying to configure syslog-ng package for managing logs, but there is some where something wrong in my configuration such that it is not generatinglogs below file is quite long #vi /usr/local/etc/syslog-ng/syslog-ng.conf code: options { sync (0); time_reopen (10); log_fifo_size (1000); long_hostnames (on); use_fqdn (yes); create_dirs (no); chain_hostnames(no); keep_hostname (yes); perm(0644); dir_perm(0755); }; source s_sys { unix-stream ("/dev/log"); internal(); }; source s_udp { udp(); }; source kernel_file { file("/proc/kmsg"); }; destination d_cons { file("/dev/console"); }; destination d_spol { file("/var/log/spooler.log"); }; destination d_mesg { file("/var/log/messages.log"); }; destination d_auth { file("/var/log/secure.log"); }; destination d_uucp { file("/var/log/uucp.log"); }; destination d_boot { file("/var/log/boot.log"); }; destination d_mlal { usertty("*"); }; destination d_kern { file("/var/log/kernel.log"); }; destination numetrace { file("/var/log/numetrace.log"); }; destination nume { file("/var/log/nume.log"); }; destination postgres { file("/var/log/postgres.log"); }; destination php { file("/var/log/local2.log"); }; destination boot { file("/var/log/boot.log"); }; destination cron { file("/var/log/cron.log"); }; destination daemon { file("/var/log/daemon.log"); }; destination ftp { file("/var/log/ftp.log"); }; destination lpr { file("/var/log/lpr.log"); }; destination mail { file("/var/log/maillog"); }; destination news { file("/var/log/news.log"); }; destination syslog { file("/var/log/syslog.log"); }; destination user { file("/var/log/user.log"); }; destination local3 { file("/var/log/local3.log"); }; destination local4 { file("/var/log/local4.log"); }; destination local5 { file("/var/log/local5.log"); }; destination local6 { file("/var/log/local6.log"); }; destination emerg { file("/var/log/emerg.log"); }; destination crit { file("/var/log/crit.log"); }; destination alert { file("/var/log/alert.log"); }; destination err { file("/var/log/err.log"); }; destination warning { file("/var/log/warning.log"); }; filter cons { facility(kern); }; filter spooler { facility(uucp) or (facility(news) and level(crit)); }; filter mesg { level(info, notice, warning, err, crit, alert, emerg) and facility(kern, uucp, news, local3, local4, local5, local6, daemon, ftp, lpr); }; filter auth { facility(authpriv); }; filter emerg { level(emerg); }; filter uucp { facility(uucp); }; filter cron { facility(cron); }; filter kern_debug { facility(kern); }; filter postgres { facility(local0); }; filter nume_trace { facility(local1); }; filter nume { facility(local1) and level(info, notice, warning, err, crit, alert, emerg); }; filter php { facility(local2); }; filter local3 { facility(local3); }; filter local4 { facility(local4); }; filter local5 { facility(local5); }; filter local6 { facility(local6); }; filter boot { facility(local7); }; filter daemon { facility(daemon); }; filter ftp { facility(ftp); }; filter lpr { facility(lpr); }; filter mail { facility(mail); }; filter news { facility(news); }; filter syslog { facility(syslog); }; filter user { facility(user); }; filter warning { level(warning); }; filter crit { level(crit, alert, emerg); }; filter alert { level(alert, emerg); }; filter err { level(err, crit, alert, emerg); }; log { source(s_sys); source(s_udp); filter(cons); destination(d_cons); }; log { source(s_sys); source(s_udp); filter(mesg); destination(d_mesg); }; log { source(s_sys); source(s_udp); filter(auth); destination(d_auth); }; log { source(s_sys); source(s_udp); filter(emerg); destination(d_mlal); }; log { source(s_sys); source(s_udp); filter(uucp); destination(d_uucp); }; log { source(s_sys); source(s_udp); filter(boot); destination(boot); }; log { source(s_sys); source(s_udp); filter(php); destination(php); }; log { source(s_sys); source(s_udp); filter(postgres); destination(postgres); }; log { source(s_sys); source(s_udp); filter(nume_trace); destination(numetrace); }; log { source(s_sys); source(s_udp); filter(nume); destination(nume); }; log { source(s_sys); source(s_udp); source(kernel_file); filter(kern_debug); destination(d_kern); }; log { source(s_sys); source(s_udp); filter(cron); destination(cron); }; log { source(s_sys); source(s_udp); filter(daemon); destination(daemon); }; log { source(s_sys); source(s_udp); filter(ftp); destination(ftp); }; log { source(s_sys); source(s_udp); filter(lpr); destination(lpr); }; log { source(s_sys); source(s_udp); filter(mail); destination(mail); }; log { source(s_sys); source(s_udp); filter(news); destination(news); }; log { source(s_sys); source(s_udp); filter(syslog); destination(syslog); }; log { source(s_sys); source(s_udp); filter(user); destination(user); }; log { source(s_sys); source(s_udp); filter(local3); destination(local3); }; log { source(s_sys); source(s_udp); filter(local4); destination(local4); }; log { source(s_sys); source(s_udp); filter(local5); destination(local5); }; log { source(s_sys); source(s_udp); filter(local6); destination(local6); }; log { source(s_sys); source(s_udp); filter(spooler); destination(d_spol); }; log { source(s_sys); source(s_udp); filter(emerg); destination(emerg); }; log { source(s_sys); source(s_udp); filter(crit); destination(crit); }; log { source(s_sys); source(s_udp); filter(alert); destination(alert); }; log { source(s_sys); source(s_udp); filter(err); destination(err); }; log { source(s_sys); source(s_udp); filter(warning); destination(warning); }; filter ext_filter { level(warning) or level(err) or level(alert) or level(crit) or level(emerg) or facility(authpriv); }; log { source(s_sys); source(s_udp); source(kernel_file); filter(ext_filter); }; Any guess , why it is not managing log, no new logs have been added to log directory, as /var/log/messages doens't contains any new message after i configured syslog-ng but if i will restart my syslog(the default that comes with redhat) it will start adding new logs to /var/log/messages. . ...... -jack __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/

2 1

[Fwd: RE: [syslog-ng]Syslog-NG 1.6.6 memory leak when sending UDP logs]
by Balazs Scheidler 08 Mar '05

08 Mar '05

Hi, Some more information about the memory leak. The last fix seems to have fixed for others. Thanks for the report Bryan. So as it seems the spoof related memory leak seems to have been fixed by my last patch. Henry's problem seems to be related but a different bug either in syslog-ng or in libnet. -------- Forwarded Message -------- > From: Ignatow, Bryan <Bryan.Ignatow(a)acs-inc.com> > To: Balazs Scheidler <bazsi(a)balabit.hu> > Subject: RE: [syslog-ng]Syslog-NG 1.6.6 memory leak when sending UDP > logs > Date: Fri, 4 Mar 2005 11:57:46 -0600 > > > A private reply - my home e-mail address is subscribed, not my work. > Feel free to forward to the list. > > We use syslog-ng on some very busy Syslog servers. About 1M logs a > day on average on the largest one. We UDP forward with spoofing over > 300K of those messages a day on average. > > We have been seeing memory problems since we first implemented 1.6.4, > and I recently upgraded to 1.6.6. and libol 0.3.15 (from 0.3.13) and > have been using libnet 1.1.2.1. We compile from source. The system > is a Fedora Core 1 reasonably fully patched, running > 2.4.22-1.2199.nptlsmp on a dual HyperThreaded P4 3GHz with 2 GB of > memory. Well... I am not sure if they were memory leaks, but the > process would keel over when it reached about 3GB of virtual (2GB > resident) in size. Restarting the process would clear the memory > problem. > > I decided since the upgrade to 1.6.6 didn't fix it, I would subscribe > to the mailing list and see what was out there (a shocking concept I > know... but I am a maverick). That is where I ran across this thread. > > I saw the note in the archive from Feb 28th with the patch to afinet.c > adding the "ol_string_free(msg_line);" line I gave this a shot and it > has really helped. We are holding steady at: > > PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU > COMMAND > 4316 root 15 0 1220 1216 756 S 0.0 0.0 5:33 0 > syslog-ng > > We started somewhere around 1023K resident and have not moved up > hardly at all in the 4 days since we put this code in place. Before > we were moving up 8K every 2 seconds. > > Hope this helps, > > Bryan > > > -----Original Message----- > From: syslog-ng-admin(a)lists.balabit.hu > [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Balazs > Scheidler > Sent: Friday, March 04, 2005 11:20 AM > To: syslog-ng(a)lists.balabit.hu > Subject: Re: [syslog-ng]Syslog-NG 1.6.6 memory leak when sending UDP > logs -- Bazsi

2 1

Syslog: Router konfiguration
by kblumer＠gmx.ch 08 Mar '05

08 Mar '05

Hi all I tried to get syslog messages from a router, but I do not get any messages. From ohter Systems it works. Does it something have to do with my syslog configuration on the routers (operational state = inactive)? TK>show syslog base SYSLOG Base Information ----------------------- Configured Maximum # of Poll iteration State hosts allowed timer ---------- ------------- -------------- Enabled 5 5 Operational # of Active # of Active # of Syslog State Seq Hosts Non-seq Hosts Messages Sent ----------- ----------- ------------- ------------- DOWN 0 0 0 TK>show syslog hosts SYSLOG Configured Hosts ----------------------- Host Ip Operational Address State Time Sequencing ---------------- ------------ --------------- 10.xx.xx.xx INACTIVE ENABLED If yes, how can I ACTIVATE the Operational State ? Thanks in advance -- Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail

2 1

not proper logs
by jack alex 08 Mar '05

08 Mar '05

Dear All, Iam using syslog-ng! I facing problem in my log rotation for postgres, it is not rotation properly. I am using syslog-ng package for loging. My logs for postgres looks like this, code: -rw-r--r-- 1 root root 10M Feb 28 23:24 postgres.log.20 -rw-r--r-- 1 root root 0 Feb 28 20:16 postgres.log.21 -rw-r--r-- 1 root root 10M Feb 28 20:15 postgres.log.22 -rw-r--r-- 1 root root 0 Feb 28 17:04 postgres.log.23 -rw-r--r-- 1 root root 10M Feb 28 17:03 postgres.log.24 -rw-r--r-- 1 root root 0 Feb 28 13:52 postgres.log.25 -rw-r--r-- 1 root root 10M Feb 28 13:51 postgres.log.26 -rw-r--r-- 1 root root 0 Feb 28 10:56 postgres.log.27 -rw-r--r-- 1 root root 10M Feb 28 10:55 postgres.log.28 -rw-r--r-- 1 root root 0 Feb 28 08:40 postgres.log.29 -rw-r--r-- 1 root root 0 Mar 2 00:12 postgres.log.3 That's after rotation it generates two files one with 0MB size and another with is of 10MB, so, why it is generating 0MB size log files?? Does it supports syslogng package for loging? If yes then what is the difference is its configuration from normal syslog package. Any help appreciated. -jack __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/

1 0

2 configuration questions
by ARGEXT-HIDALGO, FRANCISCO 07 Mar '05

07 Mar '05

Hi, I would like to ask you about two things: 1. I have a central syslog-ng server logging everything as IP's because we need it that way, but for php-syslog-ng I would like to see them as hostnames. It is possible to resolve hostnames to some destinations only? 2. We have one syslog-ng server in each region and each of them logs to the central server, I would like to be able to log each region to a diferent file. I think I can do it by sending from a different facility from each region. Unfortunatelly reconfiguring every router and switch from the network is not an option, so I was thinking I could do it if each regional server resends it's logs with a particular facility, changing the original one that it received from it's routers. Is this possible?, if not, do you know another way to do it?, I was thinking that I could send each region to a different port of the central syslog, but I prefer not changing the current configuration if possible. Thank you, Francisco

1 0

Fedora Core 3, SELinux, and syslog-ng
by Mike Pepe 05 Mar '05

05 Mar '05

I'm wondering if anyone knows the magic incantation you need in order to make FC3 with selinux turned on to like syslog-ng. it won't let syslog-ng access /proc/kmesg and therefore prevents it from working. If I turn off selinux, of course, it works fine. This selinux stuff is nice, but hard to figure out!

3 2

Re: [syslog-ng]Syslog-NG 1.6.6 memory leak when sending UDP logs
by henry＠shoelacecity.com 05 Mar '05

05 Mar '05

>There is no version 1.2.2, the latest version is 1.1.2.1 (or 1.1.3 which >is BETA) My bad, (typo) 1.1.2(.1) to be specific. >This patch fixes the byte order issue, and I'm still hunting the memory >leak with your configuration: > >diff -u -r1.25.4.6 afinet.c >--- afinet.c 5 Aug 2004 11:35:12 -0000 1.25.4.6 >+++ afinet.c 3 Mar 2005 12:26:47 -0000 >@@ -617,11 +617,10 @@ > ADDRESS2SOCKADDR(msg->saddr, sizeof(src_addr), (struct sockaddr *) &src_addr); > ADDRESS2SOCKADDR(self->super.dest_addr, sizeof(dst_addr), (struct sockaddr *) >&dst_addr); > >- > libnet_clear_packet(self->lnet_ctx); > >- udp = libnet_build_udp(src_addr.sin_port, >- dst_addr.sin_port, >+ udp = libnet_build_udp(ntohs(src_addr.sin_port), >+ ntohs(dst_addr.sin_port), > LIBNET_UDP_H + msg_line->length, > 0, > msg_line->data, I applied the patch, and recompiled. You are not going to beleive this: Data is STILL getting to the destination properly - despite the ntohs function. Yes, I checked the binary to be certain it recompiled, and threw a printf statement in there to be certain. It would seem that the ntohs function has no effect.

2 1

Resolve hostnames for some destinations only
by ARGEXT-HIDALGO, FRANCISCO 04 Mar '05

04 Mar '05

Is this possible?, I have everything logged as IP's because we need it that way, but for php-syslog-ng I would like to see it as hostnames. Any solutions? Thank you. Francisco

1 0